virtualbox.org

I was running several Windows Server 2008 R2 VMs when I noticed that two of them were listed as powered off in the VM list. When I shut them both down a while later, the host (Snow Leopard on a dual-cpu Mac Core) kernel-panicked.

After the reboot the disk with the VMs didn't mount again.

What might have happened there?

Edit: This is VirtualBox 4.1.6.

Could be the hard disk containing the VMs is failing. If it unmounted while you were running the VMs then that might account for what you saw.

rpmurray wrote:Could be the hard disk containing the VMs is failing. If it unmounted while you were running the VMs then that might account for what you saw.

Interesting.

That is possible. The hard disk dedicated to VMs was unmounted (but checked out OK) after the crash. Plus I just had another crash with the very same symptoms. Maybe the hard disk is failing.

VirtulBox still shouldn't cause a kernel panic, should it? Should I register a bug somewhere for this?

Anyway, I just added another hard disk to my Mac Pro and will wimply move all VMs and support files to the new disk and rename the new disk. Ta.

rpmurray wrote:Could be the hard disk containing the VMs is failing. If it unmounted while you were running the VMs then that might account for what you saw.

I moved all the VM data to another disk, and renamed both disks so that VirtualBox could find all the files again. All VMs work. None have so far panicked the host when shutting down.

I had a good look at the possibly-failing disk and couldn't find anything wrong with it. I think it is OK.

I noticed I was running VirtualBox 4.1.6. I updated to 4.1.8. Everything works fine so far.

ajbrehm wrote:

rpmurray wrote:Could be the hard disk containing the VMs is failing. If it unmounted while you were running the VMs then that might account for what you saw.

I moved all the VM data to another disk, and renamed both disks so that VirtualBox could find all the files again. All VMs work. None have so far panicked the host when shutting down.

I had a good look at the possibly-failing disk and couldn't find anything wrong with it. I think it is OK.

I noticed I was running VirtualBox 4.1.6. I updated to 4.1.8. Everything works fine so far.

VirtualBox crashes the entire system again, this time when closing the window of a VM running FreeNAS (x64). Incidentally, FreeNAS didn't work on VirtualBox.

It could be your host OS, something inside could possibly break.

Read the console for clues before the time of system crash.

Please see viewtopic.php?f=8&t=45387 and see whether your symptoms are similar to those described there.

There are two bugs (at least) filed against panics when shutting down VMs in VirtualBox 4.1.x. If you have it, you might want to upload your crashdump log there.

https://www.virtualbox.org/ticket/9897
https://www.virtualbox.org/ticket/9359

cheers, john

jglogan wrote:Please see viewtopic.php?f=8&t=45387 and see whether your symptoms are similar to those described there.

There are two bugs (at least) filed against panics when shutting down VMs in VirtualBox 4.1.x. If you have it, you might want to upload your crashdump log there.

https://www.virtualbox.org/ticket/9897
https://www.virtualbox.org/ticket/9359

cheers, john

That's exactly it! Can I downgrade to VirtualBox 4.0.x?

> can I downgrade
Read the threads; that worked for me, downgraded to 4.0.something a few weeks ago after someone suggested it.

That worked fine --- I could work with multiple guest VMs at the same time under Lion.

With 4.1.8, I can _not_ run more than one VM at a time.

If I try I get a localhost crash, details at viewtopic.php?f=8&t=47389&p=215311#p215311

If I wait til one VM finishes shutting down before opening another, no problems.