Make your Live system into a VHD

this is nice, but I'd guess that most of the time the converted VHD won't boot inside a virtual machine. After cloning the files to the virtual disk, it's quite often that registry and system files need to be tweaked in order to boot.

For example, dual core XP, will not boot inside a vm with a single virtual cpu.

We will soon release MyOldPCs converter, which converts live system to vmdk/vhd/vdi, and can boot via vmware/vpc/vbox/hyper-V, etc. More info can be found here:

http://www.vmlite.com/index.php/products/myoldpcs/
(website still work in progress)

The hardware needs to be changed from physical machine to virtual machine.

for example, you will have to enable IntelIde, PCI, and disable Intelppm, etc. for the hard disk controllers.

Windows XP uses different kernel images and HAL for single cpu and multiple cpus. In modern times, physical computers are usually dual core, while virtual machine usually only has one cpu. So if you move windows xp vhd without any changes, it won't boot.

There are many more stuff, mouse/keyboard, may freeze without changes, etc.

This change is the challenging part, cloning a disk is now a mudane task on XP and later systems that supports Volume Shadow Copy. On other systems, it's very tough.

We have implemented our own disk snapshot drivers on Windows 2000/xp/2003/vista/7/2008 (note MS does not have snapshot driver on 2k).

We have also implemented a disks snapshot driver on Linux 2.6, so can perform hot clone on Linux too

My knowledge of VM/VHD interaction is essentially non-existant, but huisinro's comments seem to be at odds with Russinovich's description of Disk2vhd operation.

Disk2vhd

where e.g. at the end of the page he shows a screen shot with the following caption:

"Here’s a screenshot of a copy of a Windows Server 2008 R2 Hyper-V system running in a virtual machine on top of the system it was made from:"

But I also see (or misunderstand) a slight contradiction to that when he says

"Note: do not attach to VHDs on the same system on which you created them if you plan on booting from them. ..."

as the disk signature assigned to the vhd will not match that in the captured image.

So, what is the real story? Has the vhd being used in the screenshot had something tweaked, or a lot tweaked as huisinro suggests, or am I totally misunderstanding Russinovich's words, or ...?

I would really like to understand.

Roger

As it so says...

On first boot, a VM booting a captured copy of Windows will detect the VM’s hardware and automatically install drivers...

However, Windows XP is sadly not image aware therefore capturing it and then moving to a VM is a real chore. Windows Vista and Seven are imaging aware and can be moved around different machines. Just read a bit up on the WAIK documentation, it covers a lot of this kind of stuff.

Ah, thanks logicearth, I didn't know about WAIK. I'd seen a reference to AIK in a recent post, and finding out exactly what it referred to was just another of those tuits that I hadn't yet gotten around to!

I've d/l the documentation and I'll look at it this afternoon.

Roger

The image shows Windows 2008 R2 running inside hyper-V virtual machine. I am not sure about these two combinations. It all depends on the original physical machine, the guest operating system and the virtual machine software. For instance, you don't need to do anything to clone Linux and run as VM. On the other hand, For Windows XP, you have to tweak it a lot.

Our MyOldPCs converter handles all complicated cases in order to make the cloned virtual disk to boot.

Give you another example, for ThinkPad laptops, you will have to modify the virtual disk's number of BIOS disk heads, otherwise p2v XP won't boot.