Skip to content

Update Arm64 feature gate status for ExpandDisks, HotplugVolumes, GPUGate, and HostDevicesGate#951

Open
Alexdbsdfs wants to merge 2 commits intokubevirt:mainfrom
Alexdbsdfs:main
Open

Update Arm64 feature gate status for ExpandDisks, HotplugVolumes, GPUGate, and HostDevicesGate#951
Alexdbsdfs wants to merge 2 commits intokubevirt:mainfrom
Alexdbsdfs:main

Conversation

@Alexdbsdfs
Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

Updates the Arm64 feature gate status table in the user guide.
The following feature gates have been validated on Arm64, and the documentation is updated accordingly:

ExpandDisksGate → supported (CDI required)

HotplugVolumesGate → supported (depends on CDI and DataVolume)

GPUGate → verified (requires a GPU device)

HostDevicesGate → verified (requires GPU or sound card)

This change keeps the Arm64 feature gate documentation accurate and up-to-date.

Which issue(s) this PR fixes:
Fixes: N/A

Special notes for your reviewer:
Only documentation changes; no functional code is modified.

Release note:
Update Arm64 feature gate status for ExpandDisksGate, HotplugVolumesGate, GPUGate, and HostDevicesGate.

Fix duplicate 'may be' in hotplug_volumes.md

Signed-off-by: dingbo <156674508+Alexdbsdfs@users.noreply.github.com>
summary

Update Arm64 feature gate status for the following items:

ExpandDisksGate → supported (CDI is required)

HotplugVolumesGate → supported (depends on CDI and DataVolume)

GPUGate → verified (requires a GPU device)

HostDevicesGate → verified (requires GPU or sound card)

Reason

These features have been validated on Arm64 and the status in the documentation was outdated.
This PR updates the table accordingly.

Thanks!

Signed-off-by: dingbo <156674508+Alexdbsdfs@users.noreply.github.com>
@kubevirt-bot kubevirt-bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 1, 2025
@kubevirt-bot
Copy link
Copy Markdown
Contributor

Hi @Alexdbsdfs. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@kubevirt-bot
Copy link
Copy Markdown
Contributor

[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 mhenriks 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

@kubevirt-bot
Copy link
Copy Markdown
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 1, 2026
Copy link
Copy Markdown
Member

@aburdenthehand aburdenthehand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR and for your patience @Alexdbsdfs
I just have a couple of capitalization nits.
@zhlhahaha Can you please take a look?

FEATURE GATE | STATUS | NOTES
-- | -- | --
ExpandDisksGate | Not supported yet| CDI is needed
ExpandDisksGate | supported | CDI is needed
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ExpandDisksGate | supported | CDI is needed
ExpandDisksGate | Supported | CDI is needed

Comment on lines +22 to +23
GPUGate | verified | Need GPU device
HostDevicesGate | verified | Need GPU or sound card
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
GPUGate | verified | Need GPU device
HostDevicesGate | verified | Need GPU or sound card
GPUGate | Verified | Need GPU device
HostDevicesGate | Verified | Need GPU or sound card

SnapshotGate | Supported | Need snapshotter support https://github.com/kubernetes-csi/external-snapshotter
VMExportGate | Partially supported | Need snapshotter support https://kubevirt.io/user-guide/operations/export_api/, support exporting pvc, not support exporting DataVolumes and MemoryDump which rely on CDI
HotplugVolumesGate | Not supported yet | Rely on datavolume and CDI
HotplugVolumesGate | supported | Rely on datavolume and CDI
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
HotplugVolumesGate | supported | Rely on datavolume and CDI
HotplugVolumesGate | Supported | Rely on datavolume and CDI

@zhlhahaha
Copy link
Copy Markdown
Contributor

/lgtm
For the GPUGate and HostDevicesGate features, I do not have the required hardware to verify them. I’ve marked this as LGTM for now. It would be helpful if you could create an issue, include your verification results there, and add the issue link here. @Alexdbsdfs

@kubevirt-bot kubevirt-bot added lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Mar 11, 2026
@kubevirt-bot
Copy link
Copy Markdown
Contributor

PR needs rebase.

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.

@kubevirt-bot
Copy link
Copy Markdown
Contributor

Pull requests that are marked with lgtm should receive a review
from an approver within 1 week.

After that period the bot marks them with the label needs-approver-review.

/label needs-approver-review

@kubevirt-bot kubevirt-bot added the needs-approver-review Indicates that a PR requires a review from an approver. label Mar 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-approver-review Indicates that a PR requires a review from an approver. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants