Nivida 1060 New VM Not Starting And VM Unraid Screen Hanging With Either Windows 10 or 11

[ghost82]

13 hours ago, ccsnet said:

I've added them back and attached the diags for you as screen is not displaying

In the latest diagnostics I cannot see any particular issue..so my ideas are ending..

I would try, without modifying existing config:

1. to dump your gpu vbios and pass it to the vm

2. to not use video adapters (if you can): in my personal case I had no luck with dp-->vga, but dvi-->vga worked, never tried hdmi adapters.

[ccsnet]

7 hours ago, ghost82 said:

In the latest diagnostics I cannot see any particular issue..so my ideas are ending..

I would try, without modifying existing config:

1. to dump your gpu vbios and pass it to the vm

2. to not use video adapters (if you can): in my personal case I had no luck with dp-->vga, but dvi-->vga worked, never tried hdmi adapters.

1) yep... The bios I'm using is a direct dump and I've double checked the headers

 

2) That's my next thought as I have a sound card on the mobo but I don't have expectations that it will make a change as its windows reporting the issue. 

 

I'll not stop working in this as there must be an answer. 

 

Thanks again... Have a good Christmas 

 

T

Edited December 25, 2021 by ccsnet

[ccsnet]

So - going to log this for any one else following in my foot steps - countless hours now spent on this issue over Chrimbo and researching error 43.

 

I have tried all of the above and more on brand new fresh Win 10/11 images from MS and even tried all the same with another GPU side by side (on of the suggestions I saw was have another GPU).

 

Again tried all of the above with the GPUs as primary and secondarys.

 

I've also been making BIOS changes (my MSI 970 board is not very clear on vitual settings as its a gaming orianted)

 

I'm almost at the point of believing this is a lower level than some thing I can config as I know the card works fine with Unraid its self so the last couple of throws before I raise this to the devs will be to do the same again with Unbuntu to prove if it a Windows thing but also see if I can dump the bios on a Windows machine.

 

I dont believe these will make a diffrence but I want to try before I go back to borrowing an AMD card.

 

Any reeding I have done or things I have tried are in a post a bit further back that I have been editing.

 

Right - going for a lie down as its past 1 am

 

T

Edited January 2, 2022 by ccsnet

[twiikker]

For myself I haven't been able to use gpu inside windows VM without pulling vbios file from running windows system. Worked fine under linux with smaller vbios. Tried with linux vbios tried with vbios from techpowerup and only selfmade vbios from windows worked.

Edited January 2, 2022 by twiikker

[ccsnet]

3 hours ago, twiikker said:

For myself I haven't been able to use gpu inside windows VM without pulling vbios file from running windows system. Worked fine under linux with smaller vbios. Tried with linux vbios tried with vbios from techpowerup and only selfmade vbios from windows worked.

Hi... Seen a couple of your posts and it's one of the reasons I'm going to try pulling the bios out under windows. 

 

Using spaceinvaders script it always comes out as about 50k but that feels too small compared to others out there. (not science just a feeling). 

 

I did try to dl one from the dB he suggested and it was about 250k and didn't work so I'm hoping (not expecting) I may get a different result doing it via Windows.

 

Nb for any one interested... I've started testing Windows 10 as its more established and better fault finding plus windows 11 security was a problem... Ie pin services kept coming up or rdp was disabled. You can disable pin services and you can use teamviewer to remote in but that took some working out as there was no display

 

T

 

Ps

 

Just found a reason to love my pita nvida card (plus xbox) on my unraid server if I get it going... https://moonlight-stream.org/

Edited January 2, 2022 by ccsnet

[ccsnet]

Hi all... I did it. 

 

What an effort. 

 

So I managed to get access to another windows pc so put my card in the second slot and followed nvidas advice to extract the bios here... https://nvidia.custhelp.com/app/answers/detail/a_id/4188/~/extracting-the-geforce-video-bios-rom-file

 

I then edited the bios as per spaceinvaders guide...

 

Guess what, it was bigger as I suspected so this means the extract script he provides does not always work. 

 

Any way this was was not the end but the beginning of the end. 

 

I left video=efifb:off & the pci grouping in place but did not make any changes to the xml. 

 

I set the vm up as normal using q35 6.1 for Windows 10.

 

I set the card as primary with the newly edited bios. 

 

This worked first time so on to Windows 11.

 

Here it got tricky as I decided to do a clean and fresh setup with no. Vnc and the nvidia as the primary card. 

 

It was booting but only to the uefi (could explain what I saw earlier with it starting from the unraid point of view but not been able to access). 

 

I had to type exit and then manually select the virtual dvd. 

 

After adding in storage and network drivers during set up I was able to get to the gui but still had the error 43 on the driver. 

 

To get rid of this I uninstalled the device and downloaded the latest driver set from nvidia which were some twelve months later than what Windows had installed so probably had the fix in for code 43 (Nvidia have started playing nice with virtual machines... Info on the Web). 

 

This solved it. 

 

So I've prepped and rebooted a few times so  fairly happy it's job done.

 

I'm still not sure why it was booting to the uefi but hopefully it will not be an issue in the future, if it is this should help some one. 

 

I may have a play in the future ie put my nvidia drivers on for unraid so I can get to the gui and remove video=efifb:off to make it more standard just to see if the changes make any difference. 

 

I'll post here if I do. 

 

Any thoughts on all the above especially the uefi booting? 

 

Thanks to all those who helped on this thread. 

 

T

Edited January 3, 2022 by ccsnet

[ccsnet]

On 1/3/2022 at 2:43 PM, ccsnet said:

Hi all... I did it. 

 

What an effort. 

 

So I managed to get access to another windows pc so put my card in the second slot and followed nvidas advice to extract the bios here... https://nvidia.custhelp.com/app/answers/detail/a_id/4188/~/extracting-the-geforce-video-bios-rom-file

 

I then edited the bios as per spaceinvaders guide...

 

Guess what, it was bigger as I suspected so this means the extract script he provides does not always work. 

 

Any way this was was not the end but the beginning of the end. 

 

I left video=efifb:off & the pci grouping in place but did not make any changes to the xml. 

 

I set the vm up as normal using q35 6.1 for Windows 10.

 

I set the card as primary with the newly edited bios. 

 

This worked first time so on to Windows 11.

 

Here it got tricky as I decided to do a clean and fresh setup with no. Vnc and the nvidia as the primary card. 

 

It was booting but only to the uefi (could explain what I saw earlier with it starting from the unraid point of view but not been able to access). 

 

I had to type exit and then manually select the virtual dvd. 

 

After adding in storage and network drivers during set up I was able to get to the gui but still had the error 43 on the driver. 

 

To get rid of this I uninstalled the device and downloaded the latest driver set from nvidia which were some twelve months later than what Windows had installed so probably had the fix in for code 43 (Nvidia have started playing nice with virtual machines... Info on the Web). 

 

This solved it. 

 

So I've prepped and rebooted a few times so  fairly happy it's job done.

 

I'm still not sure why it was booting to the uefi but hopefully it will not be an issue in the future, if it is this should help some one. 

 

I may have a play in the future ie put my nvidia drivers on for unraid so I can get to the gui and remove video=efifb:off to make it more standard just to see if the changes make any difference. 

 

I'll post here if I do. 

 

Any thoughts on all the above especially the uefi booting? 

 

Thanks to all those who helped on this thread. 

 

T

So nearly a month later and I've had no problems. 

 

I hope the above helps some one although I'm still not 100pct what the issue was. 

 

T