VM freezes when passthrough RTX 3080 to Windows 11 on Proxmox 9.2.3

B

brnogu

Active Member
Dec 13, 2020
22
1
43
29
Hello everyone,

I was previously running the latest Proxmox 8 release, and today I upgraded to Proxmox 9, currently version 9.2.3.

My setup has two GPUs passed through to two different VMs. One of them is still working correctly, but I am having issues with the VM that uses an RTX 3080.

The RTX 3080 can be passed through to a VM, and the VM appears to boot normally before the NVIDIA drivers are installed. However, after installing the drivers and rebooting the VM, it freezes during startup. When this happens, the VM/QEMU process shows 100% CPU usage. Sometimes it appears to get stuck at around 40% during boot before freezing completely.

This VM was working normally for a long time on Proxmox 8, including earlier today before the upgrade. The issue only started after upgrading to Proxmox 9.

I am not sure yet which logs are most relevant for troubleshooting this.

Has anyone seen similar behavior with GPU passthrough after upgrading to Proxmox 9, especially with NVIDIA RTX cards?

EDIT: It seems the machine is not totally stuck. After a long long time, I can get to the desktop, but it keeps hanging. When it hangs the RDP connection goes down for a bit of time, then it gets up again. But the machine is unusable.

Thanks in advance.

Code: 
===== PROXMOX VERSION =====
proxmox-ve: 9.2.0 (running kernel: 7.0.12-1-pve)
pve-manager: 9.2.3 (running version: 9.2.3/d0fde103346cf89a)
proxmox-kernel-helper: 9.2.0
proxmox-kernel-7.0: 7.0.12-1
proxmox-kernel-7.0.12-1-pve-signed: 7.0.12-1
proxmox-kernel-6.8: 6.8.12-30
proxmox-kernel-6.8.12-30-pve-signed: 6.8.12-30
proxmox-kernel-6.8.12-17-pve-signed: 6.8.12-17
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8.12-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 19.2.3-pve1
corosync: 3.1.10-pve2
criu: 4.1.1-1
frr-pythontools: 10.6.1-1+pve2
ifupdown2: 3.3.0-1+pmx12
intel-microcode: 3.20250812.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.1
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.1.1
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.1.6
libpve-cluster-perl: 9.1.6
libpve-common-perl: 9.1.16
libpve-guest-common-perl: 6.0.4
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.6.6
libpve-notify-perl: 9.1.6
libpve-rs-perl: 0.15.3
libpve-storage-perl: 9.1.6
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 7.0.0-2
lxcfs: 7.0.0-pve1
novnc-pve: 1.7.0-1
proxmox-backup-client: 4.2.2-1
proxmox-backup-file-restore: 4.2.2-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.3
proxmox-kernel-helper: 9.2.0
proxmox-mail-forward: 1.0.3
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.4
proxmox-widget-toolkit: 5.2.5
pve-cluster: 9.1.6
pve-container: 6.1.10
pve-docs: 9.2.2
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.18-4
pve-ha-manager: 5.2.4
pve-i18n: 3.8.0
pve-qemu-kvm: 11.0.0-4
pve-xtermjs: 6.0.0-1
qemu-server: 9.1.17
smartmontools: 7.5-pve2
spiceterm: 3.4.2
swtpm: 0.8.0+pve3
vncterm: 1.9.2
zfsutils-linux: 2.4.2-pve1

===== KERNEL =====
Linux proxmoxnext 7.0.12-1-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.12-1 (2026-06-09T21:07Z) x86_64 GNU/Linux

===== HOST CPU =====
CPU(s):                                  32
On-line CPU(s) list:                     0-31
Model name:                              Intel(R) Core(TM) i9-14900K
Thread(s) per core:                      2
Core(s) per socket:                      24
Socket(s):                               1
CPU(s) scaling MHz:                      72%
Flags:                                   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect user_shstk avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi vnmi umip pku ospke waitpkg gfni vaes vpclmulqdq rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities
Virtualization:                          VT-x
NUMA node(s):                            1
NUMA node0 CPU(s):                       0-31

===== HOST MEMORY =====
               total        used        free      shared  buff/cache   available
Mem:           125Gi        80Gi        36Gi       139Mi        10Gi        45Gi
Swap:          8.0Gi          0B       8.0Gi

===== KERNEL CMDLINE =====
BOOT_IMAGE=/boot/vmlinuz-7.0.12-1-pve root=/dev/mapper/pve-root ro quiet

