AlmaLinux/RedHat 9 not installing on VirtualBox 6.1.36 (kernel panic)

[Alvaro Palma]

I tried to install both AlmaLinux and RedHat 9 over VirtualBox 6.1.36 running on a Windows 10 (v10.0.19044) machine (i7-6600U), with Hyper-V enabled and disabled, it always fails with a kernel panic.

Attached are the VBox logs and the output of the failed installation.

This same setting works fine in AlmaLinux 8.

[mpack]

In fact Hyper-v is enabled.

00:00:05.389152 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:05.477456 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:05.477558 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

How were you disabling it?

[Alvaro Palma]

Using Control Panel -> Programs and Features -> Enable or disable Windows features -> Remove Hyper-V from the list and reboot.

I tried both cases, Hyper-V enabled and disabled, both failed. And more curious, AlmaLinux 8 works fine even with Hyper-V enabled.

Regards.

[Alvaro Palma]

Actually, an update: Disabling the Hyper-V feature from the Control Panel -> Programs and Features DOESN´T WORK.

Once I followed the instructions from viewtopic.php?f=25&t=99390, that really disabled Hyper-V and I was able to install and run AlmaLinux9.

However, it would be nice to be able to run it with Hyper-V enabled, as AlmaLinux8 runs with it with no issue, although, to be honest, this could easily be an issue of AlmaLinux instead of VirtualBox.

[Alvaro Palma]

Indeed, it seems to be an AlmaLinux issue, not a VirtualBox one:

https://almalinux.discourse.group/t/ker ... stall/1379

[scottgus1]

Disabling the Hyper-V feature from the Control Panel -> Programs and Features DOESN´T WORK.

True. There's lots of things that use Hyper-V besides "Hyper-V". Glad you kept up the hunt and found a solution!

[fth0]

Thanks for sharing the information you've found. I suspect that you helped us discover a VirtualBox bug.

If you like to be adventurous, enable Hyper-V again and try if the following command helps:

Code: Select all

VBoxManage setextradata "VM name" "VBoxInternal/CFGM/IsaExts/POPCNT" "1"

[/s]
Edit:
Damn it, that happens when you type instead of copy!

Please try the following command instead:

Code: Select all

VBoxManage setextradata "VM name" "VBoxInternal/CPUM/IsaExts/POPCNT" "1"

If it does not help, and only then, additionally try:

Code: Select all

VBoxManage setextradata "VM name" "VBoxInternal/CPUM/IsaExts/POPCNT" "2"