How to read VBOX.LOG file

[lyates]

My Centos guest install continually crashes on a Centos host.
I'd like to learn how to read the log file to determine the cause.

Are there any guidelines available for interpreting the log?

My log file is rather large:

The file is too big, maximum allowed size is 128 KiB.

...and I'd rather do it myself

I've attached a ZIP copy of my lastest crash vbox.log file.

Thanks!
-Larry

[Perryg]

Did this crash happen in a previous version of VirtualBox?
You might consider creating a ticket in bugtracker (link is below my post). You will need to setup an account there as well and please post the ticket number and results here so others can benefit from this.

[lyates]

Did this crash happen in a previous version of VirtualBox?
You might consider creating a ticket in bugtracker (link is below my post). You will need to setup an account there as well and please post the ticket number and results here so others can benefit from this.

I am using version 3.0.10.

Actually, I'd prefer to interpret the VBOX.LOG file myself.
Are there any guidelines, tips, hints on what to look for in the log?
...or how the log file is organized?

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!
!!                 Guru Meditation -2403 (VERR_TRPM_DONT_PANIC)
!!
!! TRAP=0e ERRCD=0000000000000000 CR2=000000005ec00000 EIP=5ec00000 Type=0
!! EIP is not in any code known to VMM!
!!
!!
!!

[Perryg]

Just Google.com
It stems from the old Amiga days indicating a *nix panic.
Have a search and go for it. You still should post it if you want to get it fixed though. That's the only way to stop the crashes AFAIK.

[lyates]

Hey!
How about a "structure and contents" of the VBOX.LOG file?
...please?

-Larry

[Perryg]

Sorry I don't have it. I know what about 50% of it is doing and saying but to get the rest or get it fixed you will need to go to the DEVs!
Posting this on bugtracker is the fastest way to get it fixed.

[sandervl]

You're using the wrong 3.0.10. Download again please. There was a respin of the binaries due to a last minute regression (the one you see).