Hello,
I have an image created on a real pc that I'd liketo apply to a virtaul box VM. When I try it, the machine hangs on boot up. I assume i need to add drivers to the image before applying it but does anyone know what drivers?
Thanks.
Applying a Syspreped Image to new VM?
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Applying a Syspreped Image to new VM?
Can you boot to safe mode?
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Applying a Syspreped Image to new VM?
A hang on startup (as opposed to a BSOD on startup) is often caused by having the IO APIC setting wrong (meaning: set different to what the XP image was previous installed on and using). Modern PCs typically have this feature turned on.
If you didn't do any preparation of the image then you'll probably get BSODs after fixing the hang. The preparation most needed for an XP guest is to run MergeIDE on it, to make XP more tolerant of IDE controller type changes. If you don't do this you typically get a BSOD: stop 0x7B.
It can also help to delete agp440.sys and intelppm.sys from the system32\drivers folder of the image. These drivers are optional, but they can also cause BSODs when they try to access graphics card or processor features that don't exist in the VM.
Most other problems, e.g. orphaned drivers, can be fixed in the VM - in fact the mini setup run by sysprep may get them all.
Only once you've got the VM to boot should you remember to install the VirtualBox GAs.
If you didn't do any preparation of the image then you'll probably get BSODs after fixing the hang. The preparation most needed for an XP guest is to run MergeIDE on it, to make XP more tolerant of IDE controller type changes. If you don't do this you typically get a BSOD: stop 0x7B.
It can also help to delete agp440.sys and intelppm.sys from the system32\drivers folder of the image. These drivers are optional, but they can also cause BSODs when they try to access graphics card or processor features that don't exist in the VM.
Most other problems, e.g. orphaned drivers, can be fixed in the VM - in fact the mini setup run by sysprep may get them all.
Only once you've got the VM to boot should you remember to install the VirtualBox GAs.