virtualbox.org

I use virtual software that was purchased about a couple of years ago to run a help ticketing system. Recently, the Virtualbox will stop working giving me the Guru Meditation error and I have to restart the virtual software to get it back up and running. I contacted the company the software was purchased from, and they said it was an issue with Virtualbox. I've attached the log files for the issue.

Any help would be appreciated!

Thanks

Was this software always run on the same host?

VBox.log wrote: 00:00:01.496967 Guest OS type: 'Ubuntu'
00:00:01.499136 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.
...
00:00:01.683951 RamSize <integer> = 0x00000000c0000000 (3 221 225 472, 3 GB)

**************************

48:06:06.431535 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
48:06:06.431537 !!
48:06:06.431537 !! Guru Meditation -2403 (VERR_TRPM_DONT_PANIC)
48:06:06.556493 !!
48:06:06.577758 !! TRAP=0e ERRCD=0000000000000002 CR2=0000000000000010 EIP=fe44f783 Type=0 cbInstr=ff

The log also shows a long sequence of suspend/resumes, not something I like to see. I suggest that you fully shut down the VM, and reboot (complete power off) your host before starting the VM again.

And a long snapshot list too? Also not a great idea IMHO.

I'm puzzled why VBox thinks this a 64bit VM. I'm thinking it might be because you have such a large RAM allocation to the VM - but in that case this VM can never have worked on this host, at least not with any recent VBox version. I would try reducing the RAM allocation in the VM to 1.5GB.

Thank you for the feedback mpack. To answer your questions:

mpack wrote:Was this software always run on the same host?

As far as I'm aware. The software is installed on our dedicated web server, which is running Windows Server Enterprise 64 bit.

mpack wrote:And a long snapshot list too? Also not a great idea IMHO.

What would be your recommended maximum number of snapshots? I contacted the software company about 8 months ago asking them about snapshots. They recommended to take snapshots, but never said there should be a maximum number of them.

mpack wrote:I'm puzzled why VBox thinks this a 64bit VM. I'm thinking it might be because you have such a large RAM allocation to the VM - but in that case this VM can never have worked on this host, at least not with any recent VBox version. I would try reducing the RAM allocation in the VM to 1.5GB.

As far as reducing the RAM allocated to the VM, I do not have the knowledge to do that. The software company installed and set up the software within the VM, so I only know a few things about the software as problems have risen and I've learned how to solve them after contacting the software company.

You should enable VT-x, in the BIOS. The VirtualBox software virtualization is rather unstable.
If it is enabled, disable Hyper-V: viewtopic.php?f=6&t=41258#p236620

GRDHD wrote:As far as reducing the RAM allocated to the VM, I do not have the knowledge to do that. The software company installed and set up the software within the VM, so I only know a few things about the software as problems have risen and I've learned how to solve them after contacting the software company.

As I gather, you are launching this VM on a mixture of different hosts from a server location, writing logs back to the server - that would be why the log is so confused. To compound this you are also using saved states a lot.

VMs are not totally portable between hosts - you can't just totally ignore the resources available to the host that the VM is launched on. That wouldn't be less of a problem if the VM used conservative settings, but it doesn't. In particular it uses an unnecessary amount of RAM. To fix it you just launch the VirtualBox manager GUI and change the settings. However, I don't know that caused the original crash, it was just an anomaly visible in the log.

I don't really know what else to tell you. I wouldn't use a VM this way, and if I did I wouldn't use these settings or saved states.