#1388 closed defect (fixed)
Mac OS X: Crash on reboot/shutdown of Windows XP
| Reported by: | Quinn Comendant | Owned by: | |
|---|---|---|---|
| Component: | VMM | Version: | VirtualBox 1.6.2 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Mac OS X |
Description
Running VirtualBox 1.5.51 on Mac OS X 10.5.2 (Macbook Pro 2.4GHz/4GB/250GB). Freshly installed Windows XP pro with SP2. Guest OS boots and functions well. But upon restart or shutdown the VirtualBox VM "unexpectedly quits". Crash report attached.
Attachments (2)
Change History (9)
by , 17 years ago
| Attachment: | crash_report.txt added |
|---|
comment:1 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
by , 17 years ago
| Attachment: | Picture 50.png added |
|---|
VirtualBox-1.6.0-OSX_x86.dmg: no mountable file systems
comment:2 by , 17 years ago
I'd try if I could install it. The DMG seems to be corrupt. I get this error:
VirtualBox-1.6.0-OSX_x86.dmg: no mountable file systems
(See screen capture, attached above.)
comment:3 by , 17 years ago
Works for me. Maybe your download was interrupted. Please download and try again.
comment:4 by , 17 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
ENV: VirtualBox 1.6.2
Macbook Pro 2.5GHz/gGB/250GB
Crash of VirtualBox on shutdown of Windows XP happens every time, if and only if I have booted with Setting:
[check] Mount CD/DVD Drive
Host CD/DVD Drive [MATSHITA DVD-R UJ-867]
and in the drive is the WinXP Home SP2 media (which I don't boot from, but is present when WInXP does boot).
I haven't installed the VirtualBox tools.
Let me know if you need crash data, but I imagine you should be able to repro with that info.
comment:5 by , 17 years ago
| Guest type: | other → Windows |
|---|---|
| Host type: | other → Mac OS X |
| Version: | VirtualBox Mac OS Beta 3 → VirtualBox 1.6.2 |
comment:6 by , 17 years ago
| Component: | other → VMM |
|---|
comment:7 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Please reopen if this problem persists with the latest release of VirtualBox (3.0.8).
Try again with 1.6.0 and report back if it's still relevant. Thanks.