Install Ubuntu on ESXi without open-vm-tools and everything seems fine - until the host shows no IP address for the VM, the shutdown button works like pulling the plug, and snapshots cannot talk to the guest. One small package fixes all of it. Here is what it does, how to install it, and how to prove it is working.
On a physical PC, the operating system and the hardware belong together. In a VM they are strangers: ESXi knows the virtual machine exists, but without a messenger inside Ubuntu it knows almost nothing about the guest - not its IP address, not its hostname, not even whether it is safe to shut down. open-vm-tools is that messenger, and VMware itself recommends it as the tools route for Ubuntu. This page covers what you gain, the install, the verification, and the one setting - time sync - where the honest answer surprises people.
The symptoms are small but constant. The VM's summary page on the host shows no IP address, so you are guessing which address to SSH to. Choosing Shut Down Guest OS either fails or behaves like cutting power, risking filesystem damage exactly as a real power cut would. Snapshots cannot ask Ubuntu to quieten its filesystems first. On a Desktop VM, the console will not resize, and copy-paste between your PC and the VM does nothing.
None of these are Ubuntu faults. The guest simply has no channel to report itself. That channel is a small background service - and Ubuntu packages it officially.
Install open-vm-tools and the host and guest start cooperating:
From a terminal in the Ubuntu VM:
sudo apt updatesudo apt install open-vm-toolssudo apt install open-vm-tools-desktop, then reboot the VMsudo systemctl status open-vm-tools - look for active (running)Because it comes from Ubuntu's repository, the package updates with your normal sudo apt upgrade routine and stays matched to your Ubuntu release - which is precisely why VMware points Ubuntu users here instead of the old tools ISO in the ESXi menu.
Virtual clocks drift, and a wrong clock quietly breaks logins, certificates and scheduled jobs. Two mechanisms want the job, and letting both fight is the classic mistake:
timedatectl and enable it with sudo timedatectl set-ntp true. This is the mechanism VMware's own guidance prefers for ongoing syncThe clean arrangement: NTP on, always. Tools installed for everything else it does. If timedatectl reports the clock synchronized and your times match the host's other VMs, stop tuning - time is one of those systems that should be boring.
If the host still shows no guest IP after install, work the short list: reboot the VM once (some reporting starts cleanly after a full boot with tools present); confirm the service is running with the systemctl check above; confirm the VM actually has a working network - tools can only report addresses that exist; and on heavily locked-down hosts, accept that some guest information can be restricted by host-side policy. Nine times out of ten it is the reboot or the missing network, not a deep fault.
The full process on a live ESXi host - creating the virtual machine, installing Ubuntu and fixing the common problems, exactly as they appear on screen.
Watch Full VideoIt is the open-source edition of the same guest tools, packaged and maintained for distributions like Ubuntu, and it is the route VMware recommends for Ubuntu guests. It delivers the same practical benefits - guest information on the host, graceful shutdown, quiesced snapshots - and it updates through apt with the rest of your system.
The apt route needs network access to Ubuntu's repositories. If the VM is offline, fix the network first if you can - the adapter guide in this series covers the usual causes. The legacy fallback is the tools ISO shipped with ESXi, mounted from the VM menu; it works, but it will not auto-update, so treat it as a bridge until the repository route is possible.
Let NTP keep the clock continuously - check with timedatectl and enable it with sudo timedatectl set-ntp true. VMware's own guidance prefers NTP for ongoing synchronisation; the tools sync is best treated as an event-based safety net when a VM powers on or resumes, not as the main timekeeper.