Kernel 6.8.12-12-pve Update results in VFIO PCI passthrough issues

iuns3d92 said:
I wish I had found this thread sooner. I'm having a similar issue with Dell T40 server with UNRAID VM, with the onboard SATA controller passed to the VM. After updating to the latest kernel for Proxmox 8.x, which is 6.8.12-17-pve at this moment, I couldn't start the VM anymore. I tried a lot of things but nothing worked until I downgraded the kernel to 6.8.12-13-pve, which solved the issue.

Now I'm still getting some warnings when starting the VM but it works perfectly anyaway:

Bash: 
qm start 101
kvm: vfio: Cannot reset device 0000:00:17.0, no available reset mechanism.
kvm: vfio: Cannot reset device 0000:00:17.0, no available reset mechanism.


So the takeaway is that the problem is back in 6.8.12-17-pve (regression?) and you need to go back to 6.8.12-13-pve to fix it.
Click to expand...
Have you tried the opt-in 6.14 kernel for 8.x?
t.lamprecht

Thread 'Opt-in Linux 6.14 Kernel for Proxmox VE 8 available on test & no-subscription'

We recently uploaded a 6.14 kernel into our repositories. The current 6.8 kernel will stay the default on the Proxmox VE 8 series, the newly introduced 6.14 kernel is an option.
The 6.14 based kernel may be useful for some (especially newer) setups, for example if there is improved hardware support that has not yet been backported to 6.8.
This follows our tradition of upgrading the Proxmox VE kernel to match the current Ubuntu version until we reach an (Ubuntu) LTS release, like the 6.8 kernel is, and then provide newer kernels as opt-in. The 6.14 kernel is based on the Ubuntu 25.04 Plucky...
  • Like

I was using that prior to updating to Proxmox 9.1 a few weeks ago.
 
You must log in or register to reply here.
Top Bottom