Hey, Sergio will look for other things nowadays, but before doing so he has looked into that and mentioned that while fixing it for mantix was ok, he feared that the backport to the older jammy version would have been quite complex, dragging in many dependent patches and therefore overall was crossing his risk-vs-gain bar. So he suggested we close Jammy as won't fix for this particular issue. Sad for those affected for sure, but for all others keeping the regression risk low isn't a bad decision either.
Workarounds, if you can't use a new release, might be using the qemu in server-backports [1]. Not as official and supported, but for cases like this often getting you over the finishing line. This does not mean it can never happen, if anyone is either making this a more important case or even better is willing and able to spend backporting and testing efforts this can come back. So far this is a year old and had no one else chiming in, so it seems to be the better call - maybe rejecting it now more clearly will bring up many others and then it needs to be reconsidered. [1]: https://launchpad.net/~canonical-server/+archive/ubuntu/server- backports ** Tags removed: server-todo ** Changed in: qemu (Ubuntu Jammy) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051965 Title: QEmu with TCG acceleration (without KVM) causes kernel panics with guest kernels >=6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2051965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
