I'm running Proxmox on 6 home PCs all with PCIE pass-through. This morning I just updated to the latest kernel and other proxmox updates that were released today. All systems were fine except for one older Pre-Ryzen based PC.
The pre-ryzen PC had several devices passed through such as SATA controllers and USB controllers. There were no previous issues. The devices are bound early and never touched by the OS.
After performing the update, VMs were unable to launch resulting in the following error message:
The updates that were performed today are the following:
I rolled back to the previous kernel [ 6.8.12-11-pve ] using "proxmox-boot-tool kernel pin 6.8.12-11-pve" and the issue disappeared. As I stated, all other newer systems still performed as expected with their passed through devices except for this one. I realize that with a lack of logging details, this is probably not something that can be resolved here quickly. Just posting for reference that the new kernel causes some type of vfio breakage with some special cases, in this case, an old FX based system.
The pre-ryzen PC had several devices passed through such as SATA controllers and USB controllers. There were no previous issues. The devices are bound early and never touched by the OS.
After performing the update, VMs were unable to launch resulting in the following error message:
Code:
kvm: -device vfio-pci,host=0000:00:12.0,id=hostpci1.0,bus=ich9-pcie-port-2,addr=0x0.0,multifunction=on: vfio 0000:00:12.0: error getting device from group 5: Permission denied
Verify all devices in group 5 are bound to vfio-<bus> or pci-stub and not already in use
TASK ERROR: start failed: QEMU exited with code 1
The updates that were performed today are the following:
- libnvpair3linux
- libuutil3linux
- libzfs4linux
- libzpool5linux
- proxmox-headers-6.8
- proxmox-headers-6.8.12-12-pve
- proxmox-kernel-6.8
- proxmox-kernel-6.8.12-12-pve-signed
- pve-firmware
- spl
- zfs-initramfs
- zfs-zed
- zfsutils-linux
I rolled back to the previous kernel [ 6.8.12-11-pve ] using "proxmox-boot-tool kernel pin 6.8.12-11-pve" and the issue disappeared. As I stated, all other newer systems still performed as expected with their passed through devices except for this one. I realize that with a lack of logging details, this is probably not something that can be resolved here quickly. Just posting for reference that the new kernel causes some type of vfio breakage with some special cases, in this case, an old FX based system.