virtualbox.org

Hi everyone,

I am currently experiencing persistent problems in getting both Ubuntu and Opensuse Linux guests to boot (more than once) on my new laptop.

Every time I boot up the virtual machine the machine starts, shows some initial loading screens and then ends up at a black screen with a cursor for Ubuntu and at "Loading initial ramdisk" for OpenSuse.

General machine settings in short:
4 CPU cores (8 @ Host)
4096MB RAM (32GB @ Host)
128MB Video Memory

Both machines exhibit the same error message shortly before or at the point of halting:

Ubuntu (including first messages of the shutdown)
00:00:12.485939 PIT: mode=2 count=0x12a5 (4773) - 249.98 Hz (ch=0)
00:00:12.501888 MsrExit/0: 0010:ffffffff9fc788e8/LM: RDMSR 00000140 -> 00000000 / VERR_CPUM_RAISE_GP_0
00:00:19.372376 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:00:19.372473 AIOMgr: Async flushes not supported

Opensuse (running - last message at the point of the halt)
00:00:10.301733 GIM: KVM: VCPU 0: Enabled system-time struct. at 0x0000000022c01000 - u32TscScale=0xde38b003 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x0 uVirtNanoTS=0x0
00:00:10.301749 TM: Host/VM is not suitable for using TSC mode 'RealTscOffset', request to change TSC mode ignored
00:00:11.566797 GIM: KVM: Enabled wall-clock struct. at 0x0000000022c00000 - u32Sec=1601380269 u32Nano=219061100 uVersion=2
00:00:11.567082 PIT: mode=2 count=0x12a5 (4773) - 249.98 Hz (ch=0)
00:00:11.582027 MsrExit/0: 0010:ffffffffa7a765f6/LM: RDMSR 00000140 -> 00000000 / VERR_CPUM_RAISE_GP_0

I tried googling for any description of the error but the results were a bit cryptic.

I attach two log files for two virtual machine images that I downloaded - virtual machines that were installed by myself show the same behavior.

I would really appreciate any indication as to what settings I need to change / what I need to fix to get them running on the new hardware. The old laptop always worked absolutely fine with Virtualbox

Thank you in advance!

Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

Thank you so much - this fixed the issue

I apologize for not recognizing this as a common problem ... I never had any issue in this regard despite using probably half a dozen PCs with Virtualbox

MK866 wrote:I apologize for not recognizing this as a common problem

No problem. I borrowed scottgus1's standard answer to answer in his place, because you maybe distracted him with naming the error code (VERR_CPUM_RAISE_GP_0).

Seriously, it's good to have the error code in the title, for other people to find in the future Google searches.