===== VM CONFIG =====
agent: 1
bios: ovmf
boot: order=scsi0;net0;ide0
cores: 16
cpu: host
efidisk0: M2-Samsung-2TB:vm-101-disk-0,efitype=4m,ms-cert=2023k,pre-enrolled-keys=1,size=4M
hostpci0: 0000:02:00,pcie=1,rombar=0
machine: pc-q35-9.2+pve1
memory: 40960
meta: creation-qemu=9.0.2,ctime=1736517533
name: GamingVM
net0: virtio=BC:24:11:C7:92:20,bridge=vmbr0
numa: 0
onboot: 1
ostype: win11
scsi0: M2-Samsung-2TB:vm-101-disk-1,iothread=1,size=1T,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=21dc0df4-4568-4b38-8857-6c003d1a15ba
sockets: 1
tpmstate0: M2-Samsung-2TB:vm-101-disk-2,size=4M,version=v2.0
vmgenid: 607af564-d532-4cc9-8df9-a782c30e0d30

===== PCI GPU / AUDIO / VFIO DEVICES =====
0000:00:1f.3 Audio device [0403]: Intel Corporation Raptor Lake High Definition Audio Controller [8086:7a50] (rev 11)
        DeviceName: Intel HD Audio
        Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_soc_avs, snd_sof_pci_intel_tgl, snd_hda_intel
0000:00:1f.4 SMBus [0c05]: Intel Corporation Raptor Lake-S PCH SMBus Controller [8086:7a23] (rev 11)
        DeviceName: SMBus Controller
        Subsystem: ASUSTeK Computer Inc. Device [1043:8882]
--
0000:01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:3fcb]
        Kernel driver in use: vfio-pci
        Kernel modules: nvidiafb, nouveau, nova_core
0000:01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:10fa] (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:3fcb]
        Kernel driver in use: vfio-pci
        Kernel modules: snd_hda_intel
0000:02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA102 [GeForce RTX 3080] [10de:2206] (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:403d]
        Kernel driver in use: vfio-pci
        Kernel modules: nvidiafb, nouveau, nova_core
0000:02:00.1 Audio device [0403]: NVIDIA Corporation GA102 High Definition Audio Controller [10de:1aef] (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:403d]
        Kernel driver in use: vfio-pci
        Kernel modules: snd_hda_intel
0000:03:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] [144d:a80c]
        Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
        Kernel driver in use: nvme
        Kernel modules: nvme
0000:06:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11)
--
        Kernel driver in use: vfio-pci
        Kernel modules: ahci
0000:08:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
        DeviceName: ASM1061
        Subsystem: ASUSTeK Computer Inc. Device [1043:858d]
        Kernel driver in use: ahci
        Kernel modules: ahci

