After poor marketing design vRAM past, Vmware has made another mistake on restricting of free license of ESXi. The free version of ESXi makes you only run VMs on host which has no more than 32GB memory.
This change (in my opinion, it’s also a wrong decision again!) pushes all customers from Vmware side to Microsoft side and also with no free licensing on Test and DR environment (which means you have to buy Essential Kits to cover Test and DR Hosts), we are facing no options but start to use Hyper-v in all tests environment.
One of most important elements of using Hyper-V is to convert existing VMWARE VMs to Hyper-V server.
MVMC (Microsoft Virtual Machine Converter) is one of tools you will use during the process of converting from Vmware vSphere to Microsoft HYPER-V.
Now, you will face some common issues and I hope this post will help you save some time.
My test environment:
1 Hyper-v Windows 2012 server
1 Vmware ESXi 4.1 with Windows 2008 R2 VMs
The goal is to convert VM from vmdk to VHD and up running in the Hyper-V
MVMC actually has two parts.
1. MVMC to move VM with both CLI and GUI.
2. MVDC (virtual Disk Converter) to only convert disks from vmdk to VHD.
Now, if you run the MVMC Gui, you will get this interface,
You are required to type ESXi or vCenter information here to get access to VM list. Behind the scene, What it does is to access ESXi web API to check VM lists on that ESXi.
As you can see, here is where you select your VM to be converted. The BLUE exclamation mark indicates that VM can’t be converted. There are quite few reasons why a VM can’t be converted, but on this picture, State is “OFF” and another VM without Vmware Tools can’t be converted.
Now, here is the interesting part. A login user can be used here directly, and notice it says Final State of VM is ON or OFF?
Again, it’s Final State of VM. It’s not all time states. so the original VM will be shutdown no matter what and it’s up to you to make it start again at the end.
If you want to convert VM on the fly without shutdown a VM, this is not the tool you should use.
Behind the scene, MVMC talks to ESXi to get snapshot of original VM while it’s running, the snapshot should include memory status as well. so estimate free size of VM storage.
Once snapshot is done, it removes Vmware tools and shutdown the VM. Then, it will export VM as OVF template which essentially isolate VM from hypervisor hardware layer. If your VM is a Microsoft TMG, then you probably don’t want to do that since TMG remembers the MAC of it’s nic and stored it in it’s own database. Now, there is a way to “hack” TMG, but this post doesn’t include it.
But I strongly suggest to use a UNC with share to store VMs.
This is where VM will sit. Now, according to Microsoft, it requires at least double the size of VM. As matter of fact, it requires triple size space rather than double.
Behind the scene, Like what I mentioned above, a OVF template has been generated. Now, OVF template is a compress format, so a 50GB vm can be compressed around 13GB. so this 13GB is downloaded to \\testhyp02\vmdk folder and MVMC will start convert it to 50GB vhd. After that, 50GB vhd will be copy (or upload) to Hyper-V VM location so that’s another 50GB, compressed if you use Dynamic disk. finally occupied Size is 13+50+50=113GB.
Now, when you see this page, you are pretty happy that VM has been converted and insert into HYPER-V and up running.
Now, remember this is VM from OVF, so some clean up must be done.
install new version of Integrated Service.
If you don’t install this integrated service, those hardware can’t be identified.
It does warn you the OLD IP exists, but after overwritten IP, it seems working. If you want to show hidden device of that old NIC, you won’t be able to find it.
Now, What’s Wrong?
MVMC has used multiple Microsoft technology in terms of converting.
The most common error you will get is this.
You can find log file here.
Now, for Windows 2008 R2, I recommend you to do following steps.
1. Enable Winrm
Winrm allows Windows server (2012 in this case) to remotely manage VM in terms of removing Vmware Tools.
2. Enable Server manager Remote management which will create FW fules
3. Make sure FW rules exception is ticked
3. You need to enable WMI and File and Print rules on FW no matter FW is on or OFF.
Now, after you have enable all three tricks, you can run some simple test.
For WINRM, you can run “winrs /r:yourTestServer ipconfig” from your MVMC server. If it shows result, then WINRM is working.
for WMI, you can download WMI administrator Tools and remote access root folder of VM, if you can see content, then it means it’s working.
Restart MVMC wizard and try again.
What about convert VM on the fly without shutdown ?
I’m not quite sure whether any software can do that at this stage. But You DO can clone a VM to an isolated network. run VM and import it to Hyper-V with MVMC.
For large size disk VM, you may want to use MVDC to convert disk and build a VM in Hyper-V and insert disk.
please let me know any thoughts.
following is answer from Microsoft for converting V2V on the fly.
Answer back from some of our Hyper-V guys…
It’s “possible” to perform a P2V conversion on a VMware virtual machine using Virtual Machine Manager, which leverages VSS to take the required snapshots while keeping the target machine online. However, it’s required to remove the VMware client tools first, which will probably require a reboot anyhow.