I've been able to trick consumer GPUs into working with KVM on machines that I also use for oVirt, but oVirt itself is constructing the XML files for KVM on-the-fly, so you'd have to fiddle with the code that builds them: I haven't even found that yet.

IIRC oVirt 4.3 should have the basic hooks in place for mdev passthrough. For nvidia this mean you need the vgpu drivers and a license server. These licenses have a recurring cost. AMD's solution uses SR-IOV, and requires a custom kernel module that is not well tested YMMV. You can also passthrough entire cards in ovirt without any drivers, granted since the amount of GPU's you can stuff into a server is limited this is probably not ideal. Nvidia blocks this on consumer level cards. Intel also has a mdev solution that is built into mesa / the kernel already, we have used it with VCA cards in the past, but perhaps the new Intel GPU's support it as well? Intel is the only option that will allow you to feed the framebuffer data back into spice so you can use the ovirt console. All other options require you to create a remote session to the guest directly. On 2021-01-25 07:49, kim.kargaard(a)noroff.no wrote: > Hi, > > We are looking at getting some GPU's for our servers and to use vGPU > passthrough so that our students can do some video renders on the > VM's. Does anyone have good experience with the Nvidia Quadro RTX6000 > or RTX8000 and ovirt 4.3? > > Thanks. > > Kim > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/XF4LZOEAC2Y... _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PY4ITOIWACU...

Thanks all for the feedback. When we bought the servers, they put some Nvidia Quadro P4000's in, but I can't seem to find anything that says they support vGPU. I wasn't aware of the license server requirement for Nvidia, but the pricing isn't too bad, so I can probably get that pushed through. Anyone aware of which AMD cards are supported by oVirt? I have only found a list of Nvidia cards. Thanks, Kim

why a hook? we have a “native” ovirt support for both GPU and vGPU since cca 4.1. There was a hook initially, but that’s no longer needed…since 4.2 iirc I think we also tested some Intel’s GTV-g card...

I would also be interested to know that :)

On 27. 1. 2021, at 19:20, Thomas Hoberg <thomas(a)hoberg.net&gt; wrote: > On Wed, Jan 27, 2021 at 9:14 AM <kim.kargaard(a)noroff.no&gt; wrote: > > > Ok, I think I found at least for Nvidia. You can follow what described for > RHV: > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/... > > In the same manual there are also instructions for vGPU. > > There is also the guide for 4.3: > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/... > > Gianluca Again, that's the easy part that works just fine. It's afterwards when you try to install the Nvidia driver when there might be trouble because the driver refused to load on GPUs that aren't permitted to operate inside a VM, quite independent of the hypervisor (same issue with VMware, VirtualBox, KVM). For that there are tricks you'll find on the Internet on how to cheat the Nvidia driver into believing it's running on a physical machine but on KVM that implies editing the XML config... which in the case of oVirt seems to be generated at startup.

So I guess the hooking mechanism can be used to take care of that, but I've not progressed to that stage myself, mostly because the GPUs I use in the corporate lab are whitelisted by Nvidia.

And just to give a little credit: Pass-through works very well with oVirt 4.3, only moving (inactive) VMs from host-to-host is a little more involved, while GPU live-migration unfortunately is out of the question. That makes perfect sense for NICs and storage adapters, for GPUs one might argue that their state could be migrated, too. But Linux doesn't really understand heterogenous accelerators yet, so oVirt can't do better.

_______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/S3DBQHTQDOZ...