undefined | Better HN

0 pointslawl3y ago0 comments

Amd changed their windows drivers to not output video if it detects its running in a VM. Nvidia went the other way and stopped doing so.

Both can/could be bypassed with some libvirtd xml magic, but still. Nvidia seem to slowly stop being assholes, AMD started already.

0 comments

brezelgoring3y ago

>Amd changed their windows drivers to not output video if it detects its running in a VM.

What? Why?

lawlOP3y ago

Presumably market segmentation. You're only allowed VMs that dont feel like shit (i.e. have gpu accel) if you pay for enterprise vGPU shit. Can't have someone buy two of your GPUs to give one to a VM, obviously.

kaladin-jasnah3y ago

> pay for enterprise vGPU

For AMD the driver is difficult to find and poorly documented (and only available on ESXi unlike NVIDIA vGPU support for Xen, Hyper-V, KVM, Nutanix, and ESXi, etc.). At least the guest drivers don't have licensing issues unlike with NVIDIA IIUC.

1 more reply

kevincox3y ago

Because the drivers for the consumer GPUs are not licensed for datacebter use and obviously VM == datacenter

lokedhs3y ago

This is a problem for QUbes OS which has a legitimate need for vgpu on a desktop operating system.

It's because of this arbitrary restriction that Qubes is not able to provide GPU acceleration, which is a huge barrier to its adoption.

ridgered43y ago

Wow, I hadn't heard that AMD added that check. Between that and their unending reset problems that makes them a completely inferior choice for GPU passthrough. Before Nvidia stopped the passthrough blocking you could make a case that AMD was a better choice.

namlem3y ago

The cycle continues

j / k navigate · click thread line to collapse