The latest Fling package designed to answer this challenge is called VMware Tools for Nested ESXi, and it was written by VMware engineer Jim Mattson. Once the package is installed, the virtual machine with the nested ESXi host can run VMware Tools and will therefore function like any other normal virtual machine.
This Fling is currently being offered as a VIB (vSphere Installation Bundle) file. A VIB file is effectively a software installation module for ESXi and is made up of a collection of files packaged into a single archive to facilitate distribution, much like a tarball or zip archive file.
Nesting ESXi has been possible for quite some time now, so why is adding VMware Tools so important? What extra capabilities does this Fling offer someone who is nesting?
- Without VMware Tools, there is no guest-specific information displayed in the vSphere Client for nested ESXi hosts. With this Fling, important guest OS information, such as IP address, configured hostname, and the rest can be identified.
- It allows the nested ESXi VM to be cleanly shut down or restarted when performing power operations with the vSphere Web/C# Client or vSphere APIs. Without it, administrators would have to perform this operation by logging into the VM console, or they'd have to SSH into the ESXi host.
- Administrators can execute scripts that help automate ESXi guest OS operations when the guest's power state changes.
- It adds support for the use of the Guest Operations API (formally known as the VIX API). The API allows administrators to perform guest operations within the VM without needing network connectivity.
Do you have a VMware lab at home? Are you nesting VMware? Will you or have you already tried this Fling to add VMware Tools to your ESXi host virtual machines?
This article, "New Fling installs VMware Tools on nested ESXi virtual machines," was originally published at InfoWorld.com. Follow the latest developments in virtualization at InfoWorld.com.