Screen goes black after boot screen following driver install (NVIDIA & AMD GPU passthrough)

Hello folks!
While I still have not found a fix for the driver reset bug on my AMD R9 380x Nitro the simple workaround for now was switching the cards so that the NVIDIA GeForce GTX 980 is in the first PCI-E slot instead, which seems to allow at least a flawless first boot of a VM but I am sure rebooting would create issues.

I am using Proxmox VE 7 i think:


perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_ADDRESS = "de_DE.UTF-8", LC_NAME = "de_DE.UTF-8", LC_MONETARY = "de_DE.UTF-8", LC_PAPER = "de_DE.UTF-8", LC_IDENTIFICATION = "de_DE.UTF-8", LC_TELEPHONE = "de_DE.UTF-8", LC_MEASUREMENT = "de_DE.UTF-8", LC_TIME = "de_DE.UTF-8", LC_NUMERIC = "de_DE.UTF-8", LANG = "en_US.UTF-8" are supported and installed on your system. perl: warning: Falling back to a fallback locale ("en_US.UTF-8"). pve-manager/7.0-13/7aa7e488 (running kernel: 5.11.22-5-pve)

Now sadly I have an even more annoying problem. After installing Windows 11 I finally did the GPU passthrough with the NVIDIA card and proceeded to install the driver.
During installation – presumably when the driver actually get initialized – the screen goes black and stays black. When rebooting the screen comes back online but goes black during the Windows boot sequence which presumably again is where the display driver is switched on.

VM 101 (win11):

cat 101.conf

bios: ovmf boot: order=virtio1 cores: 8 cpu: host,hidden=1,flags=+pcid efidisk0: local-lvm:vm-101-disk-3,efitype=4m,pre-enrolled-keys=1,size=4M hostpci0: 0000:05:00,pcie=1,romfile=GeForce_GTX_980_VGA_BIOS_84. ide0: local:iso/virtio-win.iso,media=cdrom,size=543390K ide2: local:iso/Win10_21H1_English_x64.iso,media=cdrom,size=5687620K machine: pc-q35-6.0 memory: 16384 name: x99-v-win11-64bit net0: e1000=DA:A2:90:FE:B3:9F,bridge=vmbr0,firewall=1 numa: 0 ostype: win11 scsihw: virtio-scsi-pci smbios1: uuid=aa0c2699-862d-47d9-ac61-d58e3ab266aa sockets: 1 tpmstate0: local-lvm:vm-101-disk-2,size=4M,version=v2.0 usb0: host=046d:c07e usb1: host=046d:c31c vga: none virtio0: local-lvm:vm-101-disk-0,size=4M virtio1: local-lvm:vm-101-disk-1,size=64G vmgenid: ffef132f-7093-49e2-a38d-2a0e29daee87

To make sure this is not some kind of Error 43 NVIDIA bullshit – which I thought was finally “fixed” by NVIDIAs decision to stop screwing customers needlessly – I cloned the Win 11 machine and put Win 10 on it. Then I passed through the AMD card. I have pretty much the same issue there only that just waiting made the screen go black. I assume however that Windows was taken the liberty to install a more fitting display driver in the background in that time – read: the AMD one…

VM 102 (win10)

cat 102.conf

bios: ovmf boot: order=ide2;virtio1 cores: 8 cpu: host,hidden=1,flags=+pcid efidisk0: local-lvm:vm-102-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M hostpci0: 0000:03:00,pcie=1,romfile=Sapphire.R9380X.4096.151101.rom ide0: local:iso/virtio-win.iso,media=cdrom,size=543390K ide2: local:iso/Win10_21H1_EnglishInternational_x64.iso,media=cdrom,size=5696060K machine: pc-q35-6.0 memory: 16384 name: x99-v-win10-64bit net0: e1000=EA:C1:02:60:2D:BE,bridge=vmbr0,firewall=1 numa: 0 ostype: win10 scsihw: virtio-scsi-pci smbios1: uuid=bcdad938-d24c-419b-a392-fd6a138593c3 sockets: 1 tpmstate0: local-lvm:vm-102-disk-1,size=4M,version=v2.0 usb0: host=046d:c31c usb1: host=046d:c07e vga: none virtio1: local-lvm:vm-102-disk-2,size=64G vmgenid: b22fc67f-6447-411b-9879-b1eaa175d909

What am I missing?

I apologize if this is something stupid but I have probably made my VM configs worse now multiple times in order to “resolve” my issues…



Note: the original version of this thread was posted on the proxmox forums: Screen goes black after boot screen following driver install (NVIDIA & AMD GPU passthrough) | Proxmox Support Forum

The “repost” here is meant to activate a broader audience of people who may want to help, since no one has answered on the proxmox forums yet and also a Gaming VM in PVE7 is still pretty niche at this point…