Skip to content

WIP/DNM - arm64: Update FG support levels #939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
lyarwood wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

WIP/DNM - arm64: Update FG support levels #939

lyarwood wants to merge 2 commits into from

Conversation

@lyarwood
Copy link
Member

@lyarwood lyarwood commented Oct 31, 2025

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

Release note:

NONE

@kubevirt-bot
Copy link
Contributor

kubevirt-bot commented Oct 31, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kubevirt-bot kubevirt-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Oct 31, 2025
@kubevirt-bot
Copy link
Contributor

kubevirt-bot commented Oct 31, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jean-edouard for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@lyarwood lyarwood mentioned this pull request Oct 31, 2025
Closed
8 tasks
@lyarwood
arm64: Update FG support levels
d398166 
Signed-off-by: Lee Yarwood <lyarwood@redhat.com>
@lyarwood @claude
arm64: Update device support levels
5cdca58 
Update the arm64 device status documentation to align with the feature
gate documentation:

- Add status definitions (SUPPORTED/UNSUPPORTED/UNVERIFIED)
- Add CI test coverage information
- Standardize status values (SUPPORTED for CI-verified only)
- Add comprehensive notes section explaining:
  - Which devices have CI verification (4 devices)
  - Architecture-specific limitations (Watchdog, Sound)
  - Devices expected to work but unverified
  - Hardware passthrough requirements
- Note that sig-compute-migrations-wg-arm64 lane is not yet active

Only 4 devices are marked SUPPORTED based on actual wg-arm64 test
coverage:
- Disks (virtio bus)
- Interfaces (virtio-net-device)
- AutoattachPodInterface
- NetworkInterfaceMultiQueue

All other working devices are marked UNVERIFIED as they lack automated
CI testing on arm64.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@kubevirt-bot kubevirt-bot added dco-signoff: no Indicates the PR's author has not DCO signed all their commits. and removed dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Nov 19, 2025
@kubevirt-bot
Copy link
Contributor

kubevirt-bot commented Nov 19, 2025

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

  • 5cdca58 arm64: Update device support levels
Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dco-signoff: no Indicates the PR's author has not DCO signed all their commits. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@lyarwood @kubevirt-bot