Ticket #8462 (closed defect: fixed)
Gentoo guest Freezes during compile
| Reported by: | kwhat | Owned by: | |
|---|---|---|---|
| Priority: | major | Component: | guest smp |
| Version: | VirtualBox 4.0.4 | Keywords: | gentoo compile |
| Cc: | Guest type: | Linux | |
| Host type: | Linux |
Description
There appears to be a thread deadlock issue when using Gentoo guests to compile software. This issue only occurs if the virtual cpu's are increased past 1. It makes no difference if there are 2 or 8 cpus allocated to the guest. I am pretty sure this is not limited to Gentoo guests however it is very easy to reproduce using Gentoo.
Steps to reproduce: Setup a vm with more than 1 virtual cpu (more the merrier) Set make -j to something like the number of cpu's +1 Start compiling something large (emerge -v --emptytree world) and wait.
It usually goes though several packages before it locks up. The best I can tell this is a thread dead lock issue and not something like a kernel panic. I have attached the kernel config that I am using to duplicate the issue.
Attachments
-
linux-2.6.36-gentoo-r5.config
(47.3 KB) -
added by kwhat 6 years ago.
- Kernel 2.6.36 configuration file.
-
VBox.log
(86.6 KB) -
added by kwhat 5 years ago.
- Log file after issue occurred and hard shutdown initiated.
Change History
Changed 6 years ago by kwhat
-
attachment
linux-2.6.36-gentoo-r5.config
added
comment:1 Changed 5 years ago by protogenes
I second that report. The guest locks up and the host CPU is completely busy. It once happened during Ubuntu 10.10 boot as well and the kernel reported a soft lockup, I assume the same for my gentoo guest (will try later). The only way to work with my VM is to only use one CPU.
host: Windows 7 Professional x64
guest: gentoo x64 2.6.36-gentoo-r8
Changed 5 years ago by kwhat
-
attachment
VBox.log
added
Log file after issue occurred and hard shutdown initiated.
comment:4 Changed 5 years ago by kwhat
Could be related...
I tried the workaround for apci=off and that seems to have worked for this issue. I also worked around the problem by disabling acpi in the kernel directly. Using nolapic_timer caused a non-boot situation. I did not try noapic or nolapic.
comment:6 Changed 5 years ago by frank
- Status changed from new to closed
- Resolution set to fixed
No response, closing.
Kernel 2.6.36 configuration file.