Virtomation
Automation in a virtually contained world...
Where ESXi belongs - Nested under KVM
25 Mar 2015
I can hear it now, why would you want to do that? Well for me the motivation was I need to test vSphere (ESXi and vCenter) automation and I don’t want to install VMware Workstation to do it.
First up, Nested ESXi
As always dependencies are first. I am using Fedora 21 so the packages commands will be related.
QEMU Changes
Fortunately we have some very smart people at VMware that are willing to help our crazy cause.
QEMU has changed since this post was originally written and so we must modify the patch.
Below are the modifications required for QEMU 2.3, which is the latest development release - your mileage my vary kinda a thing but I haven’t had a problem yet.
With the modified QEMU lets get the source, patch and recompile.
Patch and compile QEMU
This will leave our original QEMU install untouched, which is probably a good thing. Next up we need to define a virtual machine.
Create the ESXi virtual machine
There is an issue with ESXi 5.5 and the e1000 network adapter, so we have no real choice except to use vmxnet3.
Below is an example domain specifically for 5.5 because of the inclusion of vmxnet3 adapter.
ESXi 6.0 can and should be using e1000.
To define a new guest, do the following. A cd-rom will need to be added and most likely source bridge will need to be changed but the general hardware will be correct.
Any of those changes can be done in virt-manager.