Requesting exception for VEP-10 beta: DRA support for GPU/HostDevices

[Alay Patel]

Hi folks,

I am requesting exception for VEP-10: https://github.com/kubevirt/enhancements/issues/10. The effort this release is to take GPU and HostDevices DRA support to beta.

The major items for beta enablement (e2e tests and user-guide) are in progress and undergoing heavy reviews. 

For that reason, I am requesting additional week for setting up the CI with proper testing. 

Complete checklist of items pending is available here: https://github.com/kubevirt/enhancements/issues/10

Best,

Alay

[Itamar Holder]

Hi Alay,

I looked at the tracking issue, but couldn't find the list of PRs that need an exception. What am I missing?

Do you mind sharing the list here, updating the issue, or letting me know what I missed?

Thank you!

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/IA0PR12MB83259FFB3F92A502CDC6EF1ACDEE2%40IA0PR12MB8325.namprd12.prod.outlook.com.

[Alay Patel]

Hi Itamar, 

I checked again, the vep-10 issues only had details about pending items, it did not link the PR.

The issue is updated now to refer to open PRs as well. Here is the same list for quick reference:

• E2e test
• [merged] kernel module to introduce a fake pci device: Add k8s-vfio-gpu provider with fake PCI and install example dra driver: https://github.com/kubevirt/kubevirtci/pull/1726
• [Pending] Add a new DRA e2e test lane: https://github.com/kubevirt/project-infra/pull/5115
• [Pending] Add e2e tests that work on fake pci device: https://github.com/kubevirt/kubevirt/pull/18061
• Documentation for gpu dra drivers for users
• Nvidia DRA driver docs: https://github.com/kubernetes-sigs/dra-example-driver/pull/218
• User guide: https://github.com/kubevirt/user-guide/pull/1008

Thanks!

Alay

From: Itamar Holder <iho...@redhat.com>
Date: Monday, June 29, 2026 at 2:55 AM
To: Alay Patel <al...@nvidia.com>
Cc: kubevi...@googlegroups.com <kubevi...@googlegroups.com>
Subject: Re: [kubevirt-dev] Requesting exception for VEP-10 beta: DRA support for GPU/HostDevices

External email: Use caution opening links or attachments

[Itamar Holder]

Thanks Alay, that's helpful.

IIUC the reason for adding the e2e tests-related PR is that it was a requirement for Beta graduation.

I've chatted with @Vladik Romanovsky on this. While e2e tests are important, I don't see a huge benefit to add them to the previous release. The main value of presenting tests is doing so in the beginning of the cycle.

That being said, I think moving DRA to beta is important. It's one of our oldest VEPs, and I think we had more than enough time to fine-tune it.

What was brought up on my conversation with Vladik is that we'd approve an exception for a PR to bump DRA to beta, then you'll do your best to merge the remaining e2e tests to main (not to v1.9) as soon as possible. The user-guide PR should also be okay, as the user-guide is currently not versioned AFAICT.

What do you think?

What do others think?

BR,

Itamar.

[Alay Patel]

Hi Itamar,

All the e2e test work is intended to be against main, not against release-1.9, I agree with you that's where it will have its best realized benefit.

The reason why it was important and blocker for beta was, it provides a driver and fake pci devices that users and workflows can test without needing expensive GPU hardware.

Having said that, the core logic for providing fake pci devices and its driver support has merged: https://github.com/kubevirt/kubevirtci/pull/1726. From here, setting up is just going through the motions and getting all the dots checked.

Sreeja and I both have tried locally, the e2e tests are green the fake pci devices and driver. This gives me confidence that there are no hidden bugs that would have been caught if this was put in place in CI at the start of the cycle.

With all the explanation provided above, I feel confident we should be able to merge the e2e test and userguide ASAP after CF. 

If this works for the community please bless this PR enabling dra beta: https://github.com/kubevirt/kubevirt/pull/18247

Thanks,

[Itamar Holder]

Thank you Alay.

I support this exception request and have approved the PR that moves DRA to beta.

Thank you very much !

[Luboslav Pivarc]

Hey,

Thanks Alay for the update.

I must admit I don't fully understand why the tests are being disregarded. They ensure things work (that's why we require them in Beta) and that everything continues working.

What remaining work needs to be done to merge the test into main/1.9? 

Since there are no remaining "production" code changes I consider this VEP mostly done for the cycle but I would like to see the tests being merged before release (possibly after branching - today).

-Lubo

To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/CALpNySzL2j1bh93FXU9YGLzNUsGHjvwE%3Dj1zFqaA3TX%2BXrJOQg%40mail.gmail.com.

[Itamar Holder]

On Wed, 1 Jul 2026 at 23:25, Luboslav Pivarc <lpi...@redhat.com> wrote:

Hey,

Thanks Alay for the update.

I must admit I don't fully understand why the tests are being disregarded. They ensure things work (that's why we require them in Beta) and that everything continues working.

What remaining work needs to be done to merge the test into main/1.9? 

Since there are no remaining "production" code changes I consider this VEP mostly done for the cycle but I would like to see the tests being merged before release (possibly after branching - today).

Hey Lubo!

This is exactly the plan. Alay even mentioned yesterday in the sig-compute meeting that he'll try to merge the tests ASAP and if they show problems with DRA it will be moved out of Beta.

[Luboslav Pivarc]

Hey,

On Thu, Jul 2, 2026 at 8:54 AM Itamar Holder <iho...@redhat.com> wrote:

On Wed, 1 Jul 2026 at 23:25, Luboslav Pivarc <lpi...@redhat.com> wrote:

Hey,

Thanks Alay for the update.

I must admit I don't fully understand why the tests are being disregarded. They ensure things work (that's why we require them in Beta) and that everything continues working.

What remaining work needs to be done to merge the test into main/1.9? 

Since there are no remaining "production" code changes I consider this VEP mostly done for the cycle but I would like to see the tests being merged before release (possibly after branching - today).

Hey Lubo!

This is exactly the plan. Alay even mentioned yesterday in the sig-compute meeting that he'll try to merge the tests ASAP and if they show problems with DRA it will be moved out of Beta.

Great, sounds like a plan!

-Lubo

[Federico Fossemo]

Hey everyone,

Please do not forget to cherry-pick PRs. I did it this time :) 

• Add e2e tests for DRA support https://github.com/kubevirt/kubevirt/pull/18061 
• Backport: https://github.com/kubevirt/kubevirt/pull/18445
• move GPUsWithDRA and HostDevicesWithDRA feature gates to beta: https://github.com/kubevirt/kubevirt/pull/18247
• https://github.com/kubevirt/kubevirt/pull/18446

Thanks,
Federico

To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/CAFTR0GVNnznrsjWC5rtCV_o8whQnHJ5Rx5Jok7PvCVoFm%2B3%2BzQ%40mail.gmail.com.