After Updating to 6.12.3 - Getting multiple errors and GPU passthrough no longer works


Go to solution Solved by SimonF,

Recommended Posts

Hey all. Hopefully someone can help as this leaves me sorta dead in the water. After updating to 6.12.3, I can no longer passthrough my GPU to my Win 10 VM and autostarting any VMs gives me an error. Unfortunately, I didn't notice these issues/pay much attention to them until after I started a lengthy disk swap, that invloves (one at a time) replacing 4 disks. So I am unable to roll back to 6.10.x

 

Attached are the diasgnositics. Two issues are:

-Windows 10 no longer recognizes my GPU (GTX1060) - it shows it in an error state in windows device manager (sn attached)

-Everytime I stop and start the array, none of my VMs autostarts and I get a virtio error

 

Niether of these were issues in 6.10.x, everyone worked fine one minute, then immeadiately after the update these issues started.

 

Things I've tried:

-deleting the VM and remaking it

-using VNC as the primary display and making the GPU secondary

-trying to pass the GPU to my other windows server VM

-GPU tested in seperate PC and works fine

-Uninstalling and reinstalling all NVIDIA drivers

-Tried a clean install of windows server 2022, same error in windows

-No errors when booting from an image of the VM on bare metal (restored to a different PC), GPU works fine

-Different PCI-e card works in the slot the GPU is in now

-PSU confirmed to be delivering power

 

Any help would be much appreciated! Thanks!!

 

Screenshot 2023-08-12 at 12.00.49.png

tower-diagnostics-20230812-1154.zip

Edited by sublimejackman
Updated list of troubleshooting methods tried
Link to comment
  • Solution
15 minutes ago, sublimejackman said:

Hey all. Hopefully someone can help as this leaves me sorta dead in the water. After updating to 6.12.3, I can no longer passthrough my GPU to my Win 10 VM and autostarting any VMs gives me an error. Unfortunately, I didn't notice these issues/pay much attention to them until after I started a lengthy disk swap, that invloves (one at a time) replacing 4 disks. So I am unable to roll back to 6.10.x

 

Attached are the diasgnositics. Two issues are:

-Windows 10 no longer recognizes my GPU (GTX1060) - it shows it in an error state in windows device manager (sn attached)

-Everytime I stop and start the array, none of my VMs autostarts and I get a virtio error

 

Niether of these were issues in 6.10.x, everyone worked fine one minute, then immeadiately after the update these issues started.

 

Things I've tried:

-deleting the VM and remaking it

-using VNC as the primary display and making the GPU secondary

-trying to pass the GPU to my other windows server VM

-GPU tested in seperate PC and works fine

 

Any help would be much appreciated! Thanks!!

 

Screenshot 2023-08-12 at 12.00.49.png

tower-diagnostics-20230812-1154.zip 240.09 kB · 1 download

Reason for autostart not working is 74:00.0 is not valid either delete that section from the config file on the boot/config/vfio-pci.cfg or make some changes from sysdevices to update the file. Also you dont have the audio part bound for 02:00.1 on the graphics card.  Also does not look like you have it passed thru to VM hence the possible issue with drivers.

 

BIND=0000:00:1f.3|8086:a348 0000:02:00.0|10de:1c03 0000:03:00.0|144d:a808 0000:74:00.0|144d:a809

Link to comment
8 minutes ago, SimonF said:

Reason for autostart not working is 74:00.0 is not valid either delete that section from the config file on the boot/config/vfio-pci.cfg or make some changes from sysdevices to update the file. Also you dont have the audio part bound for 02:00.1 on the graphics card.  Also does not look like you have it passed thru to VM hence the possible issue with drivers.

 

BIND=0000:00:1f.3|8086:a348 0000:02:00.0|10de:1c03 0000:03:00.0|144d:a808 0000:74:00.0|144d:a809

I will remove that entry, next time I take the array down and start it shall test. Thanks!!

 

Sorry, I should have added to things I tried:

-Uninstalling and reinstalling all NVIDIA drivers

-Tried a clean install of windows server 2022, same error in windows

-No errors when booting from an image of the VM on bare metal (restored to a different PC), GPU works fine

-Different PCI-e card works in the slot the GPU is in now

-PSU confirmed to be delivering power

Edited by sublimejackman
Link to comment
On 8/12/2023 at 12:24 PM, SimonF said:

Reason for autostart not working is 74:00.0 is not valid either delete that section from the config file on the boot/config/vfio-pci.cfg or make some changes from sysdevices to update the file. Also you dont have the audio part bound for 02:00.1 on the graphics card.  Also does not look like you have it passed thru to VM hence the possible issue with drivers.

 

BIND=0000:00:1f.3|8086:a348 0000:02:00.0|10de:1c03 0000:03:00.0|144d:a808 0000:74:00.0|144d:a809

That did it! All issues resolved. Thanks!!!

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.