VirtualBox 3.0 - Linux VM's hang.

[Devil505]

unipsycho's advice did the trick for me too - thanks heaps to the OP...

[jsmith]

Same thing happens to me as well - My PCLinuxOS 2009.2 (both KDE and Gnome) guest systems worked flawlessly on 2.2.4 but after upgrading to 3.0. the VMs just freeze and hang! (This is with Win7 as the Host)

I booted into Linux and installed V3 and again it froze when using either XP or Mandriva as the Guests so version 3 does seem buggy which is a great pity as it has some great new options.

[trekfan1]

Change the guest ethernet card from PC Net Fast III to Intel PRO/1000 MT desktop and problem is solved

[jsmith]

Thanks for that trekfan, much appreciated - I'll give that a whirl

[radzfoto]

I have exactly the same failure as JeZ-l-Lee. I have a Lenvo T61 running Windows Vista 32-bit Ultimate. I installed VB 3.0.0, created an Ubuntu Linux VM and tried to install Ubuntu 9.04 and it failed at exactly the same point scanning apt.

I will need to reinstall 2.2.4 b/c I need to get this vm running today.

[jsmith]

Change the guest ethernet card from PC Net Fast III to Intel PRO/1000 MT desktop and problem is solved

I changed my ethernet card from PC Net Fast III to Intel PRO/1000 MT and VB3 now works fine - thanks Trekfan

[samuelbernardo]

The install of Ubuntu fail in 30% of the install. The error is
reported in the log of VirtualBox:

00:05:12.478 [/Devices/usb-ehci/0/LUN#999/Config/] (level 5)
(restricted root)
00:05:12.478 papLeds <integer> = 0x0000000000e8e990 (15264144)
00:05:12.478 First <integer> = 0x0000000000000000 (0)
00:05:12.478 Last <integer> = 0x0000000000000000 (0)
00:05:12.478
00:05:12.479 [/TM/] (level 1)
00:05:12.479 UTCOffset <integer> = 0x0000000000000000 (0)
00:05:12.479
00:05:12.479 [/MM/] (level 1)
00:05:12.479
00:05:12.479 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:05:13.484 Changing the VM state from 'RUNNING' to
'GURU_MEDITATION'.
00:05:13.525 ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={26881797-
bc98-444d-ac69-820633b93ec7} aComponent={Display} aText={Argument
address is NULL} aWarning=false, preserve=false
00:06:32.414
00:06:32.414 !!Assertion Failed!!
00:06:32.414 Expression: RT_SUCCESS_NP(rc)
00:06:32.414 Location : E:\tinderbox\win-rel\src\VBox\Runtime\common
\misc\thread.cpp(727) RTThreadCreate
00:06:32.414 VERR_NO_MEMORY (-8) - Memory allocation failed.

The host operating system is Win Xp SP3 and I'm running VirtualBox 3.

Grateful for your help.

[baf]

samuelbernardo start a new thread and tell us there host type vb version physical memory and how you have setup your guest.

[paullanders]

Same problem here, but worse.

VirtualBox 3.0.0 upgraded from 2.2.4
WinXP Pro host
Debian Lenny 5.0 guest
GRUB bootloader

Unfortunately the Intel PRO/1000 MT Desktop workaround does not work for me. VirtualBox reports 'unable to get the MAC address' on 2 Dell Optiplex 745 and 755. Regenerating the MAC with the tools button yields no solution. Any other ideas?

Thanks!

UPDATE - turns out the workaround DOES work. I had configured port forwarding in the virtual machine using VBoxManage and the mappings were addressing the now non-existent pcnet device. Thanks to this posting for the hint.

BTW - does anyone know when port forwarding will be incorporated into the VirtualBox GUI?

[samuelbernardo]

samuelbernardo start a new thread and tell us there host type vb version physical memory and how you have setup your guest.

Problem solved with an uninstall of Virtual Box 3.0.0 followed by a new install of Virtual Box 2.2.4
The memory lack was due to the allocation in the guest configuration of 2048Mb, in a host with 3072Mb + 1024 shared for graphic (ACER Aspire 6930).

I'm sorry for not helping you more, but I'm stuck in academic work.

Congratulations for your project. VirtualBox is realy amazing!

[wheatstraw]

Wanted to add that using the e1000 card worked for me also.

Host: Ubuntu 9.04, 64bit
Guest: Ububtu 8.04 server 32bit
VirtualBox: 3.0.10

--HippiePete