virtualbox.org

Mac OSX 10.7.2, 12GB RAM, intel Mini mid-2011.
This was the day to experiment and see if going from 8GB to 12 GB of RAM improved things.
I'd had lots of kernel panics with 4.1.4 and downgraded to 4.0.14 a few weeks ago. That seemed stable.

Yesterday, I uninstalled VBox 4.0.14 and installed 4.1.8.
One guest VM (Windows 7 Pro 64-bit) ran ok overnight.
Two ran OK for a few hours, opening and closing one or the other off and on.
I tried three VMs, they worked OK but for one 'Aborted' after closing, for a few hours
Later, as I tried closing one of those, I immediately got a localhost crash.
Looking at the Console, the first 'Aborted' session was also a localhost crash.

Today, with two Windows VMs open, and VBoxManager open, I was just looking at the Network settings for a third VM that was not operating.
In the background I saw one of the working VMs' status change to Aborted in the VBoxManager window.

Don't know if the reports will help anyone but I'm attaching them.
------ -----
I'm going to either use just a single VM at a time, or go back to 4.0.14 --depending on what my coworkers need me to do this week.

Another pair of crash reports; ran a single VM without problems, ran two VMs open at the same time without problems, and what appeared from inside the VM to be normal closes. But both showed up as "aborted" in VBoxmanager, and both got localhost crashes

So far OK with a single VM open, at a time, so I'm staying with 4.1.8 and not opening two simultaneously.
(If someone has a suggestion toward debugging that could be useful, I'll test and post results).

Anyone else having this problem, or is it just me?

No, you are not alone.

I have been experiencing kernel panics fairly regularly. It seems to be when I am shutting down a virtual machine. I run RedHat 5.7 for my Host OS, Oracle Linux 6.3, CentOS 5.7, and Windows XP as Guest OS'es. This had been happening intermittently on VB 4.1.6; since upgrading to 4.1.18 it's now happening fairly regularly (at least once a day).

Since this has been happening to folks for almost a year now (ever since the 4.1 update) and no progress has been made towards a fix, I guess that I'm going to have to return to using VMWare Workstation. I don't have time to debug VB right now; project needs are too pressing.

flurry today, attached

sorry, wrong topic, forgot how old this problem was. Yeah, I'm up to 4.1.18; I'll find the right topic to continue