VM hangs trying to connect to pulseaudio => Fixed in 1.5.6

[Rui]

Following what I just described on ticket #1089 I started VirtualBox again and the Vista VM hanged with a progress dialog saying "Starting the virtual machine..." at 0%.

The log ends with:

1192:46:38.126 End of CPUID dump 1192:46:38.128 Debug: HCPhys32BitPD=000000004b861000 aHCPhysPaePDs={0000000118419000,000000011841a000, 1192:46:38.128 Debug: HCPhysInterPD=00000000d915c000 HCPhysInterPaePDPTR=00000000c888f000 HCPhysInterP 1192:46:38.128 Debug: apInterPTs={00000000c2454000,000000001249f000} apInterPaePTs={000000011de2a000,0 1192:46:38.148 REM: Loading /usr/lib/virtualbox/VBoxREM2.rel at 0x0000000041729010 (30048576 bytes) 1192:46:38.148 REM: (gdb) add-symbol-file /usr/lib/virtualbox/VBoxREM2.rel 0x0000000041729010 1192:46:38.231 TM: cTSCTicksPerSecond=0x11bff200 (297792000) fTSCVirtualized=true fTSCUseRealTSC=fals 1192:46:38.231 CoreCode: R3=00002aaaaaab9000 R0=ffffc2000162b000 GC=a0491000 Phys=000000000f5ab000 cb= 1192:46:38.242 VMMR0.r0 module loaded. VMMR0Entry located at ffffffff88b26070. 1192:46:38.309 Activating Local APIC 1192:46:38.309 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0) 1192:46:38.319 Shared Folders service loaded. 1192:46:38.333 PIIX3 ATA: LUN#0: disk, CHS=41610/16/63, total number of sectors 41943040 1192:46:38.333 PIIX3 ATA: LUN#1: no unit 1192:46:38.333 PIIX3 ATA: LUN#2: CD/DVD, total number of sectors 0, passthrough disabled 1192:46:38.333 PIIX3 ATA: LUN#3: no unit 1192:46:38.333 PIIX3 ATA: Ctl#0: finished processing RESET 1192:46:38.433 PIIX3 ATA: Ctl#1: finished processing RESET 1192:46:38.534 NAT: passing domain name local.lan 1192:46:38.534 NAT: DNS address: 192.168.1.1 1192:46:38.534 Audio: Trying driver 'pulse'. 1192:46:38.597 Pulse: Failed to connect to server: Connection refused

And indeed pulseaudio had died (probably due to the bug I reported before). I restarted pulseaudio but VB is still hanged. I just killed it with a "kill -9 ...".

Now it started the Vista VM normally.

[Frank Mehnert]

Thanks for the report. This is a known issue with 1.5.4: If there is no server available the VM hangs. This bug is already fixed in our SVN and will be part of the next release.