VirtualBox

Ticket #2309 (reopened defect)

Opened 6 years ago

Last modified 12 months ago

Detect Hardware in XP crashes the VM (HD attached to AHCI port 0)

Reported by: TiCPU Owned by:
Priority: major Component: other
Version: VirtualBox 2.2.2 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description (last modified by frank) (diff)

I just added a serial port to the machine and wanted to install it in XP as it was not automatically detected, so I went in the device manager and clicked detect new hardware, the screen went black with some nice multicolor screen corruption.

Removing the serial port I just added also crashes the machine. Enabling VT also crashes the same way. In summary, clicking scan for hardware changes in XP just crashes VBox.

The host is Gentoo Linux, latest up-to-date version. The Virtual Machine is Windows XP Service Pack 3.

Attachments

crashed-vbox.png Download (32.5 KB) - added by TiCPU 6 years ago.
Crashed Virtual Box
XP-2008-12-11-13-38-55-stopped-automatically.log Download (62.0 KB) - added by TiCPU 5 years ago.
XP-2008-12-11-13-41-20-stopped-manually.log Download (62.4 KB) - added by TiCPU 5 years ago.
VBox.log Download (65.1 KB) - added by TiCPU 5 years ago.
VBox.Log for version 2.2.2 with matching add-ons and modules, after powering off manually.
xpvb-2009-12-01-17-00-49.log Download (45.7 KB) - added by bla0ck 4 years ago.
vb log
bsod.png Download (25.0 KB) - added by bla0ck 4 years ago.
crashed xp sp3 bsod

Change History

Changed 6 years ago by TiCPU

Crashed Virtual Box

comment:1 Changed 5 years ago by frank

Please check again with VirtualBox 2.0.4. If the problem still happens, please attach a VBox.log file of such a crashed session. And please enable core dumps for your machine, see here for instructions. If you get a core dump, please send it to frank _dot_ mehnert _at_ sun _dot_ com (if not too big, use some upload service otherwise).

comment:2 Changed 5 years ago by TiCPU

With VBox 2.0.6 I get a Blue Screen instead: STOP: 0x000000F4 (0x00000003, 0xFFB68020, 0xFFB68194, 0x805FB046) See attached Virtual Box logs, one after the VM automatically shutdown, and the other when stopped on the Blue screen.

Changed 5 years ago by TiCPU

Changed 5 years ago by TiCPU

comment:3 Changed 5 years ago by kmix

FYI -- This was a problem for me also, but I was able to install the hardware after temporarily disabling the SATA controller.

comment:4 Changed 5 years ago by TiCPU

I confirm, disabling the SATA port allow me to scan for new hardware without a crash, even if the serial port I added wasn't detected ??

comment:5 Changed 5 years ago by aeichner

Which version of the Intel SATA drivers are you using?

comment:6 Changed 5 years ago by TiCPU

In the Device Manager, with SATA Enabled, I see:

Intel(R) ICH8M-E/M SATA AHCI Controller Date: 2008-06-07 Version: 8.2.0.1001

I've got virtualbox-modules-2.0.6 installed with latest VirtualBox guest tools too.

comment:7 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Please reopen if this problem persists with the latest release 2.2.2.

comment:8 Changed 5 years ago by TiCPU

  • Status changed from closed to reopened
  • Resolution fixed deleted

Scan for new hardware works on IDE, it works with SATA AHCI enabled, switched my XP to SATA Port 0, and it crashed again! Nothing new.

Changed 5 years ago by TiCPU

VBox.Log for version 2.2.2 with matching add-ons and modules, after powering off manually.

comment:9 Changed 5 years ago by frank

  • Description modified (diff)

To be sure: You are talking about a crashing guest, not a crashing host, right?

comment:10 Changed 5 years ago by TiCPU

Yes exactly, the screenshot is the VirtualBox window but I can click on Machine -> Reset and it reboots. I will soon put a link to a whole machine and config soon with both the save state bug and this one.

