Optimizing Windows VM performance on QEMU and KVM

Running a Windows guest virtual machine on a Linux host is straightforward with standard type-2 hypervisors like VirtualBox, but those setups introduce noticeable overhead in CPU execution, disk I/O, and graphics latency.

Running applications on bare-metal KVM (Kernel-based Virtual Machine) achieves near-native performance. Unlocking that potential requires paravirtualized VirtIO drivers, Hyper-V enlightenments, and targeted guest OS optimizations.

Prerequisites and host preparation

This guide covers configuration and performance tweaks using Virtual Machine Manager (virt-manager) on Linux hosts.

Ensure the virtualization stack is installed and running on your Linux host:

sudo systemctl enable --now libvirtd.service
sudo systemctl status libvirtd.service

Before creating virtual machines, add your user account to the relevant virtualization groups to avoid permission prompts:

sudo usermod -aG libvirt $USER
sudo usermod -aG libvirt-qemu $USER
sudo usermod -aG kvm $USER
sudo usermod -aG input $USER
sudo usermod -aG disk $USER

Download the necessary installation media before proceeding:

• A clean Windows 10 or 11 installation ISO.
• The latest stable virtio-win.iso driver package from the official Fedora VirtIO repository.

Virtual machine configuration

When creating the new virtual machine in Virtual Machine Manager, check Customize configuration before install on the final creation step.

Storage bus configuration

In the customization window, navigate to your VM disk storage and change the Disk bus from SATA or IDE to VirtIO.

Dedicated storage drive passthrough offers the highest throughput if a spare physical NVMe or SATA drive is available. For file-backed storage, VirtIO with QCOW2 or raw images provides substantial I/O improvements over emulated SATA.

Network and video devices

Change the Network Interface device model to virtio to enable paravirtualized network throughput and reduced host CPU overhead.

For video output without dedicated PCIe GPU passthrough, select QXL as the video model.

Attaching VirtIO driver media

To load the storage driver during Windows setup, attach the driver ISO as a secondary CD-ROM device:

1. Click Add Hardware in the bottom-left corner.
2. Under Storage, select Select or create custom storage and click Manage.

3. Locate the downloaded virtio-win.iso file.
4. Set the device type to CDROM device and the bus to SATA or IDE.

5. Click Begin Installation at the top left to boot the virtual machine.

Windows setup and driver injection

When the Windows installer starts, select Custom: Install Windows only (advanced).

The drive list will appear empty because Windows does not bundle VirtIO SCSI drivers natively. Click Load driver.

Browse to the attached virtio-win CD-ROM drive and select the storage driver directory matching your target Windows architecture (for example, viostor\w10\amd64).

Once the driver loads, the virtual disk will appear immediately. Proceed with the standard partition creation and OS installation.

Guest tools and SPICE integration

After completing the initial Windows setup and reaching the desktop, open File Explorer and navigate to the mounted virtio-win CD drive.

Execute virtio-win-guest-tools.exe to install all remaining paravirtualized drivers, including network (NetKVM), balloon memory management, and serial communication.

Accept the default selections and complete the driver package installation.

Installing SPICE guest tools

To enable dynamic display resizing, clipboard sharing, and smooth mouse pointer integration, download the latest spice-guest-tools package from the official SPICE repository.

Download and run the spice-guest-tools Windows installer package.

Hardware channels and hypervisor features

Shut down the guest to add management channels and hypervisor enlightenments.

QEMU guest agent and watchdog

In virt-manager, add a new Channel device with the name org.qemu.guest_agent.0. This enables the host to perform clean ACPI shutdowns, query IP addresses, and freeze filesystems for consistent snapshots.

Optionally, add a watchdog device (such as i6300esb) with the default reset action to automatically reboot the guest if the kernel hangs.

Hyper-V enlightenments configuration

Hyper-V enlightenments allow KVM to emulate Windows-specific hypervisor interfaces, reducing virtualization overhead and clock synchronization drift.

Enable direct XML editing in virt-manager preferences:

1. Open Edit -> Preferences from the main Virtual Machine Manager menu.

2. Check Enable XML editing.

3. Open the VM details, switch to the XML tab, and add the following <hyperv> block inside <features>:

<features>
  <hyperv>
    <relaxed state='on'/>
    <vapic state='on'/>
    <spinlocks state='on' retries='8191'/>
    <vpindex state='on'/>
    <runtime state='on'/>
    <synic state='on'/>
    <stimer state='on'>
      <direct state='on'/>
    </stimer>
    <frequencies state='on'/>
  </hyperv>
</features>

4. Add the hypervclock timer inside the <clock> section:

<clock offset='localtime'>
  <timer name='hypervclock' present='yes'/>
</clock>

Operating system storage optimizations

Reclaim disk footprint and reduce host image inflation by tuning guest maintenance settings.

Disable hibernation

Virtual machine state can be managed directly by KVM snapshots. Disabling Windows hibernation removes hiberfil.sys, immediately saving gigabytes of disk space:

powercfg -h off

Component store cleanup

Clean up superseded update packages using the Deployment Image Servicing and Management (DISM) tool in an elevated command prompt:

dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

Disk cleanup automation

Pre-configure Windows Disk Cleanup with all cleaning categories:

cleanmgr /sageset:0

Execute the cleanup pass:

cleanmgr /sagerun:0

Trim and drive optimization

Run the Windows Drive Optimizer. When running over VirtIO SCSI with discard support, Windows detects the volume as a thin-provisioned drive and issues TRIM commands back to the host filesystem:

defrag C: /O

Operational review

With VirtIO drivers, Hyper-V enlightenments, and OS-level trimming applied, the Windows guest operates with low CPU baseline utilization, responsive graphics, and fast disk access.

This architecture separates host resource management from guest execution, delivering a high-performance Windows environment suitable for development and productivity tasks directly on Linux.