Opened 9 years ago
Closed 8 years ago
#13757 closed defect (obsolete)
VM simply stopped to run
| Reported by: | AEJ_CWB | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.2.18 |
| Keywords: | crash | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
VM crashed in a moment that I wasn't interacting with it. Previous strange behaviour was never perceived.
Attachments (1)
Change History (3)
by , 9 years ago
comment:1 by , 9 years ago
comment:2 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The VM (old VBox version btw, 4.2.18 is quite old, so upgrading can't hurt if this turns out to be a bug in VBox) bumped into the following error: VERR_VMX_VMXON_FAILED. This typically means that some other hypervisor grabbed the VT-x feature or (more likely, there is power management activity in VBox.log) the BIOS screwed up the CPU initialization when coming back from sleep.
Check if there is a newer BIOS version available...