Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.
1  
r u doing v2v or p2v? Also do you mean the version that worked with virtual server 2005? Hope not since thats older then the hills. –  tony roth Apr 18 '12 at 18:32

1 Answer 1

up vote 1 down vote accepted

Don't use that, it doesn't work with Hyper-V (if you're still running Virtual Server you'd better be planning an upgrade, soon). The SysInternals Suite includes Disk2VHD, which can do the conversion, though you'll likely have to muck with the disk drivers or the virtualized system will not boot (you'll end up with a STOP 7B.

The general steps for using Disk2VHD:

  1. Run chkdsk /x and defrag on the drive(s) you're going to convert.
  2. Muck with the IDE settings. There are MergeIDE programs and websites to help guide you through this if the KB article above isn't clear enough. It's a pain to do this after the next step, so do it here.
  3. Run the Disk2VHD program, create the VHD files.
  4. Copy the VHD files to your Hyper-V host (KVM can convert VHDs, and Xen uses them natively as well). Create the VMs pointing to the VHDs and try to get the virtual hardware as similar to the physical as possible.
  5. Install the Hyper-V Integration Services (paravirtualization drivers). Switch Emulated NICs to Synthetic (only if you had emulated installed to get the networking going before HIS.

If you're going to be doing this on multiple machines I'd recommend a fully automated tool. Microsoft provides this functionality in SCVMM, which you can download a free trial of too. There are other utilities out there, Acronis and others.

Full Disclosure: I work for an MS Partner

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.