I have a GTX 970 that works great in my Ubuntu 16.04 VM, but will not work in my Windows 10 VM. The VM is a p2v conversion, but it works with the keyboard mouse and audio passthru and with VNC as graphics, but the screens never come up with the 970. I believe I have the configuration correct in the VM settings (drivers, etc.), and have tried a few variations to be sure. Any help is greatly appreciated.

 

Diag attached. TIA.

largest-diagnostics-20161115-1758.zip

Have you disabled vnc?

The video card is set to the GTX 970. I tried adding an additional (crappy) NVIDIA card as well, but that didn't work either. When I RDP into the machine after turning it on, I see in device manager that there is an error Code 43 on both of the devices. From what I have read in the forums, this is because of a bug with NVIDIA cards that they become disabled if the machine is recognized as a VM. I have HyperV set to off, but not sure what else to do.

So no VNC set as graphics card at all to be clear.

What happens if you make a new win 10 VM? Do you have a picture on the monitor when booting the VM?

What is the two VM's set to, uefi or seabios?

VM is set to seabios. I get no picture on the monitor when booting to the VM. When I make a new VM, same thing happens, no picture.

VM is set to seabios. I get no picture on the monitor when booting to the VM. When I make a new VM, same thing happens, no picture.

 

Both the working and not working VM are set to seabios?

The Ubuntu VM that works with the 970 has the bios set to OVMF.

The Ubuntu VM that works with the 970 has the bios set to OVMF.

 

Then you have your answer. Use ovmf to create a new VM and it should work.

Do you think that because there is a difference? There are other differences between the VM's as well, and according to the wiki Windows VMs should use seabios, unless there is something I missed.

Do you think that because there is a difference? There are other differences between the VM's as well, and according to the wiki Windows VMs should use seabios, unless there is something I missed.

 

There is no rule that windows should use seabios. Some times seabios works with a specific GPU and not ovmf, and vice versa. So use what works.

You will have to create a new windows 10 VM to use ovmf. You could reuse the uuid of the existing win 10 VM so you don't have to reactivate windows through phone when you reinstall windows. You will have to reinstall when changing from seabios to ovmf.

 

Simply create a new VM and before clicking done, remove the thick in the start VM after creation box. Then go edit the XML and change the uuid to the same as the old VM. You might have to delete the old VM before that. So backup the XML and don't choose to delete the disk.

Then start the VM and install windows.

So I can't assign the current virtual disk (the one I p2v'd) for this, I have to make a completely new VM from scratch?

So I can't assign the current virtual disk (the one I p2v'd) for this, I have to make a completely new VM from scratch?

 

You can use the old disk, but it will be partitioned and formatted again when you install using ovmf as the partition layout is different. Seabios emulates the old BIOS, while ovmf emulates uefi BIOS.

Either way, backup the vdisk if it has any valuable data.

I got GPU passthru to work in the BIOS at least, so it seems like a matter of following directions and tweaking at this point. Thanks a ton.