VirtualBox

Opened 15 years ago

Closed 15 years ago

Last modified 14 years ago

#4342 closed defect (fixed)

Windows XP Setup results in a blue screen if SATA is used (VBox 3.0) => Fixed in SVN

Reported by: unggnu Owned by:
Component: virtual disk Version: VirtualBox 3.0.0
Keywords: SATA Cc:
Guest type: Windows Host type: Linux

Description

Every time I install Windows XP SP2 the VM shows a blue screen or even freezes while the XP logo is shown. It normally happens during the graphical installation part, sometimes shortly after start sometimes during the last processes.

My Host is Ubuntu 9.04 and I have enabled Sata, SMP with 3 Cores and PAE/NX .

Installation works fine if I use IDE instead. The sata driver are loaded from the virtual disk image on start.

This is the log after a blue screen early during installation. http://pastebin.ca/1480852

Attachments (3)

Windows 2000-2009-07-06-17-14-57.log (36.1 KB ) - added by Brian V. 15 years ago.
VirtualBox 3.0.0 Windows 2000 Log File
Windows XP-2009-07-06-17-19-06.log (36.0 KB ) - added by Brian V. 15 years ago.
VirtualBox 3.0.0 Windows XP Log File
VBox.log (45.8 KB ) - added by apeyser 15 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 by unggnu, 15 years ago

Btw. Sata works fine in 2.2.4. So either way it is a problem in combination with IO-APIC or a new one.

by Brian V., 15 years ago

VirtualBox 3.0.0 Windows 2000 Log File

by Brian V., 15 years ago

VirtualBox 3.0.0 Windows XP Log File

comment:2 by Brian V., 15 years ago

I have the same problem that unggnu reported. I am running VirtualBox 3.0.0 on a 32-bit Windows XP Professional host (w/SP3). I am trying to run two guest operating systems, 32-bit Windows 2000 and 32-bit Windows XP Professional. Both virtual machines are configured for the following:

  • Uses one processor
  • Hardware virtualization disabled
  • "ACPI" enabled
  • IO APIC disabled

Both guest machines were using the SATA (AHCI) hard drive controller fine in VirtualBox 2.2.4; however once I upgraded to VirtualBox 3.0.0, the SATA (AHCI) hard drive controller has given me BSOD whenever either guest operating systems try to start up. If I switch either guest machine to use the IDE hard drive controller, then it will boot up normally. I have attached both log files for my Windows 2000 guest and my Windows XP guest; when they received the BSOD message.

In addition, the BSOD message I get for my Windows 2000 guest is:

"STOP: 0x0000006F Session3_Initalization_failed"

The BSOD message I get for my Windows XP guest is:

"STOP: 0x0000007e"

comment:3 by unggnu, 15 years ago

I have installed Windows Vista 32 Bit with Virtualbox 3.0.2 on an virtual sata disk and I got a crc error which of course cancels the installation. Afterwards I changed the controller to IDE and it worked fine. So still an issue. The installation medium is an iso so it couldn't be the source. Host OS is still Ubuntu 9.04 AMD64 and IO-APIC with three cores was activated.

comment:4 by aeichner, 15 years ago

Reproduced here. We are investigating this issue.

comment:5 by Frank Mehnert, 15 years ago

Summary: Windows XP Setup results in a blue screen if SATA is used (VBox 3.0)Windows XP Setup results in a blue screen if SATA is used (VBox 3.0) => Fixed in SVN

comment:6 by aeichner, 15 years ago

This should be fixed in the next maintenance release. Thanks for the report!

comment:7 by Sander van Leeuwen, 15 years ago

Resolution: fixed
Status: newclosed

comment:8 by apeyser, 15 years ago

I'm getting something very similar with 3.0.4. My windows guest locks up on the Windows boot up screen with SATA, but not IDE. It was working perfectly under 2.4 -- but as soon as I upgraded, it was a no go.

This is VirtualBox 3.0.4 under gentoo, with PIIX4 (ICH6 locks up seconds later) with SATA(AHCI), two drives in port 0 & 1, 1G of memory, ACPI on, IO APIC off. Safe mode locked up with AGP -- after removing that, it locked up at Mup, using the latest intel sata driver.

Additionally, the intel floppy doesn't currently work with WinXP to get to the recovery console.

I'll attach my VBox log.

by apeyser, 15 years ago

Attachment: VBox.log added

comment:9 by Frank Mehnert, 15 years ago

This bug should be fixed in VirtualBox Beta 3.0.6 Beta 1.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use