Daily crashes with Vbox 4 - Win7-64 on OSOL134

[bayoda]

Hi

My 3.2.12 Virtualbox was really stable. No Crashes at all.
I installed VBox 4 on OSOL 134 some days ago (when it was available) and since this time:
Every morning I came to the office - my Win7-64 is gone. Hard Crash / freezed - doesn't mather - it's away...

I attach the VBoxLog here maybe it helps - tried every thing to "turn" but nothing really helped...

Maybe some other has the same problem and know how to fix it? or is downgrade the only possbility

greetings

Michael

[Alekz]

I have exactly the same problem. Win7 freezes, but "top" shows very high CPU usage (from 30% to 48%). No "resets" work. The only solution is to kill all VB processes and start again.

[garyd]

I have the same problem with Solaris 11 Express 11/10. Usually my first step to troubleshoot such issues is to turn off VT-x/AMD-V but when you're running a 64-bit guest that's apparently not an option. I'm tempted to install a 32-bit version of Windows to see if that helps. Has anyone had similar issues with it? What kind of host hardware are you using? I'm running on an aging Sun Ultra 20 workstation but it's got four gigabytes of RAM with two dedicated to my guest. My crashes happen much more often than daily, however.

-Gary

[gerard]

I have the same problem on redhat 5.5. Any solutions?
I running win 64 2008 R2.

[Alekz]

The high processor utilization has been fixed by reducing the amount of CPU's from 4 to 1. But Windows freezes every 30min. To restart it all VBox processes need to be killed.

[tomwaters]

Same here on solaris 11 express with latest vbox. Running headless guests, server 2008r2 and centos 5.5.

Strange thing is that box thinks it's still in running state, but can not connect or even ping the machine.

Need to kill the process...not happy. Sometimes it happens to one vm, sometimes all 3 vm's. Vm's may run a day, or 3 before freezing.

Did not have the issue with opensolaris 111b 2009.06

What do you need to help debug this...or should we submit a bug report to get some support?

[tomwaters]

I have raised a bug here http://www.virtualbox.org/ticket/8294

This is getting freaking annoying. I wish I could run VMware on Solaris.

Looks like I'll be reverting back to OpenSolaris 2009.06...at least my VM's ran for more than a day before hanging.

[pbeltranl]

Hi,

I upgraded from the last 3.x version to the last 4.x. Then, I noticed that:

I could work without any problem, but after a pause (do nothing on my laptop)... Virtualbox was crashed. So, I disabled all the powersave features (screen & HD) on my guest OS (Windows 7) and it runs stable forever since that.

Hope this helps.

My host OS is Ubuntu 10.10 (maverick).

[tomwaters]

Thanks for this pbeltranl, really appreciate the help.

Coincidently, I changed my power saving (disk, usb etc. all on all the time) and screen saver settings in the win7 vm's two days ago and have not had a "freeze" yet...normally it would have by now. Fingers crossed that is the issue.

Strange as it did not happen on v 3.12

Rather annoying in one way though...as I have a support ticket open, and set the vm's up for a core dump so can send it to the oracle guys....

[tomwaters]

Hmmm...may be related to power management...found this on the Linux forum...
" Since 4.0, there are some more ACPI options available and when you have the GA installed, they become enabled in the VM OS. Open the Guest OS power management and disable the actions for hibernate and suspend."

Looking more likely and explains why it appeared under 4.0.2....as I was rev running 3.12 in opensolaris 2009.06

[tomwaters]

I guess there is another issue as it just crashed...all 3 vm's went out...the win2k ones first, then the centos one.

Have sent the core dump to oracle.

On the bright side...it did last 4 days this time

[pbeltranl]

me too just now!

My case:

I've upgraded my Ubuntu 10.10. I paused to work on my laptop for a while... and my VirtualBox 4.0.2 was crashed again! So I guess it has happened because the OS upgrade this time. So I will try to re-build my virtual box (sudo /etc/init.d/vboxdrv setup) and I think it will fix the problem. I'll come back again if not.

[tomwaters]

I am trying 3.12 now...if that crashes, or frank is not able to decypher the issue from the core dumps, I am done.

I went solaris as a stable vm platform, and while i love Solaris, 0-4 days uptime for the VM's is just not going to work for me.

ESXi is looking like my next step.

[pbeltranl]

The new 4.0.4 version fixes this bug:

http://www.virtualbox.org/ticket/8131

[tomwaters]

Thanks for that. I am very hopeful this will resolve my issues. Will try the new release and post back with how it goes.

(Note: 3.12 seems to work ok, but only ran it for 2 days before I had to take down the server so not 100% sure it's not happening under 3.12).