Opened 16 years ago
Last modified 9 years ago
#2309 closed defect
Detect Hardware in XP crashes the VM (HD attached to AHCI port 0) — at Version 19
| Reported by: | Jerome Poulin | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 2.2.2 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description (last modified by )
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.
Change History (25)
by , 16 years ago
| Attachment: | crashed-vbox.png added |
|---|
comment:1 by , 15 years ago
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 by , 15 years ago
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.
by , 15 years ago
| Attachment: | XP-2008-12-11-13-38-55-stopped-automatically.log added |
|---|
by , 15 years ago
| Attachment: | XP-2008-12-11-13-41-20-stopped-manually.log added |
|---|
comment:3 by , 15 years ago
FYI -- This was a problem for me also, but I was able to install the hardware after temporarily disabling the SATA controller.
comment:4 by , 15 years ago
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:6 by , 15 years ago
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 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Please reopen if this problem persists with the latest release 2.2.2.
comment:8 by , 15 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
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.
by , 15 years ago
VBox.Log for version 2.2.2 with matching add-ons and modules, after powering off manually.
comment:9 by , 15 years ago
| Description: | modified (diff) |
|---|
To be sure: You are talking about a crashing guest, not a crashing host, right?
comment:10 by , 15 years ago
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 by , 15 years ago
I've removed your last comment to remove that URL from the public website. I'm currently downloading that stuff.
comment:12 by , 15 years ago
| Summary: | Clicking on detect hardware in XP crashes the VM → Detect Hardware in XP crashes the VM (HD attached to AHCI port 0) |
|---|
comment:13 by , 15 years ago
| Version: | VirtualBox 2.0.2 → VirtualBox 2.2.2 |
|---|
comment:14 by , 15 years ago
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
comment:15 by , 14 years ago
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 by , 14 years ago
BTW, I can reliably repro this on 3.1 55467 let me know in case you need more info.
Steps to reproduce:
- Install XP SP3 on IDE drive with AHCI controller enabled.
- Install latest Matrix storage driver from Intel. Mine is ICH8M-E/M AHCI Controller 8.9.0.1023.
- Shut down VM, re-attach HDD to AHCI controller port 0.
- Start VM and run Add hardware wizard.
Actual result - BSOD. Expected result - successful completion of wizard.
comment:17 by , 13 years ago
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 by , 12 years ago
Hello,
I am able to reproduce this using a Windows XP x64 SP2 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.
Crashed Virtual Box