The best tool for converting virtual machines to Hyper-V is System Center Virtual Machine Manager 2008, which is available in October 2008. It has a physical to virtual (P2V) tool that works quite well. Unfortunately, it has to be installed on a domain joined machine, so it's not suitable for ad hoc, spur of the moment P2V conversions done by anyone, any time, anywhere. Sometimes you have just one virtual machine on Virtual PC or Virtual Server you need to migrate to Hyper-V. If you don't have a P2V tool, you have to recreate all of the settings because Hyper-V doesn't use vmc files.
Matthijs ten Seldam wrote a vmc converter utility to simplify the creation of settings for a Hyper-V virtual machine. Read about it here: http://blogs.technet.com/matthts/archive/2008/09/12/vmc-to-hyper-v-import-tool-available.aspx. You still have to deal with HAL issues, for which a complete article would be required to discuss in depth. If your virtual machine's operating system is Vista or 2008 Server, the HAL problem is easy to deal with because those operating systems have a new option in msconfig to force HAL detection. It's accessed by clicking the Advanced Options button on the Boot tab. You use this after booting your virtual machine in Hyper-V for the first time.
When you manually migrate a VPC or Virtual Server vm to Hyper-V, the basic approach is to do this:
- Copy the vhd and work with the copy.
- Uninstall the Virtual Machine Additions.
- Copy the modified vhd to the Hyper-V machine.
- Use the wizard to create a new virtual machine from the vhd or use the vmc converter.
- Resolve any HAL problems.
- Install Integration Services.
If you have access to SCVMM 2008 RTM, you can install it into a Hyper-V virtual machine if that is more convenient for you. You can even have it in its own virtual domain on your laptop or desktop. I find this approach more convenient and agile for ad hoc work than having it part of a production domain.