vSphere 5: Creating a Hardware Version 4 VM

I recently had a need to create a VM for usage on ESX 3.x, but the only thing available to me in my lab was vSphere 5, which naturally creates new VMs with the latest and greatest version 8 virtual hardware.

The following table lists the virtual hardware versions and the corresponding ESX and ESXi releases:

**Version**	**Virtual Hardware Version**
ESXi 5.x	8
ESX/ESXi 4.x	7
ESX 3.x	4
ESX 2.x	3

Naturally, an ESXi 5.x host can run VMs created with older hardware versions but it is not possible (through the vSphere Client) to create a new VM with an old hardware version, and I needed to create a v4 VM for later export to an ESX 3.x host.

Of course, I could have created the VM on the ESX host that it was supposed to run on on the first place, but the host in question was unavailable at the time and the plam was to prepare the VM off site before deployment in the production environment.

Since I did not have a valid license for ESX 3.5 any more, the easiest way I found to create a hardware version 4 VM, and configure it on vSphere 5, was to use Easy VMX to create the basic VM (vmx file) instead of hacking away at creating it manually.

Easy VMX created the .VMX file that I needed to register a hardware version 4 VM to a ESXi 5.x host, and edit it through the vCenter client. Of course, it creates disk files that are incompatible with ESX but that´s of no concern as you can just remove the invalid devices and add new ones through the vCenter client.

All in all this little “trick” worked without a hitch, and the small Linux machine I had set up for the client worked perfectly when deployed on the old ESX 3.5 install.

Of course, the best option would be to reinstall the old ESX 3.5 host with ESXi 5, but as this was a system due to be decommissioned very soon that was not a real option for the client. The main purpose of the VM I created was to act as an alerting system for incoming email, warning that the email addresses had changed to a new domain, and emails sent to the old one would not be read or acted upon.

Related Posts

• Using rsync to Distribute Patches to a Remote vMA — Published 8 Mar, 2011
• Using vMA as a local vSphere Patch Repository — Published 7 Mar, 2011
• Installing vSphere Management Assistant (vMA) — Published 28 Feb, 2011
• VMware vSphere Health Check - What´s in it for You? — Published 4 Dec, 2012
• VMware ESXi 4 vs ESXi 5 Log File Locations — Published 17 Sep, 2012