“VM tools” is the umbrella name for the guest-side utilities that make a virtual machine usable: the paravirtualized drivers, the time-sync daemon, the memory balloon, the shutdown channel, and the file-copy channel. Without them the VM boots, runs, and slowly goes wrong.
Table of contents
- What the term means
- The driver layer
- Time sync
- The memory balloon
- The shutdown channel
- Why the guest sometimes doesn’t see the network
- Installing the guest tools on Linux
- FAQ
What the term means
Each hypervisor has its own name for the same idea. VMware calls it VMware Tools. Hyper-V calls it Hyper-V Integration Services (now bundled in the kernel). KVM calls it qemu-guest-agent plus the virtio drivers. The team that switches platforms needs to know that the conceptual layers are the same even when the names differ.
The driver layer
The most important piece: the paravirtualized drivers. On KVM, the virtio-net driver is 5-10x faster than the emulated e1000. On VMware, the vmxnet3 driver is the equivalent. On Hyper-V, the vmswitch driver. Without these, the guest falls back to slow emulated hardware and the team wonders why the network is slow.
Time sync
The guest clock drifts. Without a sync channel, the guest is seconds off after a week, and Kerberos, TLS certificates, and database replication start to break. The fix on KVM: qemu-guest-agent. The fix on VMware: VMware Tools time sync. The fix on Hyper-V: Hyper-V Time Sync Service. The fix on every platform: NTP, in addition to the hypervisor channel.
The memory balloon
The balloon driver lets the hypervisor reclaim memory from a guest that does not need it. The guest thinks the memory is allocated to it; the hypervisor thinks it is free. The right answer for most workloads: turn the balloon on, but set a minimum reservation so the guest does not get starved.
The shutdown channel
Without a shutdown channel, shutdown now on the guest is a hard power-off. The hypervisor does not know the guest is shutting down; the next start is a crash-consistent boot. The fix: install the guest agent and the hypervisor can issue a graceful shutdown through the channel.
Why the guest sometimes doesn’t see the network
The four reasons the VM loses network connectivity:
- Driver mismatch. The guest has the e1000 driver instead of vmxnet3. Performance is slow and the driver might not support all features. Install VMware Tools / virtio drivers.
- Bridged mode without DHCP. The VM is bridged to the host’s network but no DHCP server is available. Set a static IP or run a DHCP server on the host’s network.
- VLAN tagging. The host’s network is on a VLAN the VM doesn’t know about. Configure VLAN tagging on the VM’s NIC.
- Firewall. The guest OS firewall blocks the connection. The team that sees the host can ping the VM but the VM can’t ping the host has a guest firewall issue.
Installing the guest tools on Linux
The right commands for each platform:
- VMware Tools (Linux).
sudo apt install open-vm-toolson Debian/Ubuntu.sudo dnf install open-vm-toolson Fedora/RHEL. - VirtualBox Guest Additions (Linux).
sudo apt install virtualbox-guest-additions-isoand mount the ISO. - KVM/QEMU guest tools (Linux).
sudo apt install qemu-guest-agenton Debian/Ubuntu.sudo dnf install qemu-guest-agenton Fedora/RHEL.
The team that installs the right package has clipboard sharing, dynamic resolution, and time sync working out of the box.
FAQ
Do I need VM tools for a Linux VM?
Yes, if you want good network and disk performance and reliable shutdown. The qemu-guest-agent package plus the virtio drivers are the equivalent of VMware Tools on Linux.
Are VM tools open source?
KVM virtio drivers and qemu-guest-agent are GPL. VMware Tools is proprietary but the Open VM Tools (open-vm-tools) package is the standard install on Linux. Hyper-V Integration Services are now bundled in the Windows kernel.
Why is my VM slow without VM tools?
The guest is using emulated hardware (e1000 NIC, IDE disk). Paravirtualized drivers give 5-10x better throughput and lower CPU usage.
Can I run a VM without VM tools?
Yes, but expect slow I/O, drifting clocks, and unclean shutdowns. It is fine for a quick test; it is not fine for production.
Are VMware Tools still maintained?
The open-vm-tools package is maintained by VMware and the Linux distribution maintainers. Yes, it’s still updated for security and feature additions. The closed-source VMware Tools (shipped with VMware Workstation/ESXi) is also still maintained.
What happens if I don’t install guest tools?
Slow network, slow disk, no clipboard sharing, no dynamic resolution, drifting clock, and no graceful shutdown. The VM still works, but it’s a worse experience.
Can I use VMware Tools on KVM?
No. VMware Tools is VMware-specific. Use qemu-guest-agent for KVM. The two have similar functionality but are not interchangeable.
If you are sizing the infrastructure for the kind of project this post covers, the RunxBuild hosting calculator is the right place to model the line items. The compute, the memory, the storage, the bandwidth, the database - each one is a separate number, and the team’s mental model for the platform is the sum of those numbers. The RunxBuild dashboard is where the team sees the actual usage in one place.
Useful related references: