virtualbox.org

Lots of good new stuff on VBox 2.1, but roughly 50% of the time, trying to start a VM causes it to hang on the "Starting Virtual Machine" dialog, stuck at 0% progress.

It doesn't use any CPU, it's just stuck there. The host OS is Windows Server 2008 x64 on a quad-core box.

Since there's no way to cancel it, trying to kill the VirtualBox processes results in having a zombie VirtualBox.exe that cannot be killed (it's probably stuck on a kernel call), so the only way to be able to start the VM is to reboot the host machine.

I'm suspecting that the hang is related to the new host networking code, as the last few lines of the log when the VM gets stuck are:

00:00:03.166 ATA: Ctl: finished processing RESET
00:00:03.266 ATA: Ctl: finished processing RESET
00:00:03.365 ATA: Ctl: finished processing RESET
00:00:03.467 IntNet#0: szNetwork={HostInterfaceNetworking-Atheros L1 Gigabit Ethernet 10/100/1000Base-T Controlle} enmTrunkType=3 szTrunk={1fa6f829-54de-4fe6-924e-cc62b6505ab9} fFlags=0x0 cbRecv=223232 cbSend=36864

Anyone seeing anything similar?

tomasr wrote:
Anyone seeing anything similar?

I'm seeing the same thing.

Host: Vista x64, Intel Q6600
Guest: ubuntu server x32

-Bob

Glad to know I'm not the only one seeing this (misery loves company?). FWIW, I don't think the guest OS has anything to do with it (it happens with both my linux and windows VMs). In fact, I think the hang is even before the BIOS in the VM kicks in (i.e. the BIOS "splash screen" doesn't even get displayed at that point)

Same problem here.

Host: Windows XP x64
Guest: Windows 2000

After going through a number of reboot cycles, I figured out that after a fresh reboot, I could start the VM once. After shutting it down, I would have the problem until the next reboot.

I was using the host interface; I switched to NAT and I could start, shutdown the VM over and over again.

Please check if there is a bug report of this issue in the http://www.virtualbox.org/wiki/Bugtracker and if it isn't, create one. You need a separate account for the bugtracker though.