Opened 14 years ago
Closed 12 years ago
#8420 closed defect (fixed)
Random lockups on linux guest
Reported by: | Anssi Kolehmainen | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.0.8 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Linux |
Description (last modified by )
I have Virtualbox 4.0.2 running on Linux (Debian, 2.6.35-trunk-amd64). There are several virtual machines (~20) running but only a few seem to exhibit random lockups. When that happens the guest becomes completely unresponsive (no ping, vrde screen is empty and unresponsive) and on host side guest consumes 100% CPU.
I've tried different guest kernels (2.6.32, .35, .37) but it always locks up eventually. Additionally the lockup is rather random but seems to occur daily (on one guest, on others maybe weekly). The difference between working and nonworking guests might be 64-bit kernel (not working) and 32-bit. Also the failing guests run weblogic app server whereas working servers run glassfish.
Everything worked fine on Virtualbox 3.2.x. Attached is log of about three lockups (+reboots) and shutdown on final lockup. I also have guest and VBox coredumps if somebody wants to take a look.
Attachments (1)
Change History (12)
by , 14 years ago
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Could you check if this build fixes your problem? There was a bug in the HPET emulation which could affect your problem.
comment:4 by , 14 years ago
I didn't notice the test build. I could have tried it during easter but now it's too late :)
I'll see whether I can test 4.0.6 during next weekend (or the next after that).
comment:5 by , 14 years ago
Installed new version yesterday and so far it has worked. I want to wait for a while before calling it stable.
comment:6 by , 14 years ago
One virtual machine locked up just as before so this issue still exists in 4.0.6
comment:7 by , 14 years ago
Could you perform another test with this build? We fixed another bug which could be related to your problem as your VM uses the HPET timer.
comment:8 by , 14 years ago
Updated to 4.0.8 (and just a day before 4.0.10 was released...) and just had the same VM lock up again.
comment:9 by , 14 years ago
Version: | VirtualBox 4.0.2 → VirtualBox 4.0.8 |
---|
comment:10 by , 13 years ago
Description: | modified (diff) |
---|
Another test could be to use the PIIX3 chipset instead of the ICH9 chipset as the latter is still marked as experimental.
comment:11 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 4.1.22.
Updated to 4.0.4 and it's still broken.