===== IOMMU GROUPS =====
IOMMU Group 0 0000:00:00.0 Host bridge [0600]: Intel Corporation Raptor Lake-S Host Bridge/DRAM Controller [8086:a700] (rev 01)
IOMMU Group 1 0000:00:01.0 PCI bridge [0604]: Intel Corporation Raptor Lake PCI Express 5.0 Graphics Port (PEG010) [8086:a70d] (rev 01)
IOMMU Group 2 0000:00:01.1 PCI bridge [0604]: Intel Corporation Device [8086:a72d] (rev 01)
IOMMU Group 3 0000:00:06.0 PCI bridge [0604]: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port [8086:a74d] (rev 01)
IOMMU Group 4 0000:00:0a.0 Signal processing controller [1180]: Intel Corporation Raptor Lake Crashlog and Telemetry [8086:a77d] (rev 01)
IOMMU Group 5 0000:00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation [8086:a77f]
IOMMU Group 5 10000:e0:17.0 SATA controller [0106]: Intel Corporation Raptor Lake SATA AHCI Controller [8086:7a62] (rev 11)
IOMMU Group 6 0000:00:14.0 USB controller [0c03]: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 Gb/s) XHCI Host Controller [8086:7a60] (rev 11)
IOMMU Group 6 0000:00:14.2 RAM memory [0500]: Intel Corporation Raptor Lake-S PCH Shared SRAM [8086:7a27] (rev 11)
IOMMU Group 7 0000:00:15.0 Serial bus controller [0c80]: Intel Corporation Raptor Lake Serial IO I2C Host Controller #0 [8086:7a4c] (rev 11)
IOMMU Group 7 0000:00:15.1 Serial bus controller [0c80]: Intel Corporation Raptor Lake Serial IO I2C Host Controller #1 [8086:7a4d] (rev 11)
IOMMU Group 7 0000:00:15.2 Serial bus controller [0c80]: Intel Corporation Raptor Lake Serial IO I2C Host Controller #2 [8086:7a4e] (rev 11)
IOMMU Group 8 0000:00:16.0 Communication controller [0780]: Intel Corporation Raptor Lake CSME HECI #1 [8086:7a68] (rev 11)
IOMMU Group 9 0000:00:17.0 System peripheral [0880]: Intel Corporation RST VMD Managed Controller [8086:09ab]
IOMMU Group 10 0000:00:1a.0 PCI bridge [0604]: Intel Corporation Raptor Lake PCI Express Root Port #25 [8086:7a48] (rev 11)
IOMMU Group 11 0000:00:1b.0 PCI bridge [0604]: Intel Corporation Raptor Lake PCI Express Root Port #17 [8086:7a40] (rev 11)
IOMMU Group 12 0000:00:1b.4 PCI bridge [0604]: Intel Corporation Raptor Lake PCI Express Root Port #21 [8086:7a44] (rev 11)
IOMMU Group 13 0000:00:1c.0 PCI bridge [0604]: Intel Corporation Raptor Lake PCI Express Root Port #1 [8086:7a38] (rev 11)
IOMMU Group 14 0000:00:1c.1 PCI bridge [0604]: Intel Corporation Raptor Lake PCI Express Root Port [8086:7a39] (rev 11)
IOMMU Group 15 0000:00:1c.3 PCI bridge [0604]: Intel Corporation Raptor Lake PCI Express Root Port #4 [8086:7a3b] (rev 11)
IOMMU Group 16 0000:00:1c.4 PCI bridge [0604]: Intel Corporation Raptor Lake PCI Express Root Port [8086:7a3c] (rev 11)
IOMMU Group 17 0000:00:1d.0 PCI bridge [0604]: Intel Corporation Raptor Lake PCI Express Root Port #9 [8086:7a30] (rev 11)
IOMMU Group 18 0000:00:1f.0 ISA bridge [0601]: Intel Corporation Raptor Lake LPC/eSPI Controller [8086:7a04] (rev 11)
IOMMU Group 18 0000:00:1f.3 Audio device [0403]: Intel Corporation Raptor Lake High Definition Audio Controller [8086:7a50] (rev 11)
IOMMU Group 18 0000:00:1f.4 SMBus [0c05]: Intel Corporation Raptor Lake-S PCH SMBus Controller [8086:7a23] (rev 11)
IOMMU Group 18 0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Raptor Lake SPI (flash) Controller [8086:7a24] (rev 11)
IOMMU Group 19 0000:01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1)
IOMMU Group 19 0000:01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:10fa] (rev a1)
IOMMU Group 20 0000:02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA102 [GeForce RTX 3080] [10de:2206] (rev a1)
IOMMU Group 20 0000:02:00.1 Audio device [0403]: NVIDIA Corporation GA102 High Definition Audio Controller [10de:1aef] (rev a1)
IOMMU Group 21 0000:03:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] [144d:a80c]
IOMMU Group 22 0000:06:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11)
IOMMU Group 23 0000:08:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
IOMMU Group 24 0000:09:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I226-V [8086:125c] (rev 06)
IOMMU Group 25 0000:0a:00.0 PCI bridge [0604]: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] [8086:1136] (rev 02)
IOMMU Group 26 0000:0b:00.0 PCI bridge [0604]: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] [8086:1136] (rev 02)
IOMMU Group 27 0000:0b:01.0 PCI bridge [0604]: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] [8086:1136] (rev 02)
IOMMU Group 28 0000:0b:02.0 PCI bridge [0604]: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] [8086:1136] (rev 02)
IOMMU Group 29 0000:0b:03.0 PCI bridge [0604]: Intel Corporation Thunderbolt 4 Bridge [Maple Ridge 4C 2020] [8086:1136] (rev 02)
IOMMU Group 30 0000:0c:00.0 USB controller [0c03]: Intel Corporation Thunderbolt 4 NHI [Maple Ridge 4C 2020] [8086:1137]
IOMMU Group 31 0000:40:00.0 USB controller [0c03]: Intel Corporation Thunderbolt 4 USB Controller [Maple Ridge 4C 2020] [8086:1138]

===== VFIO / BLACKLIST CONFIG =====
/etc/modprobe.d/intel-microcode-blacklist.conf:3:blacklist microcode
/etc/modprobe.d/pve-blacklist.conf:4:blacklist nvidiafb
 
Last edited:
Hi,

I don't think the thread you linked is related.
Not sure if this will completely resolve your specific freezing issue, but I highly recommend reading through the official PCI Passthrough on Proxmox VE wiki page to double-check your baseline configuration.

While glancing over the output you provided, I did spot that you are missing a couple of entries in your blacklist.

Try adding these and updating your initramfs:

Code: 
echo "blacklist nouveau" >> /etc/modprobe.d/pve-blacklist.conf
echo "blacklist nova_core" >> /etc/modprobe.d/pve-blacklist.conf
update-initramfs -u

This forum post might also be related Fix: NVIDIA Drivers Failing after upgrade to Proxmox 9.2.2 (Kernel 7.0.2-6-pve) / NovaCore Conflict

Make sure to reboot the Proxmox host afterwards. Hope this helps!
 
You must log in or register to reply here.
Top Bottom
Back