Problem solve Get help with specific problems with your technologies, process and projects.

Microsoft Virtual Machine Converter eases VM migrations

For admins managing both vSphere and Hyper-V in the data center, Microsoft Virtual Machine Converter may mean fewer VM conversion headaches.

Microsoft released version 1.0 of MVMC, a standalone appliance for migrating VMware vSphere VMs to Hyper-V VMs. A vCenter plug-in that goes by the same name allows these conversions to occur within the vCenter client. Will these products really make life easier for virtual admins?

Some VMware customers may suffer from déjà vu when they read about Microsoft Virtual Machine Converter (MVMC). The virtualization vendor offered its own conversion software pair until 2010.

VMware Converter Enterprise was only available to enterprise customers as a plug-in to vCenter, while VMware Converter Standalone was available to anyone with a valid VMware account. VMware did away with the Enterprise edition in 2010, dropped Standalone from the name of the other converter and now offers VMware Converter  free to anyone.

What's new in MVMC and how is it different from VMware Converter?

I found both editions of MVMC very easy to use and understand. The vCenter plug-in and the standalone application are almost identical, except for two additional wizard panes in the standalone application that ask for your vSphere login credentials and to select a VM.

With the MVMC plug-in, you right-click on an existing VM in vCenter and select the option Convert to Hyper-V virtual machine from the context menu. This takes you through a short wizard asking for parameters, such as the powered-on state of the virtual and physical machine after the conversion, the workspace or temporary folder location, and which server you want to host the VM.

More resources on VM conversion

For virtualization disaster recovery, use P2V conversion

Top five P2V conversion obstacles

V2V and V2P workload migrations concerns

There are a few notable differences between VMware Converter and MVMC. First, VMware's tool performs physical-to-virtual (P2V) conversions; Microsoft's tool cannot. Microsoft's converter also lacks customization features in both the conversion wizard and the VM's operating system configuration. Lastly, the Microsoft converter cannot perform a cold clone, which means the VM must be powered on (i.e., hot) for the conversion to proceed.

And when it comes to their ability to convert virtual disks from VMware's .VMDK format to Hyper-V's .VHDX format (previously .VHD format) without having to house them on a target host, both the VMware Converter and MVMC lag behind some third-party disk conversion tools, such as the StarWind V2V Converter. The ability to convert from one virtual hard disk format to another from a single interface would be a huge improvement. I am hopeful Microsoft (and possibly VMware) will add this functionality in later releases.

I had hoped MVMC would be a more universal conversion tool, allowing P2V, virtual-to-physical and virtual-to-virtual conversions. Unfortunately, this isn't the case. Admins hosting separate vSphere and Hyper-V environments in their data centers will appreciate MVMC, version 1.0, but others will want to hold out until the vendor creates a do-it-all conversion tool.

Dig Deeper on P2V, V2V and V2P migration

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

Which conversion tool do you use in your data center?
I found vConverter very easy to use and I have not with any P2V and V2V conversions.
Platespin powerconvert
Used Starwind V2V and worked perfectly, maybe a few network card config issues after the conversion but they generally work when first turned on.
I'm using the system internals
Disk2vhd v1.63
Then the WinImage converter
I then load the result into VMWARE player and select keep the old format
Drop any ATI drivers on first boot which typically have hooks to USB etc..
And have moved metal to SAAS with no hassles
As an example: VMWARE Converter on a FX8150 8 core box with Win7 fails miserably, but with the process I outline above "no problema" and I can run the winimage in a VM :-0

Best of luck but you have to know you know and not read yourself to confusion
Easy to use