Hey all-

I have a VM that I keep perpetually on Rawhide for testing that has working fine with updates until the latest 5.18 kernels; it just hangs. Nothing is shown on the screen, no kernel panics, just hangs. The VM is running on ESXi 6.0 on a X7350 Xeon (it’s a Dell PowerEdge R900 server FWIW), configured for 8 gig of ram, 8 processors, and 90 gig of disk space. I’ve tried both rc6 kernels, as well as rc3 (that’s what’s showing up in grub), all hang. Only my ancient F33 rescue kernel works gets the VM to boot. For testing I built a new VM based on F35 on the same machine with the same specs, updated it to Rawhide, and I get the same behavior, just hangs with the rc6 kernel. Is there any troubleshooting tips I could try to figure out what’s going on? I’m worried that I’m hitting some too-new-kernel-on-ancient-hardware issue that will prevent using this machine with newer versions of Fedora.

Rawhide is rolling so im confused what you mean by 35? Rawhide is going towards 37 Beta... Also for Rawhide i get all the configs in git and just do nightly net installs On Thu, May 12, 2022 at 2:15 PM Richard W.M. Jones <rjones(a)redhat.com&gt; wrote: > On Thu, May 12, 2022 at 11:35:44AM -0500, Ron Olson wrote: >> Hey all- > >> I have a VM that I keep perpetually on Rawhide for testing that has >> working fine with updates until the latest 5.18 kernels; it just >> hangs. Nothing is shown on the screen, no kernel panics, just >> hangs. The VM is running on ESXi 6.0 on a X7350 Xeon (it’s a Dell >> PowerEdge R900 server FWIW), configured for 8 gig of ram, 8 >> processors, and 90 gig of disk space. I’ve tried both rc6 kernels, >> as well as rc3 (that’s what’s showing up in grub), all hang. >> Only my >> ancient F33 rescue kernel works gets the VM to boot. >> >> For testing I built a new VM based on F35 on the same machine with >> the same specs, updated it to Rawhide, and I get the same behavior, >> just hangs with the rc6 kernel. >> >> Is there any troubleshooting tips I could try to figure out what’s >> going on? I’m worried that I’m hitting some >> too-new-kernel-on-ancient-hardware issue that will prevent using >> this machine with newer versions of Fedora. > > First step is to attach a (virtual) serial console to the guest and > see if anything is printed. Hopefully grub and/or the kernel will > automatically recognise the serial console and use it, but it's > possible you might need to interrupt grub and add “console=ttyS0” > to > the kernel command line. > > If there are some messages but not enough for diagnosis, then remove > any “rhgb” and “quiet” and add “ignore_loglevel”. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > Read my programming and virtualization blog: > http://rwmj.wordpress.com > Fedora Windows cross-compiler. Compile Windows programs, test, and > build Windows installers. Over 100 libraries supported. > http://fedoraproject.org/wiki/MinGW > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org > 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/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure >

_______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org 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/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure