Hello
I am currently trying to route an MSI GeForce GT 1030 AERO ITX 2G to my Windows 10 VM. The VM starts but I get the error 43 (That the GPU was turned off) I saw here in the forum that you can change this with the VBios. https://forums.unraid.net/topic/51230-video-guidehow-to-pass-through-an-nvidia-gpu-as-primary-or-only-gpu-in-unraid/
But I didn't quite understand what I had to do. It would be nice if someone could explain to me again what I have to do so that the graphics card under Windows 10 is recognized normally.

Edited October 26, 20196 yr by Tobiasp

This tutorial is more up to date, try following this one.

 

 

Thanks, but I don't understand the XML part. I don't have a button to open the XML file.

I deleted the Nvidia header and inserted it via the function but it doesn't work.

8 minutes ago, Tobiasp said:

Thanks, but I don't understand the XML part. I don't have a button to open the XML file.

There is a "XML View" button on the upper right corner.

 

With regards to the infamous error 43, it's not the GPU was turned off as you said. It's because the Nvidia driver refuses to load once it detects you are in a VM environment (in the hope that it would force you to buy the more expensive Quadro).

So do yourself a favour and do these first:

1. If you selected Hyper-V = "Yes" when building your VM template then START A BRAND NEW TEMPLATE and choose Hyper-V = "No".
2. Boot Unraid in Legacy mode.
3. If your motherboard BIOS allows you to pick a different slot as primary GPU to boot with, pick a different slot from what your 1030 is in (even if you don't have a 2nd GPU) and see if it would boot. Without a 2nd GPU, you won't see any boot prompts etc but if you can access the server through the network after a few minutes from boot then it has booted successfully.

Any help you would receive here is predicated on (1) above, without which there is no hope for a card that already does error 43.

 

(2) and (3) are my own personal recommendation as I have observed them to help with some cases.

They are attempts to stop the to-be-passed-through GPU from initiating and thus make it less likely to detect that it is in a VM.