Conclusion
It might not be the best for performance, but this setup is pretty good for proof of concept and laboratories if you already have an existing environment. I was even able to install vCenter Server Appliance though with a bit of pain.Thanks to Jitze Couperus for the amazing image on the top.
Thanks to: Matt’s blog and The Perils and Triumphs of Being a Geek blog, from which I gained many information that are part of this guide.
Image courtesy of mark | marksei
The following two tabs change content below.
The IT guy with a slight look of boredom in his eyes. Freelancer. Current interests: Kubernetes, Tensorflow, shiny new things.
Latest posts by mark
- 2020 A year in review for Marksei.com — 30 December 2020
- Red Hat pulls the kill switch on CentOS — 16 December 2020
- OpenZFS 2.0 released: unified ZFS for Linux and BSD — 9 December 2020
Creating the Virtual Machine
This step is quite straightforward: you just need to create the new virtual machine, but you need to pay attention to three options:
ESXi Nested – OS Type
ESXi Nested – CPU Type
ESXi Nested – Net Type
- OS Type must be “Other OS Types“.
- CPU Type must be “host“.
- Network Type must be “VMWare vmxnet3“.
Now, take note of the machine id that you used during the installation. SSH in the node hosting the newly created virtual machine and edit the file named: /etc/pve/qemu-server/YOURVMID.conf (of course replace YOURVMID with the ID of the virtual machine you created). And add at the end of the file:
args: -machine vmport=off
Beware!
Each and every time you will modify things through the Proxmox interface, you will lose all the custom changes to this file. Unfortunately I have yet to come up with a simple way to avoid this without using glued solutions or configuration management.
In this way you should be able to complete the ESXi installation without problems. However, when you will try starting your first virtual machine, you will notice that you can’t start virtual machines inside of the ESXi host.
