VirtualBox

Opened 10 years ago

Closed 10 years ago

#12245 closed defect (fixed)

Regression: 4.2.18 -> 4.3.0: WindowsXP/KVM - BSOD - 0x0000008E

Reported by: alxchk Owned by:
Component: VMM/HWACCM Version: VirtualBox 4.3.0
Keywords: Cc:
Guest type: Windows Host type: Linux

Description

After updating from 4.2.18 to 4.3.0 Guest WindowsXP SP3 /w all (?) current updates crashed with BSOD with error line:

0x0000008E (0xC0000005, 0xB19350BA, 0xBA4CFF48, 0x00000000)

However, Guest OS can be booted with KVM disabled, or in Safe mode. Note, that minidump wasn't create and system wasn't reboot after BSOD (Minidumps saving and auto rebooting options are setted up)

Tried next steps without success:

  • Fully remove/update guest additions
  • Migrate to Different chipset
  • Migrate from NOAPIC to APIC
  • Migrate from IDE to SATA/AHCI
  • Disable Network/USB/NX/PAE/Nesting

In all cases booted successfully in safe mode, but not in normal mode. In all cases downgrading to 4.2.18 makes the problem go away.

Attachments (7)

bluescreen.png (10.0 KB ) - added by alxchk 10 years ago.
BSOD screenshot
VBox.log (95.2 KB ) - added by alxchk 10 years ago.
VBox_BSOD_4.3.2_and_4.3.0.png (117.9 KB ) - added by Schninckel 10 years ago.
VBox_BSOD.log (91.9 KB ) - added by Schninckel 10 years ago.
Logfile of XP-Machine BSOD-ing after Upgrade to 4.3.2
VBox_Safe_Mode.log (89.4 KB ) - added by Schninckel 10 years ago.
Logfile of same XP-Machine booting fine in Safe Mode
VBox.2.log (98.7 KB ) - added by alxchk 10 years ago.
Vbox 4.3.2
VBox_imported_physical_Machine.log (95.8 KB ) - added by Schninckel 10 years ago.
VBox.log - imported from a physical intel machine

Download all attachments as: .zip

Change History (26)

by alxchk, 10 years ago

Attachment: bluescreen.png added

BSOD screenshot

by alxchk, 10 years ago

Attachment: VBox.log added

comment:1 by Ramshankar Venkataraman, 10 years ago

Resolution: duplicate
Status: newclosed

Duplicate of #12227

in reply to:  1 comment:2 by alxchk, 10 years ago

Replying to ramshankar:

Duplicate of #12227

https://www.dropbox.com/s/ygv1hnfxehmvi5m/115328scr.png

If #12227 fixed, then this bug is not duplicate of the that one, because it still here, on 4.3.2

comment:3 by alxchk, 10 years ago

Resolution: duplicate
Status: closedreopened

by Schninckel, 10 years ago

in reply to:  description comment:4 by Schninckel, 10 years ago

Same Problem for me: Windows XP Machine works in Safe Mode, BSOD on boot with any other configuration. BSOD appears in 4.3.0 and 4.3.2 and disappears when downgrading to 4.2.18. Tried some things to resolve it (changed SATA to IDE, disabled Networking and USB, booted with and without Graphics Driver, etc.) but for now I seem to be stuck on 4.2.18. I doubt that this bug is a duplicate of #12227, it shows completely different behavior. This one seems similar: #12293. @ramshankar: Right now I'm short in time, but if you are interested, I'm trying to produce some logs as soon as possible.

Replying to alxchk:

After updating from 4.2.18 to 4.3.0 Guest WindowsXP SP3 /w all (?) current updates crashed with BSOD with error line:

0x0000008E (0xC0000005, 0xB19350BA, 0xBA4CFF48, 0x00000000)

However, Guest OS can be booted with KVM disabled, or in Safe mode. Note, that minidump wasn't create and system wasn't reboot after BSOD (Minidumps saving and auto rebooting options are setted up)

Tried next steps without success:

  • Fully remove/update guest additions
  • Migrate to Different chipset
  • Migrate from NOAPIC to APIC
  • Migrate from IDE to SATA/AHCI
  • Disable Network/USB/NX/PAE/Nesting

In all cases booted successfully in safe mode, but not in normal mode. In all cases downgrading to 4.2.18 makes the problem go away.

Last edited 10 years ago by Schninckel (previous) (diff)

comment:5 by Frank Mehnert, 10 years ago

Schninckel, please attach a VBox.log file for a VM session running on VBox 4.3.2. Thank you!

