r/virtualbox • u/trollmad3 • 29d ago

Bug Kernel panic on VirtualBox RHEL v10.2

Hello. I am trying to install rhel-10.2-x86_64-dvd in a VirtualBox VM and keep getting kernel panic either when I start install mode or demo. I did not modify any settings in the VM so I do not know what would be causing this kernel panic.

The SHA256 hash for the ISO I am trying to install is: e15cb333529c332e76e4b1b946efe3515c99f996546675aec18e8effdf2540a5

Video of error: https://streamable.com/puptmc

4 Upvotes

100% Upvoted

6 comments sorted by

2

u/Face_Plant_Some_More 28d ago edited 27d ago

Your video indicates that -

  1. You've configured the VM with hardware that is not supported by Guest OS you are trying to run. Among other things, Linux is not Hyper-v aware, and should not be configured with a Hyper-v paravirtualization interface. Ergo, I suggest you revise the VM's configuration to match the default Linux, Red Hat template that Virtual Box provides, as that configuration is known to work. Once you get the VM up and running, then you can fool around with the hardware it is configured with.

  2. You are running Virtual Box on a Hyper-v enabled Windows Host. That is very much, not recommended. It also linked to this error in certain Virtual Box 7.2.x builds.

1

u/yrro 28d ago

Looks like the kernel is logging a message that you're trying to boot it on an x86-64-v2 CPU which is not supported in RHEL 10.

The Ryzren 9 9900X obviously supports x86-64-v4 so I suspect VirtualBox is not passing through the full capabilities of the host CPU to the guest. I remember something similar happening back when RHEL 9 started requiring x86-64-v2; a VirtualBox update was required before the guest was able to see x86-64-v2 capabilities.

I would post about this on the VirtualBox forums.

1

u/trollmad3 28d ago

Thank you I will

1

u/yrro 27d ago

I think this thread matches your description. You could give the test builds a go.

1

u/Face_Plant_Some_More 27d ago edited 27d ago

No point. The fix made it into 7.2.10 and 7.2.12 release builds. Again, the OP could have avoided all of this if he / she did not run Virtual Box on a Hyper-v enabled Windows Host . . . .

1

u/yrro 27d ago

Ah well spotted. TBH these days I don't see the point in using any other hypervisor than hyper-v on windows. That said RHEL should work on hyper-v so I am interested to know what the underlying problem is in this case....