RedHat 8.3 not booting, RedHat 8.2 is fine

[e1011215]

RHEL 8.3 hangs early during boot, with the last message shown being "Mountpoint-cache hash table entries". This happens when booting from the RHEL 8.3 boot dvd iso, from the RHEL 8.3 binaries dvd iso, and from the kernel produced by upgrading an existing RHEL 8.2 system to RHEL 8.3 using a RHEL subscription.

RHEL 8.2 in the same VMs does not cause problems. The first message the successful boot shows after "Mountpoint-cache hash table entries" is "Last level iTLB entries" (these are messages on the console, when I remove the "quiet" option).

This is happening on Windows 10 Enterprise, with Virtualbox 6.1.16.

In the "Show Log" window, I see this as the last line (timing varies):
00:00:19.085407 MsrExit/0: 0010:ffffffffa6464d98/LM: WRMSR 00000033, 20000000:00000000 -> VERR_CPUM_RAISE_GP_0!

For both 8.2 (working) and 8.3 (not working), I have the green turtle in the status bar.

Hyper-V is disabled:
S C:\windows\System32> Get-Windowsoptionalfeature -online -featurename microsoft-hyper-v
Microsoft-Hyper-V
DisplayName : Hyper-V Platform
Description : Provides the services that you can use to create and manage virtual machines and their resources.
RestartRequired : Possible
State : Disabled
CustomProperties :

[elicro]

I have the same issue with both RHEL and Oracle Linux 8.3 on virtualbox 6.1.18.
It also works with Debian and Ubuntu but not RHEL and Oracle.
The same OS works fine under Hyper-v as the hypervisor.

Any hint on this?

[scottgus1]

e1011215, sorry we missed this one.

I have the green turtle in the status bar.

Hyper-V is disabled:

The green turtle means Hyper-V is still enabled despite the report from "Get-Windowsoptionalfeature".

elicro, you probably have the same trouble, since you report:

The same OS works fine under Hyper-v

I wonder if you left Hyper-V on? Do you have the green turtle?

Both, please see HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[Alvaro Palma]

Same issue here, happens with Hyper-V enabled and disabled.

Last working kernel is 4.18.0-193.28.1.el8_2.x86_64. All newer ones with el8_3 in the name fails.

[scottgus1]

Alvaro Palma, before you post on an existing topic, it is expected you'll try the suggestions and linked tutorials in the topic first.

[e1011215]

Redhat 7 works just fine with the green turtle on my laptop -- I couldn't be happier. However, the admins at work keep changing the many protection programs running on Windows (on my laptop), and I suspect some of them turn on Hyper V. For a while everything worked fine even with RHEL 8.3, now even 8.2 does not work at all -- but RHEL 7 still works.

Now this seems a RHEL question more than a Virtualbox question -- does anyone know of a way to get RHEL 8 past this? Maybe a boot-time option? It seems other distros work under these conditions, by and large.

[scottgus1]

e1011215, so far this may not be something RedHat et al can influence. Since the IT dept changes tings and breaks Virtualbox, let your boss know you're having a hard time working. The boss may get IT to set things up for you differently.