Ticket #7525 (closed defect: fixed)
Virtualbox 3.2.8 on OSOL b134 with high load Ubuntu 10.04.1 Server guest hangs
|Reported by:||zebra||Owned by:|
Problem isn't a simple one to pin down.
Background info from my post here:
Effectively, an OpenSolaris b134 64bit host with a Q6600 CPU base on the bare metal. Guest is Ubuntu Server 10.04.1 fully patched.
When running the Ubuntu VM guest, we find that under high CPU time/IO load using several different methods to generate said CPU utilisation (cifsd, nfsd), the host will hang, spinlock and use 100% CPU time of said guest. Becomes completely unresponsive. The only solution is to shutdown vbox forcefully, and start it up again.
Removing SMP capability, and allocating only a single core seems to remedy this instability.
Please see the VBox log file. Not sure if it's useful - can confirm however 100% that allocating more than one physical proc to the guest creates this scenario, and removing it stabilises the issue. NB: The guest was initially installed with both cores. It is *only* unstable when high load scenarios are apparent inside the guest.
- Host type changed from other to Solaris
- Component changed from other to guest smp
- Summary changed from Virtualbox 3.2.8 on OSOL b134 hangs with high load Ubuntu 10.04.1 Server as guest to Virtualbox 3.2.8 on OSOL b134 with high load Ubuntu 10.04.1 Server guest hangs