CentOS

I'm trying to install CentOS 9 Stream on a virtual machine on my computer, but I'm getting a "kernel panic not syncing fatal exception" error when it starts. I have downloaded the ISO twice to check to see if it's corrupted but I still have the same problem. I have numerous VMs installed that are working fine including Centos 8 and Debian 11.

I'm using VirtualBox 6.1.34. Host: Windows 10 Pro, Version 21H1, Build 19043.1706, 64Bit. i7-10700KF, 64GB RAM, NVIDIA GeForce GTX 1050 Ti, PRIME Z490M-PLUS Motherboard

I have the same problem.
Installation stuck on the end of kernel panic

I've not used CentOS Stream 9 as I don't see any point in it but I have installed RHEL 9.0 in a VBox VM successfully. If you sign up for a RH Developer subscription - which is free - you get a license to run up to 16 instances of RHEL of any version you like.

I had a similiar error. The error shows "Initramfs unpacking failed: XZ-compressed data is corrupt....Kernel panic". I redownload the image using default browser download and installed successfully instead of using software to download it. I suggest you test the media to see if there is any problem.

All of the mirrors carry text files containing sha256sums for the various iso images so that you can check if they are corrupted or tampered with without needing to run the media test. I would suggest using those to test your downloaded iso file before you attempt to use it at all.

Hi all

My centos 9 Stream was working fine until I updated virtualbox to VirtualBox-6.1.34a-150636-Win

No got exactly the same error on boot

Any idea hot to fix this?

Thanks in advance

Hi

Solved for me! Hyper-V was enabled in windows....

1- right-click the guest in the main Virtualbox window's guest list, choose Show Log.
2 - Search the far left tab's log for this text:

Attempting fall back to NEM


If you find it, Hyper-V is enabled in windows
See solution in https://forums.virtualbox.org/viewtopic ... 25&t=99390

Yes, the reason for the kernel panic was also due to Hyper-V being enabled. It has been disabled and now working fine. Thank you.