In this blog I will explain what changes are need to allow a nested virtual machine to be powered on inside a virtual ESX host. This is something that I have been using to allow for study of the VCAP in a limited LAB situation.
The setup I have is physical ESXi 4.1 hosts on which I made a datacenter and cluster for LAB use. Inside this cluster I built 3 ESXi 4.1 hosts which have to be configured with the following disk configuration and OS selection:
- LSI Logic SAS
- Red Hat Enterprise Linux 6 (64bit)
Once the ESXi 4.1 hosts are built and everything else is configured the vmx file of each host needs to be edited. This will enable the virtual hosts to run virtual machines in the future. The lines that need to be added are as follows (I just added these lines to the end of the vmx file):
- monitor_control.restrict_backdoor = "true"
- monitor_control.vt32 = "true"
To add the above lines to the vmx file will require the file to be downloaded from the datastore and edited (for this I use Notepad++). The edited files are then uploaded back to the datastore (for good measure I remove the virtual machine and add it again to the inventory).
These additions will mean that nested virtual machines are now able to power on and the environment function like a physical one.
By Paul Wood
I would really like to say thanks so much for the work you have made in writing this blog post. I am hoping the same effective work from you in the future as well.
Big help, big help. And superlative news of cosure.
I need to thank you so much for the job you have made in writing this posting. I am hoping the same most effective work by you later on also.
Pingback: Nested VMware vSphere ESXi 5
I like the valuable information you provide in your articles. I will bookmark your blog and check again here frequently. I am quite sure I will learn many new stuff right here! Good luck for the next!
I liked your article is an interesting technology
thanks to google I found you
Good article. Its realy good. More info help me.
hey there and thank you for your information – I’ve certainly picked up something new from right here. I did however expertise a few technical issues using this web site, since I experienced to reload the site a lot of times previous to I could get it to load correctly. I had been wondering if your hosting is OK? Not that I am complaining, but slow loading instances times will sometimes affect your placement in google and could damage your high-quality score if ads and marketing with Adwords. Anyway I am adding this RSS to my e-mail and can look out for much more of your respective interesting content. Make sure you update this again very soon..
This is very helpful, however one question how do you rename the datastores of the nested VM’s. Traditionally on a physical ESX serevr i would do this through the vCenter console itself.
As the nested datastore is within the vdmk file i would assume?