Guru Meditation -4014 (VERR_VMX_INVALID_GUEST_STATE)

[useResa]

Some background info:
Host: Ubuntu 11.10 - Kernel: 3.0.0-17-generic-pae
Guest: Windows 7

Today I upgraded VirtualBox to VirtualBox 4.1.12 r77245 linux.x86 (after having performed the initial upgrade to 4.1.12 yesterday).
With this upgrade I today encountered a Guru Meditation critical error which I have not experienced ever before.
Somewhat surprised since the initial statement on the release notes for 4.1.12 is regarding Guru Meditation albeit with other error messages.

Please find below some snippets from the log, which can be provided when needed.
Basic info:

Code: Select all

00:00:02.050 Log opened 2012-04-04T08:24:05.144397000Z
00:00:02.050 OS Product: Linux
00:00:02.050 OS Release: 3.0.0-17-generic-pae
00:00:02.050 OS Version: #30-Ubuntu SMP Thu Mar 8 17:53:35 UTC 2012
00:00:02.050 DMI Product Name: Latitude E6400                  
00:00:02.050 DMI Product Version: 
00:00:02.051 Host RAM: 4019MB RAM, available: 3415MB
00:00:02.051 Executable: /usr/lib/virtualbox/VirtualBox
00:00:02.051 Process ID: 7172
00:00:02.051 Package type: LINUX_32BITS_UBUNTU_11_10
00:00:02.081 Installed Extension Packs:
00:00:02.082   Oracle VM VirtualBox Extension Pack (Version: 4.1.12 r77218; VRDE Module: VBoxVRDP)

The beginning of the error (I assume):

Code: Select all

02:11:40.337 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
02:11:40.337 !!
02:11:40.337 !!                 Guru Meditation -4014 (VERR_VMX_INVALID_GUEST_STATE)
02:11:40.345 !!
02:11:40.345 !!
02:11:40.345 !! {mappings, <NULL>}
02:11:40.345 !!

The actual error (?):

Code: Select all

02:11:40.399 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
02:11:41.406 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'.
02:25:29.045 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={Invalid machine state GuruMeditation when checking if the guest entered the ACPI mode)}, preserve=false
02:25:31.276 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
02:25:31.276 Changing the VM state from 'GURU_MEDITATION' to 'POWERING_OFF'.
02:25:31.276 ****************** Guest state at power off ******************

Main questions:
1. Could the above be related to the latest upgrade?
2. Is there something I can do to prevent the error from happening again?
3. Is more information required?

[mpack]

"Guru Meditation" is an error reporting mechanism. It should be no surprise that it accompanies any error message.

Anyway, your message probably means that you upgraded VirtualBox while the VM was in a saved state instead of fully shut down. Always an unwise gamble.

The only cure would be right clicking on the VM (in the UI) and choosing "Discard saved state".

[useResa]

"Guru Meditation" is an error reporting mechanism. It should be no surprise that it accompanies any error message.

Thanks ... Makes sense indeed

Anyway, your message probably means that you upgraded VirtualBox while the VM was in a saved state instead of fully shut down. Always an unwise gamble.

Is there a way I can check this? I am running on a laptop and I am 99% certain that all VMs were shut down since my laptop was fully switched off before the upgrade.

The only cure would be right clicking on the VM (in the UI) and choosing "Discard saved state".

Well I simply closed (powered off) the VM and restarted. Until now it seems to be running fine.

What was the case is that I went for a lunch break and it occurred during that break. Could long(er) inactivity may have caused this?