>
> 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.


You could use qemu_cmdline VDSM hook to provide custom qemu command line
params for your VM or you could write your own hook to change libvirt xml
before the VM is powered on.

On Mon, Jan 25, 2021 at 7:03 PM Alex McWhirter <a...@triadic.us> wrote:

> 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.karga...@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@ovirt.org
> > To unsubscribe send an email to users-le...@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/XF4LZOEAC2YTRH5LTL55YKA4BPRZLVZH/
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/PY4ITOIWACUWHYLAVGOMMWIXUZYNDH5L/
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/HLC5IMZUXQAKMKVZHGJGTL7TPU5EBLOM/

Reply via email to