VirtualBox VM crashes with rc=VERR_NEM_IPE_3

[olsztyniak]

I started to have strange problem wit all VMs in my VirtualBox VirtualBox-6.1.16-140961-Win>
The VM seems to be starting ok until it gets to starting LSB.
The message is:
00:01:15.068290 Starting LSB: QEMU KVM module loading script...
00:01:15.068303 [ OK ] Started Dispatch Password Requests to Console Directory Watch.
00:01:15.068319 [ 16.986761] intel_rapl: no valid rapl domains found in package 0
00:01:15.068336 [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
00:01:15.068352 [ OK ] Started LSB: QEMU KVM module loading script.
00:01:15.068386 --------------------------------------------------------------------------------
00:01:15.068400 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:15.068426 emR3Debug: rc=VERR_NEM_IPE_3

and it fails.
---------------------------------------
Problem is that VirtualBox and WSL2 cannot work together on Windows 10.
Oracle should look into this issue and make VirtualBox work together with WSL2

[scottgus1]

VirtualBox and WSL2 cannot work together on Windows 10.

Very true. If Hyper-V-based services are enabled, very often Virtualbox is upended. The devs are working on running Virtualbox under active Hyper-V. It has been a hard battle and the fighting isn't over yet.

See I have a 64bit host, but can't install 64bit guests.

https://www.tenforums.com/tutorials/139 ... puter.html has a way to toggle Hyper-V on & off at boot.

To see if something using Hyper-V is active, right-click the VM in the main Virtualbox window's VM list, choose Show Log.

Search the far left tab's log for this text:

Attempting fall back to NEM

If you find it, Hyper-V is enabled and needs to be disabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).