Guru meditation error

[mcasperson]

I tried booting VirtualBox (7.0.4 r154605 linux.amd64) on my Ubuntu 22.04 system today and was greeted with a Guru Meditation error for previously functional VMs. Digging through the logs it appears the error is:

Code: Select all

00:00:01.292785 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:01.292798 Console: Machine state changed to 'Stuck'
00:00:01.293522 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:01.293523 !!
00:00:01.293523 !!         VCPU0: Guru Meditation -37 (VERR_NOT_SUPPORTED)
00:00:01.293527 !!
00:00:01.293539 !!
00:00:01.293539 !! {mappings, <NULL>}
00:00:01.293540 !!
00:00:01.293549 !!
00:00:01.293550 !! {hma, <NULL>}
00:00:01.293550 !!
00:00:01.293552 !!
00:00:01.293552 !! {cpumguest, verbose}
00:00:01.293554 !!

I've tried changing CPU and memory options, but nothing appears to work any more.

I have attached the full log to this post.

Is there anything I can do to get VirtualBox running again?

[multiOS]

The Log states:

00:00:01.123136 Oracle VM VirtualBox Extension Pack (Version: 6.1.38 r153438; VRDE Module: VBoxVRDP; Crypto Module: unusable because of 'VBoxExtPackVMRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='Helper version mismatch - expected 0x30000 got 0x50000'')

The first thing you need to do is update the Extension Pack to match your updated VirtualBox installation (7.0.4).

Please do that and check if the problem goes away. If not, then a new log will be needed after that update for further analysis.

[fth0]

The non-matching VirtualBox Extension Pack is ignored and only leads to unavailable functionality here. The actual problem is the following:

Another hypervisor (e.g. QEMU/KVM) is already running on the host, and VirtualBox cannot run a VM at the same time.

[multiOS]

@fth0,

Thanks for that. I hadn't looked further than the EP issue.

[fth0]

Thanks for that. I hadn't looked further than the EP issue.

You're welcome!

IME, Guru Meditation -79 and -37 are two possible consequences of QEMU/KVM running, that's why I immediately knew what to look for.

[mcasperson]

Interestingly the issue resolved itself. I can't point to anything I did that resolved the issue - not even an OS restart. But my VMs now work fine again.