After apt-get update, Windows VM seems broken with GPU passthrough.

OrakMoya

New Member
Mar 30, 2024
1
0
1
A bit ago I set up a Windows VM into which I passed through a GTX1060 for remote rendering. I set up a TightVNC server inside it so I can remote into it even when the GPU is set as the primary card (has to be for Davinci Resolve to work).

Recently I updated Proxmox VE with the pve-no-subscription repo enabled and it seems to have broken this passthrough. Now the VM displays no output when the GPU is set as primary.

Dmesg shows:
Code:
[237639.594070] vfio-pci 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x8b42

Journalctl shows:
Code:
Sep 10 09:33:53 skmedia kernel: vfio-pci 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x8b42
Sep 10 09:33:53 skmedia QEMU[3636670]: kvm: vfio-pci: Cannot read device rom at 0000:01:00.0
Sep 10 09:33:53 skmedia QEMU[3636670]: Device option ROM contents are probably invalid (check dmesg).
Sep 10 09:33:53 skmedia QEMU[3636670]: Skip option ROM probe with rombar=0, or load from file with romfile=

lspci -nnk shows:
Code:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
        Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3283]
        Kernel driver in use: vfio-pci
        Kernel modules: nvidiafb, nouveau
01:00.1 Audio device [0403]: NVIDIA Corporation GP106 High Definition Audio Controller [10de:10f1] (rev a1)
        Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 High Definition Audio Controller [1462:3283]
        Kernel driver in use: vfio-pci

lsmod | grep vfio shows:
Code:
vfio_pci               12288  2
vfio_pci_core          81920  1 vfio_pci
vfio_iommu_type1       45056  1
vfio                   65536  8 vfio_pci_core,vfio_iommu_type1,vfio_pci
iommufd                94208  1 vfio
irqbypass              12288  2 vfio_pci_core,kvm


When the VM is running, there is no display to the GPU's HDMI output like there was before the update. Connecting to the TightVNC server succeeds but shows a black screen. Pinging the VM succeeds.


Running PVE v8.2.4 with 6.8.12-1-pve kernel, motherboard BIOS was not updated recently.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!