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.
Attachment:
pgpF3k_S3W9Di.pgp
Description: PGP signature
_______________________________________________ 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
