Warning: UPDATING these packages broke my pci passthrough.

Sorry to borrow this topic. After updating the latest pve related components, compared with the original KVM that could not be started, now KVM can be started, but there are warnings.
References are as follows:

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
swtpm_setup: Not overwriting existing state file.
kvm: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]

Among them, the swtpm and warnings exist on all virtual machines. The PCI device is my NV graphics card, which currently does not affect the normal startup of KVM and device passthrough.
 
Sorry to borrow this topic. After updating the latest pve related components, compared with the original KVM that could not be started, now KVM can be started, but there are warnings.
References are as follows:

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
swtpm_setup: Not overwriting existing state file.
kvm: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]

Among them, the swtpm and warnings exist on all virtual machines. The PCI device is my NV graphics card, which currently does not affect the normal startup of KVM and device passthrough.

yes the pci warnings are new and intentional. Previously we tried e.g. to reset the device, but failed silently not knowing if it worked or not
those warnings are not bad per se, but could indicate a problem if e.g. something in the guest is not working right
 
  • Like
Reactions: mariol
In particular it should be fixed thanks to @dcsapak in libpve-common-perl >= 8.2.7 and qemu-server >= 8.2.6 both available in the testing repository at the time of this writing.

If you'd like to install the package, you can temporarily enable the repository (e.g. via the Repositories section in the UI), run apt update, run apt install libpve-common-perl qemu-server and disable the repository again, then run apt update again.

Just wanted to let the community know that the workaround Fiona suggested worked in my case.

I experienced issues on hosts with 2 CPU sockets and passing through two Nvidia L40(s) cards to a VM where only one of the GPUs was recognised in the VM. I do not exactly know which update broke the passtrough, but adding the testing apt repostiory, updating the two packages Fiona suggested and reverting back to the subscription repository, followed by an apt update and finally a host reboot, helped. Both GPUs show up in the VM now.
 
  • Like
Reactions: xmesaj2 and mariol

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!