4 ms·
NVIDIA support is not special as far as QEMU is concerned—the special parts are all in their proprietary device driver, and they talk to QEMU via the VFIO infra
by bonzini 2y ago
NVIDIA support is not special as far as QEMU is concerned—the special parts are all in their proprietary device driver, and they talk to QEMU via the VFIO infrastructure for userspace drivers. They just reimplemented the same thing in Cloud Hypervisor.
Red Hat for one doesn't ship any functionality that isn't available upstream, much less proprietary, and they have large customers using virtual GPU.
- transpute 2y ago> NVIDIA.. just reimplemented the same thing in Cloud Hypervisor. Was that recent, with MIG support for GPGPU partitioning? Is there a public mailing list thread or patch series for that work? Nvidia has a 90-page deployment doc on vCS ("virtual compute server") for RedHat KVM, https://images.nvidia.com/content/Solutions/data-center/deployment-guide-virtual-compute-server-rhel-kvm.pdf https://images.nvidia.com/content/Solutions/data-center/depl...
- bonzini 2y agoNot NVIDIA; fly.io reimplemented the parts that CH didn't already have. I know that CH is developed on GitHub but I don't know whether the changes are public or in-house. That said, the slowness of QEMU's startup is always exaggerated. Whatever they did with CH they could have done with QEMU.