Opened 12 years ago
Closed 11 years ago
#11244 closed defect (fixed)
Random Linux guest lockup
| Reported by: | m.s.s. | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.1.18 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description
We are running several Linux based VirtualBox hosts (Ubuntu 10.04 LTS and openSuse 12.1) which in turn run multiple Linux guests (OpenSuse Build Service appliances based on openSuse 12.1 and Ubuntu 12.04 LTS guests). One of VirtualBox hosts reveals weird behavior - at the random time (typically once in few days) one of VM guest running on it locks up with CPU consumed by VirtualBox process goes to to 100% * <number of CPUs allocated to the guest>. Both uniprocessor and single processor guests are affected. Sometimes locked guests can be pinged by IP address, but can be never connected. Still VMs are responding to VBoxManage and may be shutdown by VBoxManage controlvm poweroff. There is nothing particularly interesting in host logs and usually nothing in guest logs. Last time however we got some log messages in guest messages log (fragment attached). VirtualBox log from last lockup case is also attached
Host info: Dell PowerEdge 2900 CPU: 2x Intel Xeon E5410 2.33Ghz RAM: 12Gb OS: Ubuntu 10.04.3 LTS 64-bit VirtualBox: 4.1.18r78631
CPU virtualization support is enabled in server BIOS.
At some point we have disable ACPI for all virtual machines and run them with acpi=off boot option to try to prevent lockup but that did not help much. Also we suspected that it may be host time synchronization affects guest tick rate so we also disabled ntpd on the host. This also did not help.
We run the same VirtualBox version on other virtualization hosts too but they do not have such problems and I had never saw mentions about similar issues in change logs so I am reluctant to upgrade VirtualBox (though I am not strongly against it).
Attachments (2)
Change History (6)
by , 12 years ago
| Attachment: | messages.log added |
|---|
comment:1 by , 12 years ago
comment:2 by , 12 years ago
Both uniprocessor and single processor guests are affected. - I meant both uniprocessor and multiprocessor guests are affected
by , 12 years ago
| Attachment: | VBox.log.1 added |
|---|


One another thing to add: VM guest disk storage is located in LVM volumes on the host rather than in VDI files to bypass host cache and to allow guest hot backup via LVM snapshot. There are some complains in VBox.log about file system size but they are not relevant (may be they are for cases when VM snapshots are used but we do not use them).