Warning: UPDATING these packages broke my pci passthrough.

[jtheisen]

I have to second this observation.
In my case it is a RTX 4060 Ti which should be passed through to a Linux VM.
It also currently refuses to start

root@pve-win11:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-1-pve)
pve-manager: 8.3.2 (running version: 8.3.2/3e76eec21c4a14a7)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-5
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
amd64-microcode: 3.20240820.1~deb12u1
ceph: 18.2.4-pve3
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.3
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-2
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.3
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

root@pve-win11:~# qm showcmd 110
/usr/bin/kvm -id 110 -name 'ollama,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/110.qmp,server=on,wait=off' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/110.pid -daemonize -smbios 'type=1,uuid=32225e3d-397e-475d-b7a7-6ce4308df946' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd' -drive 'if=pflash,unit=1,id=drive-efidisk0,format=raw,file=/dev/zvol/rpool/data/vm-110-disk-1,size=540672' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/110.vnc,password=on' -cpu qemu64,+abm,+aes,+avx,+avx2,+avx512bw,+avx512cd,+avx512dq,+avx512f,+avx512vl,+bmi1,+bmi2,enforce,+f16c,+fma,+kvm_pv_eoi,+kvm_pv_unhalt,+movbe,+pni,+popcnt,+sse4.1,+sse4.2,+ssse3,+xsave -m 16382 -object 'iothread,id=iothread-virtioscsi0' -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=355d72bb-8c8b-4ba0-9749-701600ecbb7a' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=0000:01:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on' -device 'vfio-pci,host=0000:01:00.1,id=hostpci0.1,bus=ich9-pcie-port-1,addr=0x0.1' -device 'VGA,id=vga,bus=pcie.0,addr=0x1' -chardev 'socket,path=/var/run/qemu-server/110.qga,server=on,wait=off,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:2bf63bb7ad9' -drive 'if=none,id=drive-ide2,media=cdrom,aio=io_uring' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=101' -device 'virtio-scsi-pci,id=virtioscsi0,bus=pci.3,addr=0x1,iothread=iothread-virtioscsi0' -drive 'file=/dev/zvol/rpool/data/vm-110-disk-0,if=none,id=drive-scsi0,discard=on,format=raw,cache=none,aio=io_uring,detect-zeroes=unmap' -device 'scsi-hd,bus=virtioscsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap110i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=BC:24:11:EC:31:38,netdev=net0,bus=pci.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256,bootindex=102' -machine 'type=q35+pve0'

Start error message

