Opened 8 years ago
Closed 8 years ago
#16412 closed defect (duplicate)
Critical error has occurred running VM after upgrade to 5.1.14
| Reported by: | jac1416 | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.14 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
Was running Windows XP VM as late as three days ago with Virtual Box version 5.0.28. Received a notice that an upgrade is available. Downloaded and installed 5.1.14 over existing installation. Now the VM will not start, critical guru error. What can be done? Host running Windows 10 Pro 1607 build 14393.693.
Attachments (2)
Change History (4)
by , 8 years ago
comment:1 by , 8 years ago
Reading the log, your processor should support AMD-V virtual extensions. But it is either turned off in your BIOS or you have Hyper-V activated. Take a look on the other tickets like this here or in the forum. You’ll find how to solve this issues.
Because your hardware virtualization is turned off, VB tries to use its software layer, so called raw mode. Because of partial rewrite for version 5.1, this part is slightly broken. Take a look at this ticket #16165 and tickets mentioned in it. If your problem couldn’t be solved by changing BIOS settings or turning Hyper-V off, you should go back to the current 5.0.x version, where the raw mode works. And hope, that someday the raw mode bug would be corrected in the current branch.
comment:2 by , 8 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Let's continue the discussion in #15685.
vm log and png