VirtualBox

Opened 3 years ago

Closed 3 years ago

#20141 closed defect (fixed)

VERR_CPUM_RAISE_GP_0 when booting from CentOs8 => fixed in SVN/next maintenance

Reported by: JochenW Owned by:
Component: other Version: VirtualBox 6.1.16
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

Did the following (with Vb 6.1.18, not 6.1.16, the former version is not yet selectable):

  • Created a new VM CentOs8
  • Selected CentOS-8.3.2011-x86_64-dvd1.iso as the DVD drive.
  • Booted the machine. The Grub menu comes up, allowing me to select "Install CentOS Linux 8".
  • Virtual machines display goes black (as expected), but then the VM is frozen, and the installation kernel doesn't boot.

Attachments (3)

CentOS8.vbox (3.1 KB ) - added by JochenW 3 years ago.
Vbox definition file
VBox.log (82.0 KB ) - added by JochenW 3 years ago.
Log file
VBoxHardening.log (403.7 KB ) - added by JochenW 3 years ago.
VBoxHardening.log

Download all attachments as: .zip

Change History (15)

by JochenW, 3 years ago

Attachment: CentOS8.vbox added

Vbox definition file

by JochenW, 3 years ago

Attachment: VBox.log added

Log file

by JochenW, 3 years ago

Attachment: VBoxHardening.log added

VBoxHardening.log

comment:1 by JochenW, 3 years ago

It should be noticed, that booting from ubuntu-20.10-desktop-amd64.iso works. So, the guest OS might be able to provide a workaround here. (In the case of Linux, possibly by providing a suitable kernel.)

comment:2 by AlvaroPalmaAste, 3 years ago

I'm experiencing the same problem, but only with the el8_3 kernels. I've currently installed:

kernel-4.18.0-193.28.1.el8_2.x86_64 -> Works fine
kernel-4.18.0-240.1.1.el8_3.x86_64  -> Doesn't even boot
kernel-4.18.0-240.10.1.el8_3.x86_64 -> Doesn't even boot

comment:3 by JochenW, 3 years ago

@AlvaroPalmaAste: I understand, that you've got an installed VM, which you can boot, or not, depending on the selected kernel. If so: How did you get the VM installed? Using an older version of VirtualBox? Which?

comment:4 by paulson, 3 years ago

Status: newawaitsfeedback

This issue would have been best addressed in the forums where users from all over the world can chime in rather than just the smaller audience of the VirtualBox development team.

You are running Windows on your host system:

00:00:10.878761 OS Product: Windows 10
00:00:10.878761 OS Release: 10.0.19041

and your log reports the following:

00:00:11.350342 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available

which indicates Microsoft's Hyper-V is active so review the following post in the forums:

HMR3Init: Attempting fall back to NEM (Hyper-V is active)
https://forums.virtualbox.org/viewtopic.php?f=25&t=99390

and follow the advice there to disable Hyper-V on your system.

comment:5 by JochenW, 3 years ago

I have that post carefully. Unfortunately, completely disabling Hyper-V is not an option for me, because I need to be able to run the Docker Desktop.

comment:6 by JochenW, 3 years ago

Status: awaitsfeedbacknew

comment:7 by raidenz, 3 years ago

I am having the EXACT same issue. Running Virtualbox 6.1.18 on the latest Windows 10 Pro and I have docker Desktop also installed. Trying to install CentOS 8.3 iso and it freezes during kernel loading. I even tried the latest CentOS 8 stream [CentOS-Stream-8-x86_64-20210204-dvd1.iso] and it freezes during kernel initialization. [Shows green turtle icon when Hyper-V is enabled].

If I run a custom made linux distro [running linux kernel 5.10.13], it boots without an issue.

It's only if I disable Hyper-V and reboot and re-run Virtualbox, CentOS 8 or CentOS Stream works without any issue [no green turtle icon]. I would love to see this get fixed in Virtualbox. [I do not want to disable Hyper-V since we need docker]

MsrExit/0: 0010:ffffffffbb864d98/LM: WRMSR 00000033, 20000000:00000000 -> VERR_CPUM_RAISE_GP_0!

Last edited 3 years ago by raidenz (previous) (diff)

comment:8 by aeichner, 3 years ago

Summary: VERR_CPUM_RAISE_GP_0 when booting from CentOs8VERR_CPUM_RAISE_GP_0 when booting from CentOs8 => fixed in SVN/next maintenance

This will be fixed in the next maintenance release. Please try the latest 6.1 testbuild from here.

comment:9 by JochenW, 3 years ago

I tried the latest 6.1 testbuild. See #20177 for the result.

comment:10 by raidenz, 3 years ago

I tried the latest 6.1 build (142673) and it now works.

comment:11 by Cito, 3 years ago

Had the same problem with 6.1.18 and WSL 2 and can confirm it now works with 6.1.19-142995.

comment:12 by aeichner, 3 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use