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.

What's the best way to convert a VMWare VMDK HDD file to a HyperV VHD file?

I've been tasked with converting our environment to HyperV for evaluation purposes. We are MSDN subscribers, so the MS software for the job is probably available to me if you know it.

I have been having hit or miss success with "vmdk2vhd" - about half the time it tells me "Invalid vmdk" and as far as I know they should be fine.

share|improve this question
2  
Microsoft launched a new Solution Accelerator "Microsoft Virtual Machine Converter" which includes a plugin for vCenter! technet.microsoft.com/en-us/library/hh967435.aspx –  Garrett Dec 27 '12 at 18:50

7 Answers 7

up vote 6 down vote accepted

I'm hoping there's a better answer than this, but I've read repeated accounts of better success in converting large vmdks by breaking them down into 2gb drives (with VMWare Converter) prior to conversion.

share|improve this answer
1  
While painful, once I used vmware-diskmanager from Workstation to convert the disk into 2GB chunks vmdk2vhd recognized it as a valid VMDK file. Thanks! –  Garrett Jun 15 '09 at 22:12

There are now several tools available to achieve this task. Some of theme have some more functions like converting a running PC to a image and converting to other formats.

One neat little tool is StarWind V2V Converter:

Another one is Vmdk2Vhd from vmToolkit but I have no experience with this one.

If you want to go for the big solution with more functions under the hood you can try VMware vCenter Converter.

share|improve this answer

When I converted to vhd from vmdk using winimage, the resulting file after being added to a new Hyperv VM did not boot and it told me that the version of windows on that disk was corrupt. Running repair from windows image file did not help. The OS is win2k3 SP2.

Is there anything special that needs to be done for this conversion to work properly ?

share|improve this answer

use WinImage 8.1, it can help you to convert vpc images between VHD and VMDK, easy to use and powerful.

share|improve this answer

A few notes, you can't (in my experience) uninstall VMWare Tools "after the fact". Why? Because they keep the converted system from working to the point where you can boot up and log in. At least that was my experience with a Vista conversion.

System Center VMM really is the way to go, even if I can currently having a hard time with it.

J.Ja

share|improve this answer
    
We did install this as an alternative solution as well... So far it's just a glorified hard drive converter and drops all the settings for NICs, HDDs, etc and we have to add all the harware back. Pretty unsatisfied, myself. –  Garrett Jun 18 '09 at 17:21

I've tried converting VMDK to VHD and ended up with a black screen and inability to start Windows after conversion.

Check the following comment thread for issues you may have with VMware drivers and the black screen after convertsion: http://vmtoolkit.com/blogs/announcements/archive/2006/11/20/vmdk-to-vhd-converter-available.aspx

There's an article here with similar or the same information as the comment thread above, but it requires registration: http://searchservervirtualization.techtarget.com/tip/0,289483,sid94_gci1225164,00.html?asrc=SS_CLA_303373&psrc=CLT_94

Finally, this forum thread has similar information as the above two sites: http://vmtoolkit.com/forums/thread/78.aspx

share|improve this answer

Just converting the vmdk to a vhd won't transfer the server to Hyper-V as all the drivers will be wrong. I had to do just the same as you, with about half a dozen VMWare virtual servers. I did it by using the Microsoft System Center Virtual Machine Manager to import the servers just as if they were physical servers. I think the SCVMM is a free download from Microsoft, or at least an evaluation version is available.

Some notes: uninstall VMWare Tools from the virtual servers before you do the import to Hyper-V or they'll give errors when you start the imported Hyper-V servers. My imported servers give occasional w32time errors, but apart from that they work perfectly.

JR

share|improve this answer
    
I don't think I have the time to do a physical import from all the servers... I really just need to be able to convert the VMDKs to VHD and fire them up - can always uninstall VMWare Tools after the fact. –  Garrett Jun 15 '09 at 17:28

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.