Opened 15 years ago
Closed 14 years ago
#3833 closed defect (fixed)
Host Crashes on VM Exit
| Reported by: | David Bolding | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 2.2.0 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Linux |
Description
When any Guest exits, the kernel panics. No logs seem to survive the reboot (/var/log/vbox/ is empty), and no diagnostic messages are printed. I have installed VirtualBox on a RedHat Enterprise Linux 4, 64-bit host: the machine is a Core 2, Quad-Core. Though I have VT-x enabled, I have left the rest of the virtualization-related features of my system off. The crash seems to occur regardless of whether ACPI is on or off, whether Nested Paging is on or off, regardless of whether Guest Additions have started or not, and regardless of the guest (I have a Windows XP 32-bit guest and a Sidux Linux 32-bit guest, both of which cause the crash). If memory serves, the crash occurs even if VT-x is off on the Guest, though I do not think it occurred when I had VT-x disabled in the BIOS. As I said, no log files seem to survive the restart, so there are no additional files that I can provide.
Attachments (2)
Change History (10)
comment:1 by , 15 years ago
by , 15 years ago
| Attachment: | vbox_log.txt added |
|---|
comment:2 by , 15 years ago
Actually the vbox.log is not complete (due to the crash). i will attach a 'complete' vbox.log
by , 15 years ago
| Attachment: | XP-2009-07-06-16-27-48.log added |
|---|
comment:3 by , 15 years ago
So looks like a problem with VT-x. There were several VT-x-related fixes in 3.0.0 / 3.0.2, please could you check the latest release (3.0.2)?
comment:6 by , 15 years ago
Oh -- and I was wrong in the bug report above: even if VT-X is enabled in the host's BIOS, if VT-X usage is off for the guest, it exits fine, no crash. It is only if VT-X usage is enabled in the guest that there is a crash.
comment:7 by , 14 years ago
Basically it looks like a conflict between vboxdrv and ancient Linux host kernel.
I suggest upping this bug to "blocker" status, because it crashes Host.
-Technologov
comment:8 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Please reopen if still relevant. There were some fixes for older Linux 2.6 kernels in 3.0/3.1.
I can confirm this. same os with 2 Xeon Core2Quad. If i enable VT-X a system crash occurs without VT-X no crash. No systems log informations available - systems has no time to write any information to disk. vbox.log seems to stop successfully.