SOLVED: Restoring WinXP .tib to Virtual Box with BSOD
I have carefully searched the forum and KB for all posts on this subject, but must in the end approach the experts here to request advice...
I have VirtualBox v4.1.6 installed in a Win7 Pro partition on my laptop. I installed a WinXP CD into VB and use this working IDE Primary Master to inspect a formatted IDE Primary Slave for whatever VHD's or .tib file content I might attempt to load to it. So much for the background.
I have built a BartPE with ATIH 2012 and the Plus-Pack for a universal restore. It works fine booting into VBox and restoring a 2012 .tib of my old Win-XP partition.
I pre-prepped the old WinXP partition by installing IDEreg (registry mod to relax IDE constraints), stripping out most programs and hardware-dependent apps, setting some services to Manual, defragging, chkdsk'd, etc, before backing up all 5Gb to a .tib on an external USB HD.
Ok, then: I booted BartPE in the VBox and recovered the .tib from the USB HD into the IDE Primary Slave. Options used: I restored the partition, sector-0, and the MBR (all 3 choices near the end of the wizard). I also checked the Recover Signature box. It ran to completion.
I rebooted into my working WinXP VHD as IDE Primary Master and verified the recovered files on the 2nd drive. I then shutdown, deattached the working WinXP disk, and made the recovered disk the IDE Primary Master. Rebooted.
The Win logo appeared, and the blue progress-bar sequence made it halfway through before the BSOD. I tried booting into Safe-Mode, but the display doesn't make it past the first line of d347bus.sys before the BSOD again.
Let me say that in the past 3 days I have tried all kinds of combinations in attempting to migrate WinXP to VBox, including the VMWare Stand-Alone Converter, RAW disks built in Linux, and VBoxManage conversions (at which I am now a master).
In almost every case I get this BSOD at the same point in booting, despite trying other VB controllers and system options. I must conclude that I am missing a driver or two for my Virtual Box.
Before you direct me over to their forum, I'm wondering if any of you can suggest something further with ATIH (and yes, I've tried using its converted VHD instead of a .tib)...
Thanks for listening.
- Log in to post comments
Thanks for replying, MudCrab -- good points.
Yes, I did check UR.
The BSOD has always been error 0x000000vB. [ EDIT: "7B" ]
I enabled IO APIC.
I enabled PAE.
#processors is greyed out in the System | Processor tab, but set to 1.
I've tried all manner of controller settings and chip-sets.
I pre-prepped to hopefully keep issues to a minimum. It did take me two days to realize that I needed SP3 on the source partition...!
[ EDIT: MudCrab is right: either SP2 or SP3 will work. ]
- Log in to post comments
Dave:
Have you tried de-attaching the working primary virtual disk, attaching the target virtual disk as the primary IDE master, and then restoring the saved image file to what is now the primary IDE disk? In other words, do the restore operation to a target virtual disk that is in the same position as the source virtual disk was when the backup was created.
- Log in to post comments
I assume you mean 0x0000007B. "v" isn't a valid hex number. This error usually means the storage drive installed is incorrect. Are you sure you're using the correct drivers for VBox?
XP SP3 shouldn't be required, but it does make it a lot easier.
- Log in to post comments
MudCrab -- yes, it's 7B, usually caused by incorrect controller drivers as I understand from Microsoft support pages. And no, I think the drivers needed for VBox are not in my XP source partition.
When one installs fresh from a CD, the drivers are obviously in place from the CD. Just which ones they are will take me too long to determine, so I will approach this from another angle: migrating from the XP source to my working VHD using PCmover.
Mark -- I tried to set up your idea of installing into a Master Primary Drive, but the Acronis Recovery Disk is reacting badly today with both my laptop touchpad and my USB mouse, so had to give it up for now. I'm sure it's a controller driver problem and hence in VB's domain -- not an Acronis problem.
Thanks to you both for your interest.
Dave
73's --> HS0ZGR / K2DZ 55 km's SE of Vientiane, Laos
- Log in to post comments
After 5 days of effort, I solved the BSOD problem and booted successfully. There was a missing IDS controller driver in the .tib source. [ EDIT: The tutorial at [ http://www.runpcrun.com/move-windows-xp-to-new-system-or-motherboard helped me find the missing driver. ]
It's still not 100% because the ATIH 2012 recovery process using UR (running from an ISO) aborted halfway through with (typically) no reason given. If it happens again, I'll look for an event log. I'm not hopeful of finding any, since I'm booting ATIH Recovery from an ISO.
I'll write up a short tutorial here to help others.
- Log in to post comments
MIGRATING A WinXP PARTITION TO VIRTUAL BOX
(Notes to myself to make the next migration
an easier, less stressful affair)
==================================
Background setup:
----------------------
WinXP SP2 partition in laptop with an IDE disk controller.
Win7 SP1 partition in same laptop with installed Virtual Box v4.1.6, and Guest Additions loaded.
VBox has a new VM into which was installed WinXP-SP2 via CD to have a bare-bones, clean, working WinXP machine for comparison and a driver database source at various stages of the procedure.
---- The VHD is VDI, small, dynamically allocated, set to Primary Master.
---- System | Enable IO-APIC box was checked (else couldn't view the Win-logo at boot time, giving a black screen).
---- The Network adapter is Bridged, "cable-connected" box checked.
---- Once up and running, network-drives were mapped to other laptop partitions.
---- Shared folder was set up with the host Win7 partition.
The objective: to migrate the source WinXP partition into a destination VBox VM.
Tools used for migration:
------------------------------
Acronis v10.0 (10 years old) installed in the WinXP partition.
(I had no success using ATIH 2012 and its Universal Recovery feature.)
An Acronis Recovery v10.0 ISO stored in the Win7 partition for booting into the target VM. (Generated from within the Acronis app on the WinXP partition for Full-mode only -- not Safe-mode w/o USB drivers.)
A BartPE ISO for booting into VM containing partition tools like Symantec's DriveImage tool PTEDIT32.exe to re-"active" the target VHD if Acronis recovery aborts, thereby locking the primary partition. I also put PQBoot32.exe here in case of multi-boot difficulties. (PartitionMagic Utility Tool).
The tutorial at [ http://www.runpcrun.com/move-windows-xp-to-new-system-or-motherboard ] to pre-prep the old WinXP partition with the IDE controller drivers needed at VM boot time, hopefully avoiding the all-too-common "7B" BSOD.
Download MergeIDE.reg -- to be merged into the WinXP source partition's registry to relax UUID constraints on installing IDE controller drivers during booting into the target partition. I believe MergeIDE is the registry merge-code mentioned in the above web tutorial, but the link has been blocked. Microsoft Support *suggests* using this code in their BSOD support pages, but they do not support or "recommend" it.
Pre-prepping the WinXP source partition:
---------------------------------------------------
First: verify the presence of the WinXP IDE controller drivers in the working VM by browsing to C:\Windows\System32\drivers and looking for these (4) drivers ---> ATAPI.SYS, INTELIDE.SYS, PCIIDE.SYS, and PCIIDEX.SYS One may be missing, but those present MUST also appear in the source WinXP partition. (I was missing INTELIDE.SYS in the .TIB backup, causing a "7B" BSOD for a heart-breaking number of days in trying to boot the new VM).
Uninstall anti-virus, 3rd-party firewall, and wireless-adapter apps. Or, otherwise disable them.
Change the Startup mode of 3rd party services from Automatic to Manual or Disabled.
Remove any hardware-dependent apps if that hardware will be unavailable on the VM.
Clean up the disk partition (using CCleaner).
Defragment and Chkdsk the partition.
Check that C:\boot.ini refers to Drive 0, partition 1.
Examine the "C:\Windows\System32\drivers" folder to check if the (4) drivers mentioned above agree with those found in the working WinXP VM. If not, follow the web tutorial above to add them. It takes only minutes, but saves so much grief.
Apply MergeIDE.reg to the registry by clicking on it.
Migration procedure:
-------------------------
With the Acronis app running in the old, source partition, back it up to another local partition, or to an external USB HD.
Boot into the Windows[7] partition on which VBox is already installed.
I use PQBoot32.exe to do this: it hides and otherwise locks the source partition (and any other Primary partitions) while making the Win7 partition Active.
Create a new destination VM in VBox with a fixed-length VHD of sufficient size to receive the recovered .TIB file. This new file must be formatted from within a running VM, or using VBoxManage.exe in the Virtual Box Program Files folder.
I found it easier to attach the working WinXP VHD file to the new VM, making it Primary Master with the target fixed file as Primary Slave. After booting up, right-click on My Computer | Manage | Storage | Disk Management, and Initialize, then Format the Primary Slave, which is probably Disk 1. Check the sizes to be sure. The Acronis recovery app to follow will make it Active and bootable.
Shut down the new VM. In the Storage tab, de-attach the working Primary master VHD, change the newly formatted target VHD to be Primary master, and click the IDE Controller entry to add a CD device. Click "Choose disk" to select the Acronis Recovery .ISO file for booting.
Start up the VM. It should boot immediately into the ISO to run the Acronis Recovery of the source partition .TIB to the destination fixed, formatted VHD. I selected "Make Active" and did not restore the MBR.
At the successful completion of the recovery (using Acronis v10.0, they have ALL been successful), shut down by "Send the Shutdown Signal". De-attach the ISO file, and click the System | Enable IO-APIC box.
Reboot and enjoy...
Addendum:
-------------
Some guest drivers may not install themselves correctly after initial booting. Check for yellow warnings in the System | Device Manager. Compare Driver Details in the Property Box to those in the original working VM for WinXP. Usually the correct driver package (with the all-important .inf file) is cached in the Windows folder and can be copied over to the target VM via shared folders in the host Win7 file system and installed.
Summary:
-----------
It's a nice learning exercise, but I have to conclude that the VM with the CD install of WinXP runs so much faster than the restored (migrated) VM. System problems which existed on the source partition are also migrated to the new VM.
I will try migrating from the source partition to the CD-installed one using PCmover...
- Log in to post comments
Dave:
I tried a similar image and restore operation with TI 10 when moving an XP VM from Virtual PC to VMWare and ended up with BSODs and many driver issues also. After several attempts I got it working (sort-of) but wasn't happy with the outcome. Then I found out that VMWare has a utility called VMWare VCenter Converter, which is for converting virtual hard disks of different formats or physical hard disks with Windows installed on them into VMWare-compatible VHDs. I ran it and it worked perfectly. I don't know if VirtualBox has a converter program available, but if they do it may be worth a try.
- Log in to post comments
Virtual box can convert VHD's to VDI's, the hard way or the easy way! :)
Hard way is via esoteric command line entries, the easy way is via Don Milne's Virtual HD Clone Utility with GUI front end. Unfortunately I can't remember where I downloaded it from (possibly the VirtualBox forum), but search for the above name or mpack (his user name on the virtualbox forums).
- Log in to post comments
@ColinB this is the thread you are looking for: https://forums.virtualbox.org/viewtopic.php?f=6&t=22422&sid=50a4b495c66…
- Log in to post comments
That is the one, thanks RayG.
- Log in to post comments