error writing '1' to '/sys/bus/pci/devices/0000:01:00.0/reset': Inappropriate ioctl for device
failed to reset PCI device '0000:01:00.0', but trying to continue as not all devices need a reset
kvm: ../hw/pci/pci.c:1633: pci_irq_handler: Assertion `0 <= irq_num && irq_num < PCI_NUM_PINS' failed.
TASK ERROR: start failed: QEMU exited with code 1

journalctl

Jan 15 16:06:28 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 16:06:28 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 16:06:28 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 16:06:28 pve-win11 kernel: vfio-pci 0000:01:00.1: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 16:06:28 pve-win11 kernel: vfio-pci 0000:01:00.1: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 16:06:28 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible

Jan 15 15:58:11 pve-win11 pvestatd[1639]: VM 110 qmp command failed - VM 110 not running
Jan 15 15:58:47 pve-win11 systemd-logind[1181]: New session 4621 of user root.
Jan 15 15:58:11 pve-win11 pvedaemon[2669381]: <root@pam> end task UPID:pve-win11:002F7714:52E3B19F:6787CC72:qmstart:110:root@pam: start failed: QEMU exited with code 1
Jan 15 15:58:47 pve-win11 systemd[1]: Starting user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Jan 15 15:58:11 pve-win11 pvedaemon[3110676]: start failed: QEMU exited with code 1
Jan 15 15:58:47 pve-win11 systemd[1]: Created slice user-0.slice - User Slice of UID 0.
Jan 15 15:58:10 pve-win11 pvedaemon[3107237]: VM 110 qmp command failed - VM 110 not running
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.1: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 65535ms after bus reset; giving up
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 32767ms after bus reset; waiting
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 16383ms after bus reset; waiting
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 8191ms after bus reset; waiting
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 4095ms after bus reset; waiting
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 2047ms after bus reset; waiting
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 1023ms after bus reset; waiting
Jan 15 15:59:24 pve-win11 kernel: pcieport 0000:00:01.1: retraining failed
Jan 15 15:59:24 pve-win11 kernel: pcieport 0000:00:01.1: broken device, retraining non-functional downstream link at 2.5GT/s
Jan 15 15:59:24 pve-win11 kernel: pcieport 0000:00:01.1: retraining failed
Jan 15 15:59:24 pve-win11 kernel: pcieport 0000:00:01.1: broken device, retraining non-functional downstream link at 2.5GT/s
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.1: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:59:24 pve-win11 kernel: fwbr110i0: port 2(tap110i0) entered disabled state
Jan 15 15:59:24 pve-win11 kernel: tap110i0 (unregistering): left allmulticast mode
Jan 15 15:59:24 pve-win11 kernel: fwbr110i0: port 2(tap110i0) entered disabled state
Jan 15 15:59:24 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.1: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible


Jan 15 15:57:06 pve-win11 pvestatd[1639]: VM 110 qmp command failed - VM 110 qmp command 'query-proxmox-support' failed - got timeout
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 65535ms after FLR; giving up
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 32767ms after FLR; waiting
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 16383ms after FLR; waiting
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 8191ms after FLR; waiting
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 4095ms after FLR; waiting
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 2047ms after FLR; waiting
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 1023ms after FLR; waiting
Jan 15 15:58:10 pve-win11 kernel: pcieport 0000:00:01.1: retraining failed
Jan 15 15:58:10 pve-win11 kernel: pcieport 0000:00:01.1: broken device, retraining non-functional downstream link at 2.5GT/s
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: timed out waiting for pending transaction; performing function level reset anyway
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:58:10 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:57:00 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:56:57 pve-win11 kernel: fwbr110i0: port 2(tap110i0) entered forwarding state
Jan 15 15:56:57 pve-win11 kernel: fwbr110i0: port 2(tap110i0) entered blocking state
Jan 15 15:56:57 pve-win11 kernel: tap110i0: entered allmulticast mode
Jan 15 15:56:57 pve-win11 kernel: fwbr110i0: port 2(tap110i0) entered disabled state
Jan 15 15:56:57 pve-win11 kernel: fwbr110i0: port 2(tap110i0) entered blocking state
Jan 15 15:56:57 pve-win11 kernel: fwbr110i0: port 1(fwln110i0) entered forwarding state
Jan 15 15:56:57 pve-win11 kernel: fwbr110i0: port 1(fwln110i0) entered blocking state
Jan 15 15:56:57 pve-win11 kernel: fwln110i0: entered promiscuous mode
Jan 15 15:56:57 pve-win11 kernel: fwln110i0: entered allmulticast mode
Jan 15 15:56:57 pve-win11 kernel: fwbr110i0: port 1(fwln110i0) entered disabled state
Jan 15 15:56:57 pve-win11 kernel: fwbr110i0: port 1(fwln110i0) entered blocking state
Jan 15 15:56:57 pve-win11 kernel: vmbr0: port 3(fwpr110p0) entered forwarding state
Jan 15 15:56:57 pve-win11 kernel: vmbr0: port 3(fwpr110p0) entered blocking state
Jan 15 15:56:57 pve-win11 kernel: fwpr110p0: entered promiscuous mode
Jan 15 15:56:57 pve-win11 kernel: fwpr110p0: entered allmulticast mode
Jan 15 15:56:57 pve-win11 kernel: vmbr0: port 3(fwpr110p0) entered disabled state
Jan 15 15:56:57 pve-win11 kernel: vmbr0: port 3(fwpr110p0) entered blocking state
Jan 15 15:56:57 pve-win11 kernel: tap110i0: entered promiscuous mode
Jan 15 15:56:57 pve-win11 systemd[1]: Started 110.scope.
Jan 15 15:56:57 pve-win11 pvedaemon[3110676]: failed to reset PCI device '0000:01:00.0', but trying to continue as not all devices need a reset
Jan 15 15:56:57 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:56:57 pve-win11 pvedaemon[3110676]: error writing '1' to '/sys/bus/pci/devices/0000:01:00.0/reset': Inappropriate ioctl for device
Jan 15 15:56:57 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 65535ms after FLR; giving up
Jan 15 15:56:57 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 32767ms after FLR; waiting
Jan 15 15:56:57 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 16383ms after FLR; waiting
Jan 15 15:56:57 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 8191ms after FLR; waiting
Jan 15 15:56:57 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 4095ms after FLR; waiting
Jan 15 15:56:57 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 2047ms after FLR; waiting
Jan 15 15:56:57 pve-win11 kernel: vfio-pci 0000:01:00.0: not ready 1023ms after FLR; waiting
Jan 15 15:56:57 pve-win11 kernel: pcieport 0000:00:01.1: retraining failed
Jan 15 15:56:57 pve-win11 kernel: pcieport 0000:00:01.1: broken device, retraining non-functional downstream link at 2.5GT/s
Jan 15 15:56:57 pve-win11 kernel: vfio-pci 0000:01:00.0: timed out waiting for pending transaction; performing function level reset anyway
Jan 15 15:55:46 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:55:46 pve-win11 kernel: vfio-pci 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible
Jan 15 15:55:46 pve-win11 pvedaemon[3110676]: start VM 110: UPID:pve-win11:002F7714:52E3B19F:6787CC72:qmstart:110:root@pam:
Jan 15 15:55:46 pve-win11 pvedaemon[2669381]: <root@pam> starting task UPID:pve-win11:002F7714:52E3B19F:6787CC72:qmstart:110:root@pam:

System:
AMD Ryzen 7700X
MSI MAG B650 Tomahawk