Changes between Version 6 and Version 7 of Migrate_Windows

Timestamp:

Aug 6, 2009 5:44:33 PM (15 years ago)

Author:

Klaus Espenlaub

Comment:

--

Migrate_Windows

@@ -4 +4 @@
 
 This document explains the common pitfalls and how to workaround these. We assume that either a physical Windows installation or a VMware image is the source of migration. It is also assumed that a suitable virtual disk image (either VDI or VMDK for !VirtualBox >= 1.4) is already present.
+
+There's a step by step description below.
 
 == HAL ==
@@ -24 +26 @@
 A similar problem may exist with `intelppm.sys`, which can also cause a hang of the guest OS.
 
+= Step By Step Instructions For Windows XP =
 
-After the above steps, your Windows installation should work fine in !VirtualBox.
+This should work for Win2k Vista and Windows 7 as well, but it's untested.
+
+ 1. Run the `MergeIDE` utility as mentioned above on existing windows machine.
+ 1. Shut down windows machine.
+ 1. Either pull the drive from the windows machine or copy the data with a low level image tool (like `dd`) to a USB drive or other removable media.  If making an image, DO NOT image just the partition, this will not work!
+ 1. Use VBoxMange convertfromfaw to convert the image or to copy from the drive you pulled from the windows machine.
+   a. If you are converting from the image, the syntax is just
+{{{
+VBoxManage convertfromraw ImageFile.dd OutputFile.vdi
+}}}
+   a. If you are converting from the drive, you need to use `VBoxManage stdin /dev/sdg OutPutFile.vdi NUMBEROFBYTES`.  Note, if you use `fdisk -l` in Linux you can see how many bytes each drive is to supply this parameter.  Example:
+{{{
+# fdisk-l /dev/sda
+Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
+}}}
+ 1. Then use the media manager in VirtualBox to add the newly converted drive.
+ 1. Make a new virtual  machine, using the drive you just added with the media manager.
+ 1. Once it is created, go in and turn on “Enable IO APIC”, select the # of processors you want etc. 
+ 1. Try to boot the new virtual machine.  It may “just work”, or you may get a BSOD.  If it just works install guest additions and you are done. Depending on your license you might need to re-activate Windows.
+ 1. If it did not work, and you got a BSOD.  Shutdown the virtual machine and boot up from a windows CD.  Go through until you get to the select a partition, select the existing partition, and choose “repair”.  It will basically reinstall windows and configure it for your new hardware (virtual hardware). 
+ 1. Reinstall patches (Service packs) and updates.
+ 1. Install guest additions