GURU_MEDITATION ERROR

[bharath]

Critical error has occurred while running the virtual machine and the machine execution has been stopped. guru meditation error appear in running oracle vm frequently & it is changing the VM state from 'RUNNING' to 'GURU_MEDITATION'. Plz tell me how to resolve this issue. Plz find the attached guru meditation error message.

[mpack]

Where is the log file that the dialog asks you to provide?

Minimum information needed for assistance.

[bharath]

Log file has been attached.

[mpack]

Grand. Now you only need to provide all of the other basic info asked for in the link. In particular I want to know what the guest OS is, including whether it's 32bit or 64bit.

It looks like you're attempting to install someone else's prepared VM (IPMPlus?)? If so, please explain the goal - I'm not sure I see the benefit of installing power management software inside a VM, or why you would choose FreeBSD 32bit as the base.

[bharath]

guru meditation error appear in running oracle vm frequently & it is changing the VM state from 'RUNNING' to 'GURU_MEDITATION'.

Plz tell me how to resolve this issue.

all the details in attached log file log file.

[mpack]

Please read my previous answers carefully, and provide the information requested.

[bharath]

Our guest OS is FreeBSD 9.1 32bit. IPMPlus is our own product.

We choose FreeBSD 32bit as the base, because IPMplus require 32bit OS & 2GB RAM.

For what reason guru meditation error message appear ?

[mpack]

The logged reason for the guru meditation is :-

131:10:52.622458 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
131:10:52.622462 !!
131:10:52.622462 !! Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
131:10:52.622485 !!
131:10:52.622538 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
131:10:52.622551 !!
131:10:52.622551 !! {mappings, <NULL>}
131:10:52.622553 !!

Some bugs along these lines have been fixed recently, so it may be worth your time to upgrade to 4.3.12. When I've seen this error before, other than as a bug, it was because (I believe) the user was attempting to install a 64bit OS in a 32bit VM. I know nothing about FreeBSD, so I can't tell if that applies here.

Note that FreeBSD has only limited support, for example with no Guest Additions, so it may be a poor choice anyway.

[bharath]

Ok we will upgrade to 4.3.12.

Thank you.