Guru meditation from XP P2V Project

[halasjani]

Hi!
I have a similar problem.
I made a VHD file from a hardware faulty Windows XP disk.
I'm giving this VHD to a new Virtual Machine.
The machine only starts in safe mode, I get a Guru Meditation error during normal startup. I installed the integration features in safe mode, but it didn't help. Can you help me with what the problem might be and in what direction should I try to solve it?

Thanks for the help, I attach the log file.

[mpack]

I split your post from the 2018 topic you posted in, which really bore no resemblance to your problem.

First things first, you have the wrong extension pack installed.

VirtualBox VM 5.2.44 r139111 win.amd64 (Jul 9 2020 19:02:39) release log
...
00:00:02.457715 Oracle VM VirtualBox Extension Pack (Version: 6.1.4 r136177; VRDE Module: VBoxVRDP unusable because of 'VBoxExtPackVMRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='Helper version mismatch - expected 0x3 got 0x10002'')

Next up, 18MB is not enough graphics RAM.

00:00:02.653151 VRamSize <integer> = 0x0000000001200000 (18 874 368, 18 MB)

Then there is the guru error message:

00:01:02.469048 Console: Machine state changed to 'GuruMeditation'
00:01:02.469281 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:02.469282 !!
00:01:02.469282 !! VCPU0: Guru Meditation -2301 (VERR_REM_VIRTUAL_CPU_ERROR)
00:01:02.469307 !!
00:01:02.469341 !!
00:01:02.469341 !! {mappings, <NULL>}

This one is a bit puzzling, since at first glance it seems to be saying that something else is using VT-x... but VirtualBox 5.2.44 doesn't insist on VT-x being available, and at first glance I'm not seeing any setting that requires it. It might have something to do with using that 6.1.x extension pack, since 6.1.x does require VT-x for all VMs.

However, I suspect the error will go away if you fix the settings problems mentioned above and enable VT-x in the host BIOS and in the VM settings.

Is there a particular reason that you installed such an old version of VirtualBox?

[fth0]

FWIW, the VirtualBox Extension Pack is not used when VBoxExtPackVMRegister() returns an error.

The error code VERR_REM_VIRTUAL_CPU_ERROR indicates that VirtualBox used software virtualization (Recompiled Execution Manager mode). I'm not sure how to recognize if the VM has been deliberately configured not to use VT-x/AMD-V from the log messages (and I'm too lazy to search for it in the obsolete VirtualBox 5.2 sources).

[mpack]

FWIW, the VirtualBox Extension Pack is not used when VBoxExtPackVMRegister() returns an error.

I wouldn't want to lay bets on how predictably the API behaves when there's such a version mismatch, particularly when the extpack is so much newer.

I'm not sure how to recognize if the VM has been deliberately configured not to use VT-x/AMD-V from the log messages

It has been so configured. "HMEnabled = 0" on line 35.

[fth0]

I'm not sure how to recognize if the VM has been deliberately configured not to use VT-x/AMD-V from the log messages

It has been so configured. "HMEnabled = 0" on line 35.

Thanks for the hint. I knew that HMEnabled is 0 when the VM has been deliberately configured not to use VT-x/AMD-V. What I'm not sure about is the following:

If VT-x is enabled in the VM configuration and VirtualBox 5.2 discovers that VT-x is not available, does it automatically switch to software virtualization or does it error out? In case of the former, does it also set HMEnabled to 0?

[mpack]

Sorry, 5.2.x was too long ago for me to be certain about my failing memory.