VM hanging while starting up at 0% => Fixed in SVN

[Tomas Restrepo]

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 Q6660 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

Problem does not seem related to the kind of Guest: it happens with both Linux and Windows guests, and the hang happens even before the "bios splash screen" is rendered.

[fcpk]

Confirming same issue here only since 2.1. 2k8 x64 here too and experiencing these freeze all the time.

Last lines of my log: 00:00:01.752 IntNet#0: szNetwork={HostInterfaceNetworking-Realtek RTL8168B/8111B Family PCI-E Gigabit Ethernet NI} enmTrunkType=3 szTrunk={6b240002-4f6b-438e-9fee-c0902e5ff3d1} fFlags=0x0 cbRecv=223232 cbSend=36864 00:00:01.758 IntNet#1: szNetwork={HostInterfaceNetworking-Microsoft Loopback Adapter} enmTrunkType=3 szTrunk={bfeb7f5b-d22b-4112-a97c-05b288a603af} fFlags=0x0 cbRecv=223232 cbSend=36864

[Riccardo]

Same issue since 2.1 on XP Pro x64 with kubuntu 8.04 x86/x64 guests.

Last lines of my log:
00:00:01.537 ATA: Ctl: finished processing RESET
00:00:01.638 IntNet#0: szNetwork={HostInterfaceNetworking-Intel(R) 82566DC Gigabit Network Connection} enmTrunkType=3 szTrunk={cdac3795-e40f-4139-9115-58e1a840c563} fFlags=0x0 cbRecv=223232 cbSend=36864

[Riccardo]

I add to my previous report that the hang happens only when using "host interface" network. No problems with NAT so far.

[bassamt]

We are seeing this too on Vista x64 host running Linux x86 guest.

[Dominator]

Same here since 2.1.0 on Windows Server 2003 x64 on any guest OS when using the host interface.

[Evan Stoner]

Same problem. VB 2.1.0, Host WinXP Pro, Guest Win7. Was working fine, closed the VM ok. Tried to start it later in the day and this problem occurred.

[Evan Stoner]

Also, changing networking type does not fix the problem for me. Tried NAT and even disabling the adapter, but neither worked.

[JesperW]

Just wanted to add that on my system (WinXP x64) it ALWAYS starts once after computer boot, and hangs on any subsequent attempts. It does not seem to matter that I use Process Explorer to kill all VBox processes, it still runs only once.

[Evan Stoner]

At some point, I enabled 3D Acceleration and that's what caused the problem. When I turned it off, the VM started just fine. Hope this helps someone!

[Sander van Leeuwen]

So it seems to be host interface networking and/or 3d acceleration. Can the others confirm this? Thanks.

[Tomas Restrepo]

I can confirm I have both host interface networking AND 3d acceleration enabled when the problem happens.

[JesperW]

Nope, sorry, 3D is inactive for all my VM's. Still have the problem.

[Riccardo]

I too, have the problem with 3D disabled.

[Sander van Leeuwen]

Please read my question again. (JesperW & riccardo65) Disable both host interface networking (use NAT) and 3d acceleration.

[Riccardo]

Sorry. The question was already clear. Here is a more detailed answer:

• NAT: no problem regardless of 3D being enabled/disabled.
  
• Host interface: guest often hangs after the first restart regardless of 3D being enabled/disabled.

[JesperW]

Confirming. It's only Host Interface that's hanging.

[misha]

I confirm that the problem was host interface - related. The issue was caused by the state variable not being initialized properly. The issue is fixed in SVN now.

[Stephan Wiechert]

Is there a chance to get hotfix?

Regards

Seranor

[Konstantin]

I also have this problem. When you can get the upgrade?