Implementing a Multi-Node Hypervisor Cluster on a Single Desktop Running VMware Workstation 8
As a field consultant for the last several years, I have been amazed at the numerous deployment scenarios that can be reproduced utilizing just one piece of physical hardware. Due to increasingly expensive electrical bills I trimmed down my server class lab hardware nearly a year ago in favor of a megadesktop that could handle anything I threw at it. While dual-, tri- and quad-boot scenarios have given me the ability of running ESXi, XenServer, Hyper-V, and Windows 7 natively on the hardware, it has been difficult to reproduce complex multi-node hypervisor cluster scenarios without wrangling additional equipment. With the release of VMware Workstation 8 and Nested 64-bit Virtual Machine support, hardware assisted virtualization technologies (Intel-VT/AMD-V) can now be passed through to virtual machines!
The screenshot above visually demonstrates the power and capabilities to nest Hyper-V R2, XenServer 6, and ESXi 5 directly into VMware workstation to evaluate or reproduce countless deployment scenarios. Attempting to install the Hyper-V role would likely result in the following unrecoverable error:
Additionally, for Hyper-V, you must modify the VMX file and add the following line:
hypervisor.cpuid.v0 = FALSE
While XenServer allows you to proceed through the following error, functionality is severely impacted:
Similarly, ESXi allows you to proceed through the following error but will limit you to running only 32-bit virtual machines:
Now that I’ve shown you all of the expected errors, let’s configure VMware Workstation 8 to allow nested 64-bit virtual machines thus resolving all three of the above notifications.
First, the desired virtual machine must be upgraded to Hardware Version 8. In VMware Workstation, right click the virtual machine and go to Manage -> Change Hardware Compatibility. Click Next and validate Workstation 8 is selected from the drop-down.
If a lower version was previously selected, VMware Workstation will prompt to determine if you want to “Create a new clone of this virtual machine” or “Alter this virtual machine.”
Second, the Virtualize Intel VT-x/EPT or AMD-V/RVI checkbox must be selected within the Virtual Machine Settings. In VMware Workstation, right click the virtual machine and go to Settings. Select the Processors node and check the bottom box on the right hand side:
Both options require a shutdown and restart of the virtual machine in order to apply, so it’s highly recommended to perform both changes with the desired virtual machines shutdown. Upon boot, these virtual machines will now support Hypervisor installations within VMware Workstation including support for 64-bit Nested Virtual Machines!
Additional details for setting up 64-bit Nested Virtual Machines within ESXi 5 clusters can be found on the VMware Communities site at http://communities.vmware.com/docs/DOC-8970
Feel free to comment below if you would like any further information on setting up Multi-Node hypervisor clusters nested in VMware Workstation 8. Thanks so much,
Seem to me nobody can answer a simple question:
Is it possible to run a hypervisor on top of a cluster?
This question is the reverse idea of what this article wants to show: running a cluster on top oa a hypervisor.
Unfortunately, while you can run XenServer using your tips, when you try to install VM on nested XenServer and apply Xen Tools on that machine, VM with XenServer crashes. I’m using Workstation 8.0.2 and have tried to run VM on nested XenServer several times. Each time result was the same.
Nice article and helpful
This is a nice article Dane, might be time for me to downsize and get a more powerful desktop as well, this seems pretty convenient. You have some great articles on your site, good work sir.
This is very nice, did you use a laptop for this.?
My main lab rig is a desktop class system, but I have spun up single VM hypervisors on my laptop as well. Usually only do that if I need something validated from a hypervisor perspective in a pinch and don’t have access to my lab.