https://github.com/virtio-win/kvm-guest-drivers-windows

Windows paravirtualized drivers for QEMU\KVM
https://github.com/virtio-win/kvm-guest-drivers-windows

c c-plus-plus drivers guest guest-agent kernel-driver kvm kvm-hypervisor ndis qemu qemu-kvm storport virtio virtio-win virtualization wdf wdm windows windows-driver windows-driver-kit

Last synced: 27 days ago
JSON representation

Windows paravirtualized drivers for QEMU\KVM

• Host: GitHub
• URL: https://github.com/virtio-win/kvm-guest-drivers-windows
• Owner: virtio-win
• License: bsd-3-clause
• Created: 2011-10-06T09:06:41.000Z (about 13 years ago)
• Default Branch: master
• Last Pushed: 2024-09-29T11:41:27.000Z (about 1 month ago)
• Last Synced: 2024-10-02T02:08:36.437Z (about 1 month ago)
• Topics: c, c-plus-plus, drivers, guest, guest-agent, kernel-driver, kvm, kvm-hypervisor, ndis, qemu, qemu-kvm, storport, virtio, virtio-win, virtualization, wdf, wdm, windows, windows-driver, windows-driver-kit
• Language: C
• Homepage: https://www.linux-kvm.org/page/WindowsGuestDrivers
• Size: 9.94 MB
• Stars: 2,004
• Watchers: 107
• Forks: 385
• Open Issues: 118
• Metadata Files:
  • Readme: README.md
  • Contributing: contributing.md
  • License: LICENSE
  • Codeowners: .github/CODEOWNERS

Awesome Lists containing this project

README

        
# 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. If all you want is use virtio-win in your Windows

virtual machines, go to the

[Fedora virtIO-win documentation][fedora-virtio]

for information on obtaining the binaries.

If you'd like to build virtio-win from sources, clone this repo and

follow the instructions in [Building the Drivers][wiki-building].

Note that the drivers you build will be either unsigned or test-signed

with Tools/VirtIOTestCert.cer, which means that Windows will not load

them by default. See [Microsoft's driver signing page][ms-signing]

for more information on test-signing.

If you want to build cross-signed binaries (like the ones that ship in

the Fedora RPM), you'll need your own code-signing certificate.

Cross-signed drivers can be used on all versions of Windows except for

the latest Windows 10 with secure boot enabled. However, systems with

cross-signed drivers will not receive Microsoft support.

If you want to produce Microsoft-signed binaries (fully supported,

like the ones that ship in the Red Hat Enterprise Linux RPM), you'll

need to submit the drivers to Microsoft along with a set of test

results (so called WHQL process). If you decide to WHQL the drivers,

make sure to base them on commit eb2996de or newer, since the GPL

license used prior to this commit is not compatible with WHQL.

Additionally, we ask that you make a change to the Hardware IDs so

that your drivers will *not* match devices exposed by the upstream

versions of KVM/QEMU. This is especially important if you plan to

distribute the drivers with Windows Update, see the 

[Microsoft publishing restrictions][ms-publishing] for more details.

[fedora-virtio]:https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/index.html

[wiki-building]:https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/Building-the-drivers-using-Windows-11-21H2-EWDK

[ms-signing]:https://docs.microsoft.com/en-us/windows-hardware/drivers/install/installing-test-signed-driver-packages

[ms-publishing]:https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/publishing-restrictions

- - - -