If you have found yourself in a scenario where you would like to use Hyper-V as a test environment for your virtual machines, but you are using VMware ESXi Server,Citrix XenServer or VirtualBox then this tutorial is for you.
Note: this method will work for any virtualization platform that supports exporting it’s virtual machines in OVA format.
In this article we are going to detail the steps required to convert an OVA export from ESXi into a VHDX file for use with Hyper-V. The first thing you need to do is get an OVA export from ESXi. To do this you must first open the VMware vSphere Client and shutdown the virtual machine you would like to export. Once the shutdown is complete, you will want to select “File > Export > Export OVF Template” as seen in the picture below. 
Required software
- Microsoft Virtual Machine Converter 3.0 available here.
- Your OVA export unzipped into a folder.
Preparations
- Download and install Microsoft Virtual Machine Converter 3.0.
Convert The Image
Next we will need to convert our VMware Image in order for Hyper-V to run it. This can be done using Powershell as seen below.
# Import the Converter Powershell Module Import-Module "C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1" # Convert the VMware .vmdk to a Hyper-V .vhdx ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath "D:\Debian8\Debian8-disk1.vmdk" -DestinationLiteralPath "D:\Debian8.vhdx" -VhdType DynamicHardDisk -VhdFormat Vhdx
Using The Image
In order to use our newly created image we must first create a new Hyper-V virtual machine or edit one that has been previously created. Important notes below.
- When creating your new virtual machine, you must ensure you select “Generation 1” when choosing the generation of the virtual machine.
- The converted image can be moved to any location you choose.
Once you have completed all the steps above, you should have a fully working copy of your virtual machine running on Hyper-V.
Here’s the fix for the disk descriptor issue.
https://blogs.technet.microsoft.com/stevemoore/2017/06/08/convert-vmdk-to-vhd-fails-with-the-entry-2-is-not-a-supported-disk-database-entry/
Awesome tip, Thanks Robert
I have to say that I tried this approach for VMWare and VirtualBox machines and only the first seemed to work. When trying to convert a VirtualBox OVF export (regardless if it’s 1.0 or 2.0 OVF) I always get an error from Powershell like: “ConvertTo-MvmcVirtualHardDisk : The entry xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx is not a supported disk database entry
for the descriptor.”
I get the same error. Interesting.. Will post if I find a fix.
I think this might help you.
http://techfans.org/index.php/2017/10/23/convert-an-ova-open-virtualization-format-file-to-a-vhd-file-hyper-v/
Thanks for the info Shanky.
perfect ! Thanks 🙂
Amazing! You Saved me a lot of time ( I have spent a lot of time looking for this way already). Good move to use PowerShell.