Jan 31, 2019 KVM/QEMU Windows guest drivers (virtio-win) This repository contains KVM/QEMU Windows guest drivers, for both paravirtual and emulated hardware. The code builds and ships as part of the virtio-win RPM on Fedora and Red Hat Enterprise Linux, and the binaries are also available in the form of distribution-neutral ISO and VFD images.
This repository contains KVM/QEMU Windows guest drivers, for bothparavirtual and emulated hardware. The code builds and ships as partof the virtio-win RPM on Fedora and Red Hat Enterprise Linux, and thebinaries are also available in the form of distribution-neutral ISOand VFD images. If all you want is use virtio-win in your Windowsvirtual machines, go to theFedora virtIO-win documentationfor information on obtaining the binaries.
If you'd like to build virtio-win from sources, clone this repo andfollow the instructions in Building the Drivers.Note that the drivers you build will be either unsigned or test-signedwith Tools/VirtIOTestCert.cer, which means that Windows will not loadthem by default. See Microsoft's driver signing pagefor more information on test-signing.
Proxmox Windows 10 Drivers
If you want to build cross-signed binaries (like the ones that ship inthe Fedora RPM), you'll need your own code-signing certificate.Cross-signed drivers can be used on all versions of Windows except forthe latest Windows 10 with secure boot enabled. However, systems withcross-signed drivers will not receive Microsoft support.
Virtio Drivers Windows10
If you want to produce Microsoft-signed binaries (fully supported,like the ones that ship in the Red Hat Enterprise Linux RPM), you'llneed to submit the drivers to Microsoft along with a set of testresults (so called WHQL process). If you decide to WHQL the drivers,make sure to base them on commit eb2996de or newer, since the GPLlicense used prior to this commit is not compatible with WHQL.Additionally, we ask that you make a change to the Hardware IDs sothat your drivers will not match devices exposed by the upstreamversions of KVM/QEMU. This is especially important if you plan todistribute the drivers with Windows Update, see theMicrosoft publishing restrictions for more details.