In this post we’ll look at how to convert a Hyper-V virtual machine using the VHDX format virtual disk to a VMware Workstation virtual machine using the vmdk format virtual disk.
Until Windows 8 I’ve used VMware Workstation for testing, but with the advent of Windows 8 and the built in Hyper-V I decided to give it a try and have been using it quite happily ever since. In the near future though I’m going to be looking at some vSphere testing, and from memory recall that you can nest it within VMware Workstation, so I thought I would give the latest version a go.
The only problem is I don’t want to rebuild my current test environments so I need some way of converting the VHDX that Hyper-V uses to vmdk that VMware Workstation uses.
You have to register to download the product, but once you have and installed it below are the steps I took to convert a UEFI Boot, Gen 2, 2012 R2, Hyper-V VM using VHDX to vmdk for VMware Workstation.
In this post I will look Inspecting and Editing virtual disks in Hyper-V. In a previous post I looked at creating a vm template to deploy virtual machines from. The template used a Dynamically expanding virtual hard disk, so although the virtual machines’s operating system would see it as 127GB it’s actual size at deployment was 18GB, and it will grow as required up to its specified maximum size.
This is great for keeping storage usage down while testing or for templates storage, but in a production envrionment it is best practice to deploy fixed disks to increase disk throughput.
If you have deployed a Windows Server 2012 R2 generation 2 virtual machine on 2012 R2 Hyper-V server you may find that Windows Update fails on any generation 2 virtual machines.
Generation 2 virtual machines use UEFI rather than BIOS. UEFI is a firmware interface to the hardware that will gradually replace BIOS on newer hardware. It is more secure than BIOS and designed to protect pre-boot prcesses from attack, improve startup times and support larger disks, as well as a number of other enhancements.
So a Generation 2 virtual machine uses UEFI, and therefore has the EnableSecure Boot option enabled by default.