VirtualBox

Opened 8 years ago

Last modified 8 years ago

#15618 new defect

5.1 and Windows XP machine crashes (raw mode, VERR_REM_VIRTUAL_CPU_ERROR Guru)

Reported by: Trolleyfan Owned by:
Component: other Version: VirtualBox 5.1.0
Keywords: 5.1 Crash XP Cc:
Guest type: Windows Host type: Windows

Description

Just upgraded to 5.1 from 5.0.24 - and Windows XP machine crashes every time you try to load. The saved session crashed. The fresh boot crashed. I can do a Windows Safe boot (and loaded the new utilities there), but a regular boot still crashes.

Attachments (4)

VBox.log (264.5 KB ) - added by Trolleyfan 8 years ago.
VBox log file
VBox.png (10.0 KB ) - added by Trolleyfan 8 years ago.
VBox png file
VBox.2.log (403.3 KB ) - added by dtvkoe 8 years ago.
VBox.2.png (46.0 KB ) - added by dtvkoe 8 years ago.

Download all attachments as: .zip

Change History (9)

by Trolleyfan, 8 years ago

Attachment: VBox.log added

VBox log file

by Trolleyfan, 8 years ago

Attachment: VBox.png added

VBox png file

comment:1 by johnlee, 8 years ago

You don't give much infi but fwiw I'm running an existing xp vm on win 7 64, with 5.1, ok. j

comment:2 by Frank Mehnert, 8 years ago

According to the VBox.log file the VT-x mode of your host is not available for some reason. Disabled in the BIOS? Try to enable it.

comment:3 by Frank Mehnert, 8 years ago

Summary: 5.1 and Windows XP machine crashes5.1 and Windows XP machine crashes (raw mode, VERR_REM_VIRTUAL_CPU_ERROR Guru)

by dtvkoe, 8 years ago

Attachment: VBox.2.log added

by dtvkoe, 8 years ago

Attachment: VBox.2.png added

comment:4 by dtvkoe, 8 years ago

I've got a similiar problem as Trolleyfan. Windows XP crashses right after start the login screen pops up.

VT-x mode is disabled because my host cpu doesn't support it.

I've tried VirtualBox-5.1.0-108711-Win.exe as well as version VirtualBox-5.1.2-108956-Win.exe. Both versions have the same problem.

Last edited 8 years ago by dtvkoe (previous) (diff)

comment:5 by Iker Rodriguez, 8 years ago

I had exactly the same problem, and my Windows XP VM was running perfectly for years. I fixed it using only 1 virtual CPU in the VM configuration. There must be some regression in the way VirtualBox deals with I/O APIC and more than one CPU in Windows XP guests.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use