by Schninckel, 10 years ago

Attachment: VBox_BSOD.log added

Logfile of XP-Machine BSOD-ing after Upgrade to 4.3.2

by Schninckel, 10 years ago

Attachment: VBox_Safe_Mode.log added

Logfile of same XP-Machine booting fine in Safe Mode

in reply to:  5 comment:6 by Schninckel, 10 years ago

Replying to frank:

Schninckel, please attach a VBox.log file for a VM session running on VBox 4.3.2. Thank you!

Sorry, it took some time before I had the chance to upgrade to 4.3.2 again - this is my workstation for productive use.

comment:7 by Frank Mehnert, 10 years ago

Thanks! Now I'm really sure what the problem is: The access to MSR 0x2C. This one is not documented on AMD and will actually raise a GP (general protection fault) on physical hardware but for some reason your Windows guest seems to expect that this MSR can be read without raising a GP. VBox 4.2.x just returned 0 and didn't raise a GP while VBox 4.3.x raises a GP on AMD.

comment:8 by Frank Mehnert, 10 years ago

Did you create this guest initially on an Intel box by any chance?

in reply to:  8 comment:9 by Schninckel, 10 years ago

Replying to frank:

Did you create this guest initially on an Intel box by any chance?

Initially I created this machine on an AMD-based PC, but then copied it over to a Laptop my employer gave me, which was pure Intel Hardware. Some months ago I moved the Virtual XP Machine back to the originating AMD PC. So it was not really created on Intel Hardware, but lived there for a while.

comment:10 by Schninckel, 10 years ago

Edit: Just tried to boot the XP Machine with AMD-V disabled in VB 4.3.2. and it works just fine. (I always thought, I couldn't revert back to non-accelerated mode, once it's been enabled.) Turning AMD-V back on triggers the BSOD again.

comment:11 by alxchk, 10 years ago

Just FYU: I never use VirtualBox on AMD

Version 0, edited 10 years ago by alxchk (next)

comment:12 by Frank Mehnert, 10 years ago

alxchk, please attach a VBox.log file for a VBox 4.3.2 VM session where you see this BSOD.

by alxchk, 10 years ago

Attachment: VBox.2.log added

Vbox 4.3.2

comment:13 by Schninckel, 10 years ago

I'm attaching a logfile of a friends PC. His virtual XP Machine has been imported from a physical Intel-Machine. It was running fine on an AMD host until 4.3.2, since then it's BSODing. Reverting back to 4.2.18 or turning of AMD-V makes the problem go away.

by Schninckel, 10 years ago

VBox.log - imported from a physical intel machine

comment:14 by Frank Mehnert, 10 years ago

alxchk, your problem is handled in #12240.

comment:15 by Schninckel, 10 years ago

@frank: Just wanted to ask, if this bug is still under investigation and if I can provide you with any additional data, to solve this problem. And: #12420 might be a duplicate of this bug.

comment:16 by Frank Mehnert, 10 years ago

This bug is still under investigation. Your VM is kind of a special case (a VM running on an AMD box is accessing an MSR of an Intel box. It would BSOD on bare metal so we are currently discussing how we define the VBox behavior. I know that you expect that VBox should tolerate that MSR access as VBox 4.2.x did so...

comment:17 by Frank Mehnert, 10 years ago

VBox 4.3.6 should fix your VMs, please confirm.

in reply to:  17 comment:18 by Schninckel, 10 years ago

Replying to frank:

VBox 4.3.6 should fix your VMs, please confirm.

VBox 4.3.6 fixes the Problem on both my affected machines.

Steps to reproduce 1:

  1. Copy a working Win-XP-Machine from an AMD-PC to an Intel-PC
  2. Start XP-Machine on Intel-PC (Vbox-Version makes no Difference here)
  3. Copy XP-Machine from Intel-PC back to AMD-PC
  4. Start XP-Machine on AMD-PC with Virtualbox 4.3.0/4.3.2/4.3.4 -> BSOD
  5. Start XP-Machine with Virtualbox 4.3.6 -> works as expected, no BSOD

Steps to reproduce 2:

  1. Migrate a physical XP-Installation from an Intel-System to a Virtual-Machine
  2. Start XP-Machine on AMD-PC with Virtualbox 4.3.0/4.3.2/4.3.4 -> BSOD
  3. Start XP-Machine with Virtualbox 4.3.6 -> works as expected, no BSOD

comment:19 by Ramshankar Venkataraman, 10 years ago

Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use