Kernel Panic at boot after Update to latest 3.10.0-1160.31.1 Kernel in Hyper-V VM

General support questions
Post Reply
masterofnone
Posts: 2
Joined: 2021/06/16 06:12:50

Kernel Panic at boot after Update to latest 3.10.0-1160.31.1 Kernel in Hyper-V VM

Post by masterofnone » 2021/06/16 06:21:02

Good morning,

after some yum update last night on several Centos-Server-VMs (7.9.2009) running as VMs on Micrsoft Windows Hyper-V 2016, the VMs were updated to new Kernel "3.10.0-1160.31.1".
The VMs would not boot anymore after reboot with the new .31 Kernel.
Selecting the older 3.10.0-1160.25.1.el7 Kernel the boot is ok an working.
So i have uninstalled the .31 Kernel on the VMs in order to restore operations.

Does anyone have the same issue ? Or knows something about it?
I cloud not find any related informations or bugs during my search.

I have attached a screenshot of the VM Console right after the start of the VM.
centos_kernel_panic.png
centos_kernel_panic.png (19.51 KiB) Viewed 1571 times
Any help or info would be highly welcome.
Thanks
masterofnone :ugeek:

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Kernel Panic at boot after Update to latest 3.10.0-1160.31.1 Kernel in Hyper-V VM

Post by TrevorH » 2021/06/16 08:56:32

That looks like the stacktrace you get from an incomplete or corrupt initramfs file for the kernel selected. Either recreate it with dracut -f or yum reinstall that kenrel by full name-version.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

masterofnone
Posts: 2
Joined: 2021/06/16 06:12:50

Re: Kernel Panic at boot after Update to latest 3.10.0-1160.31.1 Kernel in Hyper-V VM

Post by masterofnone » 2021/06/16 09:39:29

Thanks for the hint with the corrupted iniramfs, this seemed to be the reason for the KP - I just did a "yum reinstall kernel-3.10.0-1160.31.1.el7.x86_64" and now the reboot is good and all is running well with the new Kernel Version.
Sorry for the cry for help - but i experienced this behaviour for the first time.

Post Reply