I recently posted an article about how to use VMware’s free tool “vCenter XVP Manager” to manage Hyper-V with vCenter (see post Managing Hyper-V with VMware vCenter XVP Manager and VIDEO: Control Hyper-V Servers in vCenter with XVP Manager and Converter).
Those tools push you to use VMware Converter to convert your VMs running on Hyper-V to vSphere. I am a big proponent “freedom of choice” and standardization in virtualization that would allow you to convert easily from one hypervisor to another. Virtualization should be an open market where you choose the best virtualization platform available and you can easily move there. You shouldn’t be stuck in a platform you don’t want to be in, primarily because you don’t have an easy option to move.
In this article, let me show you how to use another free tool to go the opposite way, from vSphere to Hyper-V. That tool is the free 5Nine V2V Easy Converter. While you could do this with Microsoft System Center Virtual Machine Manager (SCVMM), that program isn’t free nor is it easy to implement (for more information on that topic see this article by Janique Carbone – Performing a V2V Conversion from VMware vSphere to Hyper-V R2 Using System Center VMM 2008 R2 or this video by Ed Lieberman- VIDEO: How to Convert a VMware Virtual Machine to a Hyper-V virtual machine).
Three Reasons to V2V
Before I show you HOW to perform a V2V (vSphere to Hyper-V), let’s first answer the WHY question. Why would you want to move from vSphere to Hyper-V?
- Testing Hyper-V – let’s say that you want to prove that an application runs just as well (or even as poorly) on Hyper-V as it does vSphere. You could do a V2V and try it out. You could also just test out Hyper-V, if you haven’t used it before, with an existing VMware vSphere VM.
- Conversion – when a company is bought, sold, or consolidated, there are always scenarios where you would want to move from one platform to another.
- Production – with VMware being so popular, many VMs are run in vSphere or saved in VMware’s formats. It is very likely that you need to move production VMs from vSphere to Hyper-V
Bonus reason: “because you want to”. Everyone should have the freedom and ease of moving a VM from one platform to another. After all, that is one of the things that virtualization first enabled – hardware independence, portability, freedom, and choice in your hardware – you should also have that in your virtualization option.
Downloading and Installing V2V Easy Converter
Recently, I came across a new V2V tool for going from vSphere to Hyper-V, currently in a beta preview mode. V2V Easy Converter from 5Nine is free (at least the beta preview is), simple to use, tiny to download, fast to install, and it works. Here’s what I did…
I downloaded V2V Easy Converter (which didn’t take long as it is under 2MB). It was the typical Windows install, only a little shorter because it is so small.
vSphere to Hyper-V VM Conversion, Step by Step
The general process of performing a V2V, no matter what the two platforms are, is:
- Capture the VM’s configuration and create a VM with the same configuration on the other hypervisor
- Copy the VM’s virtual disk and convert it to the other hypervisor’s virtual disk format (such as VMDK to VHD)
- Replace the virtualized device drivers in the guest OS (inside that virtual disk) with the virtual device drivers for the new hypervisor
No matter what V2V application you use, this is the general process that happens in the background.
To get started with this V2V conversion using our tool, I ran the icon in the Windows start menu called 5Nine EasyConverter. When the converter comes up, it shows you a series of blanks for you to fill out, across a few screens, in easy wizard-format.
It starts with the selection of the source. In other words, what ESXi server or vCenter server will we contact to find the virtual machine that you want to convert?
It scanned the vCenter server I specified and then gave me a list of the VMs I could convert.
Note that, today, these VMs must be Windows 2008 or Windows 7 (or newer) VMs and that they must be powered off. Later, it will be supported to convert older operating systems and, perhaps, powered on VMs.
I selected the VM I wanted to convert, gave the new VM a name, and specified the hardware resources it will consume over on the Hyper-V server I was moving it to.
Next, I entered the name of my Hyper-V server and used the “assess” option to see if it was a suitable host for the VM that I want to convert there.
From there, I took the defaults for the VM paths on the Hyper-V server and selected what virtual networks this new VM would have access to.
Next, I reviewed a final summary of what was about to happen and opted to power on the VM once it was converted.
After clicking Finish, the VM started its conversion. Being as this VM has a 200GB thinly provisioned virtual disk (that only had 11GB in use), I was curious to see how long this would take and exactly what would happen. It took a while (on my slow lab network) but I saw that the virtual machine had been converted (as in Figure 7, below).
Over in the Hyper-V Manager, I could see that a new VM had been converted and I could even see the size of the VM’s virtual disk had 12GB in use of the maximum 200GB virtual disk (almost identical to the original).
I can even access the console of the converted VM to prove that it worked.
At this point, our conversion from vSphere to Hyper-V is done!
What Did We Learn?
What did we learn through this V2V process?
- There are a number of reasons you would want to convert VMs from vSphere to Hyper-V and you should have an easy option to do so if you choose (freedom of choice, just like in a free market economy). Reasons include testing, learning, and consolidation of production VMs.
- That, besides System Center Virtual Machine Manager (a great product but a product with a price), there is another option that is tiny, free, and works if you are just looking for V2V conversion
- That converting a VM from one hypervisor to another doesn’t have to be difficult when you have tools to help