On 7/18/22 14:42, Sam Varshavchik wrote:
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64
crash reliably, on particular hardware, after starting a VM in
virt-manager?
At least I think it's a crash. One second after a VM start it's
brick-city. Display frozen, no response from the network. I've got
nothing: after a reboot there's nothing in journalctl -r -b -1. This
brings up fond memories -- ages ago I had a null modem adapter hooked up
to a serial port, the kernel configured for a serial console, thusly I
was able to capture OOPSes over the serial console, in situations like
these.
But, these days, no more RS-232 ports. I dimly recall that a USB-serial
option is possible; but I don't have any of that in any case.
Anyway, reverting to 5.18.9 made this VM happy, and my VMs on another
hardware, also running the same kernel, are also fine. But, 5.18.11 gets
reliably clusterfarked by qemu on at least on some hardware
combinations. I wish I had more useful data points, but I've got nuthin'
worth putting into Bugzilla.
Hi Sam,
Did you try <Ctrl><alt><f2>?
Fortunately, it is not happening to me, but I
am still running 5.18.10-200.fc36.x86_64.
I am getting paranoid about upgrading my kernel.
Did you report it to Bugzilla?
-T
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
