VirtualBox 3.0 problems on several Linux vm's

Discussions about using Linux guests in VirtualBox.

Re: VirtualBox 3.0 problems on several Linux vm's

Postby squonk » 11. Jul 2009, 10:08

Someone has tested the new version 3.0.2 if solve the problems?
squonk
 
Posts: 3
Joined: 1. Jul 2009, 17:47
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: Ubuntu, XP

Re: VirtualBox 3.0 problems on several Linux vm's

Postby mala88 » 11. Jul 2009, 16:51

I tried the new 3.0.2 and am still having problems with an Ubuntu 9.04 guest on a Vista host. It doesn't finish booting and it seems to be a networking problem. I switched to the Intel PRO/1000MT adapter but it didn't help at all.

Oh well, I guess I will go back to 2.2.24 until these issues are resolved.
mala88
 
Posts: 4
Joined: 3. Oct 2008, 02:50

Re: VirtualBox 3.0 problems on several Linux vm's

Postby futtta » 11. Jul 2009, 23:26

running 3.02 on winXP guest with ubuntu 9.04 host, no network-related freezes any more up until now.
futtta
 
Posts: 3
Joined: 2. Jul 2009, 15:26
Primary OS: MS Windows XP
VBox Version: PUEL
Guest OSses: ubuntu 9.04 (and some others for fun)

Re: VirtualBox 3.0 problems on several Linux vm's

Postby mfox » 13. Jul 2009, 06:55

3.02 seems to be working OK on my MacBook Pro with Ubuntu 9.04.
mfox
 
Posts: 18
Joined: 1. Jul 2009, 13:54
Primary OS: Mac OS X Leopard
VBox Version: PUEL
Guest OSses: Linux (various)

Re: VirtualBox 3.0 problems on several Linux vm's

Postby cornelius » 13. Jul 2009, 20:55

mfox wrote:3.02 seems to be working OK on my MacBook Pro with Ubuntu 9.04.


MacBook Pro OS X host with Ubuntu 9.04 guest here, too. Mine still hangs at various points under high load (during gnome startup, on program launch, ...).
cornelius
 
Posts: 7
Joined: 14. Apr 2009, 20:55
Primary OS: Mac OS X Leopard
VBox Version: PUEL
Guest OSses: Ubuntu 9.04

Re: VirtualBox 3.0 problems on several Linux vm's

Postby jdpfu459 » 23. Jul 2009, 19:06

--- AM Report ---
I'm having the same lock-up problem as others are reporting with slight differences. The lockup happens whenever constant network traffic is caused on Linux guests with 2-CPU and IO-APIC enabled.

Host is Vista-64 SP-latest w/ (2) T8100 C2D 2.1GHz CPUs
Guest is xubuntu 8.0.4 (2.6.24-24-generic SMP / i686) - current patches on LTS hardy
VM NIC is the Intel PRO/1000 MT Desktop (for almost a year)

Installed 3.0.2 onto Vista and altered both xubuntu and WinXPPro VMs to use 2 CPUs. IO-APIC was forced as a setting. No other VM setting changes from the 2.2.4 settings. Boot both VMs and install client extensions. reboot. WinXP runs clean and good. No issues, beyond it doesn't see the 2nd CPU.

xubuntu locks up after some period of network use, perhaps 20 min. Force a close on the Linux VM (shutdown isn't possible) and change the xubuntu settings to 1 CPU and uncheck IO-APIC. Then reboot the linux VM. All is working well again, accept only 1 CPU is used. Downloaded 6GB of data and placed under heavy load for 45 min. Stable. Networking seems as solid as before the 3.x.x update (was on 2.2.4)

No 3D Acceleration enabled or nested paging.

Next test will be checking IO-APIC, but staying at 1 CPU.

Again, WinXP is happy running 2 CPUs (though it doesn't appear to know it has 2 CPUs). IO-APIC was not enabled during installation for **any** of the VMs, but is enabled whenever 2 CPUs are configured in the VBox settings.

--- PM Update ---
Tested Linux VM with IO-APIC and 1 CPU - stable for the last 30 min while performing heavy processing and networking. Need to let it run for a few more hours before I try adding the 2nd CPU back. BTW, verified that Linux did see IO-APIC by `more /proc/interrupts` and didn't see it with the prior settings.

Code: Select all   Expand viewCollapse view
$ more /proc/interrupts
           CPU0       
  0:        484   IO-APIC-edge      timer
  1:       1713   IO-APIC-edge      i8042
  6:          4   IO-APIC-edge      floppy
  8:          3   IO-APIC-edge      rtc
  9:          0   IO-APIC-fasteoi   acpi
 12:       7453   IO-APIC-edge      i8042
 14:      15276   IO-APIC-edge      libata
 15:       8806   IO-APIC-edge      libata
 16:     600786   IO-APIC-fasteoi   ehci_hcd:usb2, eth0
 17:          0   IO-APIC-fasteoi   ohci_hcd:usb1
 18:        609   IO-APIC-fasteoi   eth1
 19:    1479333   IO-APIC-fasteoi   vboxadd
 20:       1154   IO-APIC-fasteoi   Intel 82801AA-ICH
NMI:          0   Non-maskable interrupts
LOC:     219580   Local timer interrupts
RES:          0   Rescheduling interrupts
CAL:          0   function call interrupts
TLB:          0   TLB shootdowns
TRM:          0   Thermal event interrupts
SPU:          0   Spurious interrupts
ERR:          0
MIS:          0

--- Day 2 Report ---
Ok, so the machine is still running but after about 14 hours, access to a vboxsf host directory has locked up. Everything else seems to still be working, except "share" access and any programs that attempt access to the share like df, ls, and normal applications. I'll remove the 2nd CPU and test again with no other changes.
Last edited by jdpfu459 on 24. Jul 2009, 12:28, edited 3 times in total.
jdpfu459
 
Posts: 2
Joined: 23. Jul 2009, 18:04
Primary OS: MS Windows Vista
VBox Version: PUEL
Guest OSses: xubuntu, WinXPPro, OpenSolaris, FreeBSD

Re: VirtualBox 3.0 problems on several Linux vm's

Postby kartikeyans » 23. Jul 2009, 20:19

I am surprised of no reply/comments from Sun/Virtualbox developers.

kartikeyan
kartikeyans
 
Posts: 7
Joined: 29. Dec 2008, 08:46

Previous

Return to Linux Guests

Who is online

Users browsing this forum: No registered users and 5 guests