Opened 4 years ago
Closed 4 years ago
#20254 closed defect (fixed)
VERR_CPUM_RAISE_GP_0 error with Virtualbox 6.1.18 and HypervisorPlatform/WSL2 enabled on some CPUs
Reported by: | mictaege | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 6.1.18 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
In order to use WSL2 I enabled HypervisorPlatform and VirtualMachinePlatform with the following commands:
Dism /online /Enable-Feature /FeatureName:HypervisorPlatform /All Dism /online /Enable-Feature /FeatureName:VirtualMachinePlatform /All
After a reboot I wasn't able to boot existing Virtual Machines or to create new ones anymore. After GRUB was loading fine, the machine gets stuck with a black screen and a blinking cursor. At this time the last entry in the VBox.log file of the machine was:
MsrExit/0: 0010:ffffffffb9c6dc97/LM: RDMSR 00000140 -> 00000000 / VERR_CPUM_RAISE_GP_0
This happend in the same way with a variety of different Linux guests both with newer and older kernels: Oracle Linux 7, Ubuntu 20.04 LTS, Ubuntu 20.10, Ubuntu 18.10
Trying VB 6.1.19 r142995 doesn't help. Although there was no longer a VERR_CPUM_RAISE_GP_0 error, but the VMs run with extremely poor performance (e.g. boot time up to 5m)
After many tries I found that that these problems only occur on my notebook with a i9-10885H CPU @ 2.40GHz CPU but not on another notebook with a i7-1065G7 CPU @ 1.30GHz CPU. On the notebook with the i7 CPU VB 6.1.18 worked very well together with HypervisorPlatform, VirtualMachinePlatform and WSL2 enabled. Even the performance of the VM was very good.
Attachments (1)
Change History (4)
by , 4 years ago
comment:1 by , 4 years ago
comment:3 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
sorry for adding the log file accidentally twice