)
Usage
To install Virtio Win Driver (Install), run the following command from the command line or from PowerShell:
choco install qemu-virtio-driver
To upgrade Virtio Win Driver (Install), run the following command from the command line or from PowerShell:
choco upgrade qemu-virtio-driver
To uninstall Virtio Win Driver (Install), run the following command from the command line or from PowerShell:
choco uninstall qemu-virtio-driver
Description
VirtIO drivers for Windows guests on QEMU/KVM
This package installs the official virtio-win drivers from Red Hat for Windows guest systems in QEMU/KVM environments (e.g., Proxmox VE, libvirt, oVirt/RHV, OpenStack). The paravirtualized drivers improve performance and integration compared to fully emulated devices.
Included components (depending on guest and selected hardware)
- NetKVM (VirtIO network)
- viostor / vioscsi (VirtIO block / SCSI)
- Balloon (memory ballooning)
- viorng (VirtIO RNG)
- vioinput / vioserial
- optionally qxldod / SPICE display drivers
What this package does
- Installs VirtIO drivers via the official MSIs (virtio-win-gt-x86/x64.msi)
- Deploys signed (partly WHQL-certified) drivers for the relevant device classes
- Suitable for unattended/automated deployments with Chocolatey
Not included
- QEMU Guest Agent (install separately): Chocolatey package: https://community.chocolatey.org/packages/qemu-guest-agent
Compatibility and requirements
- Windows 10/11 and Windows Server (per upstream support)
- Administrator privileges required; a reboot may be required
- Hypervisor: QEMU/KVM (e.g., Proxmox VE, libvirt)
Verification after installation
- Device Manager: VirtIO devices should bind to Red Hat drivers (NetKVM, viostor/vioscsi, etc.)
- Optional: verify driver versions under Properties → Driver
Disclaimer
This Chocolatey package is community-maintained and is not created, endorsed, or supported by the Red Hat.
To use choco:// protocol URLs, install (unofficial) choco:// Protocol support
Please Note: This is an automatically updated package. If you find it is out of date by more than a day or two, please contact the maintainer(s) and let them know the package is no longer updating correctly.