I haven't seen a post of a staff member in this thread, so I don't know if they are aware of this problem yet...I’m guessing this is going to get fixed soon as it’s a huge problem, right?
I pinged @oguz before, not sure if there's someone else we should ping. Hopefully soon. Thanks!
I pinged @oguz before, not sure if there's someone else we should ping. Hopefully soon. Thanks!
I haven't seen a post of a staff member in this thread, so I don't know if they are aware of this problem yet...
Awesome! Thanks for your great workFWIW, we're aware of it and will look more closely into it in the next work days, for now please just boot an older, previously working kernel, that's always a valid workaround. FYI: The problematic kernel is not yet on the enterprise repositories, so production workloads shouldn't be affected by this.
Also confirmed - 5.13.19-4-pve broke my system as well - get extremely hugh IO delays and systems hangs HARD! Can't even perform proper shutdown through KVM - console totally frozen!! Went back to previous kernel - all is well . . .
Good to hear. Thank you.FWIW, we're aware of it and will look more closely into it in the next work days, for now please just boot an older, previously working kernel, that's always a valid workaround. FYI: The problematic kernel is not yet on the enterprise repositories, so production workloads shouldn't be affected by this.
Perfect. I solved my problem with the solution provided by StruppieSame here - problem occurs only with newest kernel 5.13.19-4-pve, switching back to 5.13.19-3-pve works fine.
Sometimes pve comes up, but virtual machines cannot be started
For the ones running a headless system without the possibility to select a menu entry during boot via Grub, here a workaround to boot the former kernel, which runs fine for me:
- open file /etc/default/grub with editor (e.g. with nano or vi)
- change entry GRUB_DEFAULT=0 to GRUB_DEFAULT="1>2", which means select second main menu entry and then 3rd submenu entry (which is the former kernel 5.13.19-3-pve)
- save file
- run "update-grub" from terminal
- reboot
=> system starts up fine again, everything working as expected
The latter is only block device related, that can affect HBA's or disk pass-through, but not general PCI pass through, and it's also only a problem on 5.13 FWICT, as the back ported patch relied on behavior added only in later kernels.Maybe the problem here is not the passthrough but getting the kernel to release the controller and/or drives? Reports about that have popped up.
Seems that some devices can be passed through, others not so much. But actually I'm not sure it's the passthrough that is the problem...
Hello Matt, How did you install pve-kernel-5.15? When I tried those commands it couldn't find the kernel version.FYI I fixed the issue by updating to the latest kernel:
Code:apt update apt install pve-kernel-5.15
Hello,Had the same issue with USB-passthrough not working.
Went with the 5.15 kernel and now its back to working again.