4 ms·

While the driver can be licensed under GPLv2 (all kernel drivers needs to be signed by Microsoft*, and VirtIO is a precedent¤ that you can do it), I'm not sure

While the driver can be licensed under GPLv2 (all kernel drivers needs to be signed by Microsoft*, and VirtIO is a precedent¤ that you can do it), I'm not sure if the header should be licensed under GPLv2, mainly because it would stifle Wireguard adoption. * In ordinary conditions. Test-sign mode does exist. ¤ ... for example, these Red Hat versions: https://www.catalog.update.microsoft.com/Search.aspx?q=Red%20Hat https://www.catalog.update.microsoft.com/Search.aspx?q=Red%2...

vetinari 5y ago
You can get them here: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/ https://fedorapeople.org/groups/virt/virtio-win/direct-downl... packaged in a nice iso, ready to use for iso store of your hypervisor. (It might be also slightly newer; v204 is 100.85.104.20400).
Denvercoder9 5y ago
The header is dual-licensed under GPLv2 and MIT.
shawnz 5y ago
VirtIO changed license from GPL to BSD so that it could be signed by Microsoft. See here: https://github.com/virtio-win/kvm-guest-drivers-windows/commit/d9da33e851c15e23dce8e926d7652dcb7b357e16 https://github.com/virtio-win/kvm-guest-drivers-windows/comm...