virtualbox.org

My VM has recently begun crashing (comes up with the termination screen with the pic of some sort of guru on it). It has happened before but recently it happened a few times in a row when I tried to open the terminal window. The screen suggested I come here and share my log file to see if anyone can help, I have no idea what part of the log is relevant so here is the last few lines...

00:02:22.424946 NAT: zone(nm:mbuf_cluster, used:0)
00:02:22.426011 NAT: zone(nm:mbuf_packet, used:0)
00:02:22.426028 NAT: zone(nm:mbuf, used:1)
00:02:22.426043 NAT: zone(nm:mbuf_jumbo_pagesize, used:0)
00:02:22.427023 NAT: zone(nm:mbuf_jumbo_9k, used:0)
00:02:22.427521 NAT: zone(nm:mbuf_jumbo_16k, used:0)
00:02:22.427805 NAT: zone(nm:mbuf_ext_refcnt, used:0)
00:02:22.488673 Changing the VM state from 'DESTROYING' to 'TERMINATED'.

I'm at the stage where the VM will boot but I can't do anything with it as it just crashes.

Windows 8 is the host, Ubuntu is the guest...

I've attached the whole log file. It seems like I might have been allocating way too much RAM, does that sound feasible?

I think you clicked wrong somewhere - there is no log file
The part you've pasted doesn't tell us anything btw.

hi there

same prob. here, guru meditation say:
a critical error as ocurred while running the virtual machine and the machine execution has been stoped.
for help please see the comunity section to.......

this is the last part of the log file:
Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'.
00:00:39.179980 VMR3Suspend:
00:00:39.180028 RUNNING -> SUSPENDING, RUNNING_LS -> SUSPENDING_EXT_LS failed, because the VM state is actually GURU_MEDITATION
00:00:39.180066 VMSetError: D:\tinderbox\win-4.2\src\VBox\VMM\VMMR3\VM.cpp(3491) int __cdecl vmR3TrySetState(struct VM *,const char *,unsigned int,...); rc=VERR_VM_INVALID_VM_STATE
00:00:39.180093 VMSetError: VMR3Suspend failed because the current VM state, GURU_MEDITATION, was not found in the state transition table
00:00:39.188657 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={Could not suspend the machine execution (VERR_VM_INVALID_VM_STATE)}, preserve=false

win 8 and kali linux in VM.

any idea will be aprechate.

If no one posts the complete log file (as an attachment) no one will be able to help. Period.

Perryg wrote:If no one posts the complete log file (as an attachment) no one will be able to help. Period.

the file in attachment is too big
ok.

You must be a member for 1 days and have 1 posts before you can post urls.


mediafire(DOT)com/ ?r1te8tsvhwbf3o7

regards

It can't be too big *if* you compress it.

Same here.
the log is attached.

explorerv wrote:Same here.
the log is attached.

error_Kali_on_VB.zip

I'm fairly certain that the on screen message also told you what to do to fix this. Enable PAE in the guest setting

Thanks Perryg!

In fact on the first error screen I was advised to collect the logs and leave by choosing OK.
Only when I followed your comment and continued with "Ignore" I found the second screen:
Cheers!

I m using windows 10 and virtual box 4.3.12.
The git bash is showing the following error below in the image when "vagrant up". The virtual box is running well when started manually.
Help me out with the solution .

First the error mentioned says you need to enable PAE in the guest setup.
Next we don't support vagrant here so that does not help.
Finally Windows 10 is not fully supported yet. Some things work but others don't.