comment:11 Changed 5 years ago by frank

I've removed your last comment to remove that URL from the public website. I'm currently downloading that stuff.

comment:12 Changed 5 years ago by frank

  • Summary changed from Clicking on detect hardware in XP crashes the VM to Detect Hardware in XP crashes the VM (HD attached to AHCI port 0)

comment:13 Changed 5 years ago by frank

  • Version changed from VirtualBox 2.0.2 to VirtualBox 2.2.2

comment:14 Changed 5 years ago by ToddAndMargo

I am having the same problem: Host: CentOS 5.3; guest XP-Pro-SP3. Scanning for hardware changes in the guest (XP) gives me the BSOD. VBox is 3.0.2.

Additional information: crashes with or without VB Guest Additions installed.

-T

Changed 4 years ago by bla0ck

vb log

Changed 4 years ago by bla0ck

crashed xp sp3 bsod

comment:15 Changed 4 years ago by bla0ck

Hi,

log and bsod of win xp guest on win xp host from my side attached.

This is a problem when using Cisco VPN any connect client as it also executes new hardware search during connection.

The workaround is to attach boot drive on IDE controller. Any other drive attached on AHCI controller seems to be lost by system during hardware scan.

Thanks for fixing this.

comment:16 Changed 4 years ago by bla0ck

BTW, I can reliably repro this on 3.1 55467 let me know in case you need more info.

Steps to reproduce:

  1. Install XP SP3 on IDE drive with AHCI controller enabled.
  2. Install latest Matrix storage driver from Intel. Mine is ICH8M-E/M AHCI Controller 8.9.0.1023.
  3. Shut down VM, re-attach HDD to AHCI controller port 0.
  4. Start VM and run Add hardware wizard.

Actual result - BSOD. Expected result - successful completion of wizard.

comment:17 Changed 3 years ago by wbic16

I'm able to reproduce this using Windows XP SP3 guest, AHCI SATA port 0, ICH8M-E/M, Ubuntu 64-bit 11.04 host, VirtualBox 4.0.6 r71344. Whenever I attempt to run the Add Hardware Wizard the VM just locks up.

comment:18 Changed 2 years ago by clarkjc

Hello,

I am able to reproduce this using a Windows XP x64 guest, AHCI SATA port 0, ICH8M-E/M, Ubuntu 11.10 64-bit host, and VirtualBox 4.1.10 r76795. Whenever "Scan for hardware changes" in selected in the Device Manager on the guest, the VM spontaneously reboots.

The problem does not occur when using the emulated PIIX4 IDE controller instead of the emulated ICH8M-E/M AHCI SATA controller.

Thank you.

Version 0, edited 2 years ago by clarkjc (next)

comment:19 Changed 19 months ago by frank

  • Description modified (diff)

Still reproducible with VBox 4.1.22?

comment:20 Changed 19 months ago by Squall Leonhart

yes, and 4.2

comment:21 Changed 12 months ago by Takeshi

Hello everyone ..

I am using VirtualBox 4.2.12 r84980, my guest is Windows XP SP3

When I do hardware scan, the VM Guest simply reboot .. After Digging for a while, I was able to find the Intel's 10.1.0.1088 version AHCI Driver

Intel(R)ICH8M-E/M SATA AHCI Controller 10.1.0.1088

It was bundled in RAID_F6_32bit_10.1.0.1008_PV self-extract Driver

and I am using ICH9 chip set, dual core CPU with Intel vt and 2GB ram .

help anyone?

comment:22 Changed 12 months ago by Squall Leonhart

use IDE for the emulated hdd's instead of ahci/sata

comment:23 Changed 12 months ago by Takeshi

so you can't use SATA for Windows XP for sure? there is no way to fix the broken function?

I mean ... XP already using ICH7, 10 with SATA device for a long time and VirtualBOX does have the function out there for SATA devices ..

but now we can't use SATA because it's broken? then what's the point of having SATA controller option?

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use