(Help) VirtualBox critical error

[OoOCountDraculaOoO]

I get this error when I try to start VirtualBox and run Kali Linux. This is my first time attempting this please explain how I can fix this as simple as possible. I'm a noob. I have been following this youtube tutorial.

youtube.om/watch?v=tvpDMZlqMjA

VirtualBox- Guru Meditation
A critical error has occurred while running the virtual machine and the machine execution has stopped.

For help, please see the Community section on virtualbox.rg or your support contract. Please provide the contents of the file VBox.log and the image file VBox.png, which you can find in the C:\Users\VirtualBoxVMs\Kali\Logs directory, as well as a description of what you were doing when this error happened. NOte that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window.

Press OK if you wan to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now.

Here is the log info and my system specs:



VirtualBox VM 4.3.10 r93012 win.amd64 (Mar 26 2014 18:53:57) release log
00:00:01.518739 Log opened 2014-04-04T01:41:59.019621400Z
00:00:01.518741 Build Type: release
00:00:01.518745 OS Product: Windows 7
00:00:01.518747 OS Release: 6.1.7601
00:00:01.518749 OS Service Pack: 1
00:00:01.533003 DMI Product Name: UL50VT
00:00:01.537687 DMI Product Version: 1.0
00:00:01.537697 Host RAM: 6109MB total, 4316MB available
00:00:01.537700 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:01.537701 Process ID: 4836
00:00:01.537702 Package type: WINDOWS_64BITS_GENERIC

............

00:00:32.824808 early console in decompress_kernel
00:00:32.824823
00:00:32.824838 Decompressing Linux... Parsing ELF... No relocation needed... done.
00:00:32.824853 Booting the kernel.
00:00:32.824869
00:00:32.824884
00:00:32.824899
00:00:32.824915
00:00:32.824930
00:00:32.824945
00:00:32.824960
00:00:32.824975
00:00:32.824991
00:00:32.825006
00:00:32.825021
00:00:32.825037
00:00:32.825052
00:00:32.825067
00:00:32.825082
00:00:32.825098
00:00:32.825113
00:00:32.825128
00:00:32.825143
00:00:32.825159
00:00:32.825175
00:00:32.825190 --------------------------------------------------------------------------------
00:00:32.825204 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:32.825218 emR3Debug: rc=VERR_DEADLOCK
00:00:33.825325 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'.
00:00:33.827675 VMR3Suspend:
00:00:33.827701 RUNNING -> SUSPENDING, RUNNING_LS -> SUSPENDING_EXT_LS failed, because the VM state is actually GURU_MEDITATION
00:00:33.827741 VMSetError: D:\tinderbox\win-4.3\src\VBox\VMM\VMMR3\VM.cpp(3443) int __cdecl vmR3TrySetState(struct VM *,const char *,unsigned int,...); rc=VERR_VM_INVALID_VM_STATE
00:00:33.827780 VMSetError: VMR3Suspend failed because the current VM state, GURU_MEDITATION, was not found in the state transition table
00:00:33.827830 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Could not suspend the machine execution (VERR_VM_INVALID_VM_STATE)}, preserve=false

[Perryg]

Post the complete guests log file ( as an attachment )

[mpack]

... preferably zipped.

[OoOCountDraculaOoO]

Okay, here is the file zipped. Thank you for helping me btw.

[mpack]

00:00:32.820192 Console: VM runtime error: fatal=true , errorID=PAEmode message="The guest is trying to switch to the PAE mode which is currently disabled by default in VirtualBox. PAE support can be enabled using the VM settings (System/Processor)"

Also, I see you have the 32bit Debian template selected, please confirm that it was a 32bit guest you installed? Also you have IO-APIC disabled which may be unusual in a modern guest.

Finally, a reminder that Kali is not officially listed as a supported guest.

[WheatGrass]

Thank you. Enabling PAE support was the solution for me.

I was running Debian GNU/Linux, with Linux 3.2.0-4-486 but couldn't get the "Linux 3.2.0-4-686-pae" to run.
I upgraded VirtualBox from v4.3.20 r96997-Win to v4.3.26 r98988 with the same result.

Enabling PAE support was the solution. I'll try to pay more attention to the kernel name next time.

00:00:32.820192 Console: VM runtime error: fatal=true , errorID=PAEmode message="The guest is trying to switch to the PAE mode which is currently disabled by default in VirtualBox. PAE support can be enabled using the VM settings (System/Processor)"

Also, I see you have the 32bit Debian template selected, please confirm that it was a 32bit guest you installed? Also you have IO-APIC disabled which may be unusual in a modern guest.

Finally, a reminder that Kali is not officially listed as a supported guest.