Opened 16 years ago
Closed 15 years ago
#3114 closed defect (fixed)
Win XP SP2 Guest fails to boot after upgrading to 2.1.2 on Mac OS X 10.5.6 host
Reported by: | Robert | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.1.2 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Mac OS X |
Description
After upgrading to 2.1.2, both of my Windows guests will not boot. I get a BSOD when the guests start to load windows (during the black screen with progress bar, see screen shot). I tried to capture the error, but the VM immediately reboots when the error occurs. I was able to successfully boot in safe mode, but have yet been able to boot into "normal" mode.
My Linux guests appear to function correctly. Both Windows VMs worked correctly immediately prior to the upgrade, and I rebooted the host before starting the guests after upgrading.
Please advise on any additional information you need.
Attachments (6)
Change History (19)
by , 16 years ago
Attachment: | WindowsLoading.png added |
---|
by , 16 years ago
Attachment: | WinXP - PB1F-2009-01-22-15-23-22.log added |
---|
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Previously I was running VirtualBox-2.1.0-41146-OSX_x86. I just used the previous one. I did not reinstall Windows and all of my required software in a new VM.
comment:4 by , 16 years ago
Yes, I was. I did not change any settings after the upgrade. But, I did look through the settings pages after the upgrade.
comment:5 by , 16 years ago
Try turning off VT-x/AMD-V in the advanced settings dialog to see if that helps.
comment:6 by , 16 years ago
I am having no problems booting XP SP2 or Vista Home Premium (Same Host OS with 2.1.2)
- Upgraded from 2.1.0.
- Wasn't using VT-x previously.
- Did the Guest Additions upgrade.
comment:7 by , 16 years ago
Disabling VTX did not correct the problem.
If I simply uninstall 2.1.2, and reinstall 2.1.0 (replacing the config files with good backups) the VM boots correctly.
comment:8 by , 16 years ago
Interesting blue screen (STATUS_ILLEGAL_INSTRUCTION). Would it be possible for you to create a minidump (http://support.microsoft.com/kb/315263)? I know it's quite a bit of work, but it would be very useful.
So basically turn on minidumps (might already be turned on), go to 2.1.2, boot until the blue screen, reinstall 2.1.0 and then attach the minidump (path in dialog when you boot again) here.
Thanks!
comment:9 by , 16 years ago
I am sure minidumps are enabled; however, I tried several times and did not get any minidump files. The C:\Windows\Minidump folder is empty.
I have a variety of developer (and related) tools installed on that VM. In particular Visual Studio 2008 Pro is installed. Would that impact where the mini dump is being placed? I searched the drive and found no other dump files.
comment:10 by , 16 years ago
I tried enabling kernel dumps as well. Again, no dump was produced.
I took another screen shot of the BS... in case it is of any value.
comment:12 by , 16 years ago
Yes they do.
I tried switching the boot drive to IDE. Still get a BS and no dump file.
I also tried something else. "Safe Mode" works just fine. However, when I try "Safe mode w/ Networking" -- I get a BS (attached).
It appears to die sometime after loading the mup.sys driver. No additional drivers list, but in "Safe Mode" it continues and in "Safe mode w/ Networking" it throws a BS.
comment:13 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 3.1.6.
Upgrading from which version? Did you recreate your VM or just used the existing one?