Proxmox VMware Tools – How to Install VirtIO Drivers and QEMU Guest Agent

Editor’s Note: Updated on 14 June 2026: Added internal links to related Proxmox guides, refreshed the VirtIO driver version notes, and reviewed the QEMU Guest Agent installation steps for the latest Proxmox VE release.

What is the equivalent of VMware Tools in Proxmox?

If you’ve just migrated from VMware to Proxmox, you might be wondering what to install instead of VMware Tools. In VMware ESXi, this package is essential because it includes both drivers and a guest agent that improve performance and integration. While you cannot directly install VMware Tools in Proxmox, you can achieve similar functionality by installing VirtIO drivers and the QEMU Guest Agent, which together provide the features you get when you install VMware Tools on a VMware guest OS.

So the short answer: Proxmox doesn’t use VMware Tools. Instead, you need to install two components:

• VirtIO drivers → for storage, network, and memory ballooning
• QEMU Guest Agent → for integration with the Proxmox host

Together, these provide the functionality you’re used to in VMware. In this guide, I’ll show you exactly how to install them on Windows and Linux.

---

What Are VMware Tools in Proxmox?

VMware Tools in Proxmox enhance the performance of guest operating systems in virtual machines.

VMware Tools is a bundle of two things:

• Device drivers (network, storage, graphics, mouse integration)
• Guest agent (shutdown, time sync, freeze/thaw for backups)

In Proxmox, this is split into separate components:

• VirtIO Drivers → high-performance drivers for disk and NIC, plus the VirtIO balloon driver for RAM optimization. These provide near-native performance.
• QEMU Guest Agent → The QEMU Guest Agent enables advanced features such as graceful shutdown and time synchronization between the guest and host in Proxmox.

If you’re in the process fron moving from VMware ESXi host, make sure VirtIO drivers are installed before migration for better performance. I highly recommend it. I cover in detail in my VMware to Proxmox migration guide.

---

VMware Tools vs. Proxmox Equivalent

Here’s a quick side-by-side look:

Feature	VMware Tools	Proxmox Equivalent
Storage Drivers	✔ PVSCSI	VirtIO Block/SCSI
Network Drivers	✔ VMXNET3	VirtIO NIC
Guest Agent (shutdown, time sync, freeze/thaw)	✔	QEMU Guest Agent
Memory Ballooning	✔	VirtIO Balloon Driver
Graphics / Mouse Integration	✔	Limited (basic drivers)

---

Installing VirtIO Drivers and QEMU Guest Agent on Windows

If you just installed or migrated a Windows VM, you’ll likely need to install both VirtIO drivers and the QEMU agent. You will find the both tools on the same ISO file

If you are starting from scratch, I also wrote a step-by-step guide to installing Windows Server on Proxmox with VirtIO drivers.

See the picture below of the VirtiO ISO file

• marked blue arrow: VirtiO driver for 64bit
• marked green arrow: QEMU Windows guest tools

Step 1 – Enable QEMU Guest Agent in Proxmox

• Go to VM → Options → QEMU Guest Agent → Enable.

Step 2 – Mount VirtIO ISO

• Download the latest virtio-win ISO from the official Proxmox website and upload it to your Proxmox environment. I have a separate article explaining how to upload and ISO image.
• Mount the ISO to your VM via the Proxmox GUI.

Step 3 – Install VirtIO Drivers

• Inside Windows, open the mounted ISO.
• Install virtio-win-gt-x64.msi (64bit) or virtio-win-gt-x86.msi (32bit)
• This will install all the necessary packages for the Windows vm guest operating system.

Step 4 – Install QEMU Guest Agent

• From the the same ISO,
• Run virtio-win-guest-tools.exe
• Complete the installer.

Step 5 – Verify Installation

• Open Services.msc and confirm “QEMU Guest Agent” is running.
• In Proxmox, check the Summary tab of the VM — the IP address should now show up correctly.

---

After installing Open VM Tools, the guest operating system may require a restart to apply changes.

If VirtIO drivers do not behave as expected, it can also help to check the current Proxmox GitHub issue tracker for known Windows driver problems and recent fixes. That is especially useful if you suspect a driver-specific issue rather than a Proxmox configuration problem. Based on my experience, the latest VirtiO drivers are not always the best.

Installing QEMU Guest Agent on Linux

Linux makes this much easier, since VirtIO drivers are built-in. You only need the QEMU Guest Agent. For Linux it is important that you enable the QEMU Agent first – see above Step 1 – before installing it on Linux Debian / Ubuntu

Debian / Ubuntu

sudo apt update
sudo apt install qemu-guest-agent -y

Verify the service

systemctl is-enabled qemu-guest-agent
systemctl status qemu-guest-agent

Then in Proxmox, check the Summary tab for the guest IP.

---

Verifying Integration in Proxmox

Once installed, you can test the agent directly:

qm agent <VMID> ping

Other ways to confirm:

• Shut down the VM from the Proxmox GUI → it should gracefully power off.
• Check if the IP address shows under the VM Summary.
• Run a backup → Proxmox should use freeze/thaw hooks from the agent.

---

If you’re setting up Proxmox in a homelab, a mini-PC like the Minisforum MS-01 is a solid choice.

Common Issues and Fixes

Even though installing the QEMU Guest Agent and VirtIO drivers is usually straightforward, there are a few common problems you might run into:

1. No IP address showing in Proxmox

• Ensure the QEMU Guest Agent is enabled in the VM options and installed/running inside the guest. (NIC model doesn’t matter. If you changed to a VirtIO NIC on Windows, also install the VirtIO NIC driver so networking works.)
• Fix: mount the VirtIO ISO, install the network driver, then reboot the VM.

2. QEMU Guest Agent not running

• On Linux, check with:
• If it shows as inactive, start it with sudo systemctl start qemu-guest-agent.
• On Windows, open services.msc and verify the QEMU Guest Agent service is running and set to Automatic.

3. Driver signing issues on Windows

• Older VirtIO ISO builds sometimes throw driver signing errors during installation.
• Fix: always download the latest stable VirtIO ISO from the official Fedora project. That ensures the drivers are properly signed and compatible.

Backups failing or not consistent

• If you notice snapshot backups failing or not freezing the filesystem, it usually means the QEMU Guest Agent isn’t fully integrated.
• Fix: make sure you’ve both enabled the Guest Agent in the Proxmox VM options and installed it inside the VM. A reboot after installation often helps.

5. Service won’t enable on Linux

• Some Linux distributions use socket activation, so you may see an error when running systemctl enable. This doesn’t mean the agent is broken.
• Fix: enable the socket instead:

By double-checking these points, you’ll avoid the most common pitfalls and ensure your VM integrates properly with Proxmox.

---

Looking for budget-friendly hardware to run Proxmox?
Renewed servers from Amazon are a great way to get enterprise-grade performance at a fraction of the price. Below are some solid options I recommend that readers of my blog have already picked up.

Wrap-Up

If you’re searching for “Proxmox VMware Tools”, the answer is simple: For a deeper understanding of the QEMU Guest Agent, the official documentation is available here.

• VirtIO Drivers = performance (disk, NIC, memory balloon).
• QEMU Guest Agent = integration (shutdown, time sync, IP reporting).

Install both after migrating to Proxmox, and your VMs will behave just like they did with VMware Tools — sometimes even faster.

Haven’t migrated yet? Check out my article to install Proxmox virtual environment and how to migrate from VMWare.