Install or Upgrade VMware Tools

— ny_wk

To install or upgrade VMware Tools on a Linux virtual machine, the modern, supported method is to install the open-vm-tools package from your distribution's repository rather than mounting the legacy bundled installer. This guide covers both approaches: the current best practice (open-vm-tools), the legacy ISO-based vmware-install.pl workflow you may still meet on older vSphere estates, and how to verify the result.

VMware Tools is the set of drivers and userspace daemons that lets a guest operating system cooperate with the VMware hypervisor (ESXi). On Linux, installing or upgrading VMware Tools gives you proper graphics and network drivers, time synchronization, graceful shutdown from vCenter, quiesced snapshots, the balloon memory driver, and clean copy/paste in the console. Without it, a VM runs, but it runs blind to the host.

Why VMware Tools matters and which version to install

There are two distinct families of the toolset, and choosing the right one is the single most important decision:

• open-vm-tools — the open-source implementation, maintained on GitHub and shipped in the package repositories of virtually every modern Linux distribution. VMware (now part of Broadcom) officially recommends open-vm-tools for all supported Linux guests. It updates through your normal package manager, so you never re-run an installer after a kernel upgrade.
• The bundled VMwareTools-*.tar.gz (operating system specific packages / OSP / Perl installer) — the legacy tarball you mount as a CD-ROM and unpack with vmware-install.pl. This method is deprecated and removed from current vSphere releases. You will only encounter it on old ESXi 5.x/6.x hosts or images that predate open-vm-tools adoption.

If your distribution offers open-vm-tools (it almost certainly does), use it. Reserve the tarball method for genuinely legacy environments where it is the only option.

open-vm-tools vs the legacy installer at a glance

The problem this solves

You provisioned a Linux VM and the console reports “VMware Tools is not installed” or “VMware Tools is out of date.” Symptoms include the VM not shutting down gracefully from vCenter, the wrong screen resolution, no time sync, failed quiesced snapshots, or a warning banner in the vSphere Client summary tab. The fix is to install the correct toolset and confirm the daemon is running.

Recommended method: install open-vm-tools

Connect to the guest over SSH (PuTTY on Windows, or a terminal on macOS/Linux) and run the command for your distribution as root or with sudo. There are two flavours: a headless package for servers and a desktop package that adds drivers for the graphical console.

Debian / Ubuntu

1. Refresh the package index:
   sudo apt update
2. Install the headless toolset (servers):
   sudo apt install -y open-vm-tools
3. On a VM with a desktop environment, add the desktop drivers instead:
   sudo apt install -y open-vm-tools-desktop

RHEL / CentOS / Rocky / AlmaLinux / Fedora

1. Install with the system package manager:
   sudo dnf install -y open-vm-tools
2. For desktop/GUI guests, also install:
   sudo dnf install -y open-vm-tools-desktop
3. On older RHEL 7 / CentOS 7 systems use yum instead of dnf:
   sudo yum install -y open-vm-tools

SUSE / openSUSE

1. Install via zypper:
   sudo zypper install -y open-vm-tools
2. Desktop variant:
   sudo zypper install -y open-vm-tools-desktop

Enable and start the service

On almost every modern distribution the package enables the service automatically. Confirm it, and start it if needed:

1. Enable on boot and start now in one command:
   sudo systemctl enable --now vmtoolsd
2. Check it is active:
   systemctl status vmtoolsd

That is the complete, supported install. No reboot is normally required, and future kernel and security updates flow through your package manager.

Legacy method: install or upgrade VMware Tools from the mounted ISO

Use this only where open-vm-tools is genuinely unavailable, typically older ESXi hosts. The workflow mounts a virtual CD-ROM containing the tools ISO, then runs the Perl installer inside the guest.

Step 1 — mount the tools ISO from vCenter

1. Log in to the vSphere Client (vCenter) and locate your VM in the inventory.
2. Right-click the VM and choose Guest OS > Install/Upgrade VMware Tools (on older clients this lives under the VM menu).
3. In the dialog, select Interactive Tools Upgrade/Installation and click Mount. This attaches the tools ISO to the VM's virtual CD-ROM drive.

Step 2 — mount the CD-ROM inside the guest and unpack the tarball

SSH into the guest as root and run:

1. Create a mount point and mount the optical device:
   mkdir -p /mnt/cdrom
mount /dev/cdrom /mnt/cdrom
2. List the contents to find the exact tarball name (the version number varies):
   ls -l /mnt/cdrom/
3. Extract it to a working directory — substitute the real filename you just saw:
   tar -zxvf /mnt/cdrom/VMwareTools-*.tar.gz -C /tmp/

Tip: the original instruction to extract directly from /mnt only works if you mounted there; always extract from wherever the ISO is actually mounted, and use the * wildcard so you do not mistype a long version string.

Step 3 — run the installer

1. Change into the unpacked directory:
   cd /tmp/vmware-tools-distrib
2. Run the installer accepting all defaults (note the two hyphens — it is --default, not a single dash; the en-dash that often appears in copied notes will fail):
   sudo ./vmware-install.pl --default
3. If prerequisites such as perl or kernel headers are missing, install them first (for example sudo apt install -y perl build-essential linux-headers-$(uname -r) on Debian/Ubuntu) and re-run.

Step 4 — unmount and clean up

1. Inside the guest, unmount the CD-ROM:
   umount /mnt/cdrom
2. Back in the vSphere Client, the summary tab may prompt to disconnect the tools installer — confirm Yes / OK to eject the ISO from the virtual CD-ROM.
3. Reboot if the installer requested it:
   sudo reboot

Migrating from the legacy installer to open-vm-tools

If a VM already carries a Perl-installed copy and you want to switch to the supported package, uninstall the old version first to avoid conflicting files and daemons:

1. Run the bundled uninstaller:
   sudo /usr/bin/vmware-uninstall-tools.pl
2. Then install the package as shown above (for example sudo apt install -y open-vm-tools).

From that point forward, upgrading VMware Tools is simply part of your routine patching — there is nothing special to do.

Common pitfalls

• Copying the dash wrong. Documentation frequently renders --default as an en-dash. Type two plain ASCII hyphens or the flag is ignored.
• Hard-coding the version string. Filenames like VMwareTools-9.4.15-2827462.tar.gz change between releases. Use ls and a wildcard rather than copying an old name.
• Missing kernel headers. The legacy installer compiles modules and fails silently without the matching linux-headers/kernel-devel package.
• ISO not actually mounted from vCenter. If mount /dev/cdrom reports “no medium found,” the Install/Upgrade VMware Tools action was never triggered, or another ISO is attached. Trigger it again in the vSphere Client.
• Choosing the wrong package. Installing open-vm-tools-desktop on a headless server pulls in unnecessary X11 dependencies; use the plain open-vm-tools package for servers.
• Forgetting to enable the service. Installing the package without systemctl enable --now vmtoolsd on a minimal image can leave the daemon stopped, so vCenter still reports tools as not running.

Verification: confirm VMware Tools is installed and running

Validate from both inside the guest and from vCenter.

1. Check the daemon is active:
   systemctl status vmtoolsd
2. Query the version and status with the toolbox command:
   vmware-toolbox-cmd -v
3. Confirm the host's view of the tools status:
   vmware-toolbox-cmd stat raw text session
4. In the vSphere Client, open the VM's Summary tab. The VMware Tools field should read Running, version: ... (Guest Managed) for open-vm-tools, instead of Not installed or Out of date.

If the Summary tab still shows a stale status, give the daemon a moment to report, or restart it with sudo systemctl restart vmtoolsd.

Key Takeaways

• Prefer open-vm-tools from your distro repository — it is the supported method and updates automatically with the system.
• Use open-vm-tools for servers and open-vm-tools-desktop for guests with a graphical console.
• The legacy vmware-install.pl ISO method is deprecated; keep it only for old ESXi estates, and always discover the real tarball name with ls.
• Type --default with two real hyphens, and install kernel headers before running the Perl installer.
• Verify with systemctl status vmtoolsd, vmware-toolbox-cmd -v, and the vCenter Summary tab.

Frequently Asked Questions

Is open-vm-tools the same as VMware Tools?

Functionally yes for Linux. open-vm-tools is the open-source implementation that delivers the same guest integration — time sync, graceful shutdown, quiesced snapshots, drivers — and it is the version VMware (Broadcom) recommends for supported Linux distributions.

Do I need to reboot after installing VMware Tools on Linux?

With open-vm-tools a reboot is normally not required; the service starts immediately. The legacy vmware-install.pl installer often asks for a reboot because it compiles and loads kernel modules.

How do I upgrade VMware Tools to the latest version?

If you use open-vm-tools, upgrading is just sudo apt upgrade / sudo dnf upgrade as part of normal patching. For the legacy installer you must mount the newer ISO from vCenter and re-run vmware-install.pl.

Why does vCenter still say VMware Tools is not running after install?

The most common causes are a stopped daemon (run sudo systemctl enable --now vmtoolsd), a stale Summary tab that needs a refresh, or an old Perl-installed copy conflicting with the new package — uninstall it with vmware-uninstall-tools.pl first.

For more Linux and virtualization walkthroughs, subscribe on YouTube @explorenystream.