4 ms·
Entirely for market segmentation. The ones they allow it on are much more expensive. With this someone could create a cloud game streaming service using norma
by simcop2387 6y ago
Entirely for market segmentation. The ones they allow it on are much more expensive. With this someone could create a cloud game streaming service using normal consumer cards and dividing them up for a much cheaper experience than the $5k+ cards that they currently allow it on. The recent change to allow virtualization at all (removing the code 43 block) does allow some of that, but does not allow you to say take a 3090 and split it up for 4 customers and get 3060-like performance for each of them for a fraction of the cost.
- my123 6y agoThe RTX A6000 is at USD 4650, with 48GB of VRAM and the full chip enabled (+ECC, vGPU, pro drivers of course) The RTX 3090, with 24GB of VRAM is at USD 1499. Customer dGPUs from other HW providers do not have virtualisation capabilities either.
- lostmsu 6y agoI am interested in the recent change you are referring to. Is there a good article on how to use it on Windows or at least Linux?
- sirn 6y agoThe OP is referring to GPU passthrough setup[1], which passes through a GPU from Linux host to Windows guest (e.g. for gaming). This is done by detaching the GPU from the host and pass it to the VM, thus most setup requires two GPUs since one need to remain with the host (although single GPU passthrough is also possible). Nvidia used to detect if the host is a VM and return error code 43 blocking them from being used (for market segmentation between GeForce and Quadro). This is usually solved by either patching VBIOS or hiding KVM from the guest, but it was painful and unreliable. Nvidia removed this limitation with RTX 30 series. This vGPU feature unlock (TFA) would allow GPU to be virtualized without requiring the GPU to first be detached from the host, vastly simplify the setup and open up the possibility of having multiple VMs running on a single GPU, all with its own dedicated vGPU. [1]: https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVM...