signed WOA (arm64) drivers for future windows

[fcicq]

virtio-win.spec pointed me to this repo.
I see there is no arm64 mentioned in virtio-win-pre-installable-drivers-win-10.xml

is it too late to catch the final train before 2021 or other deadline?
(context: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/deprecation-of-software-publisher-certificates-and-commercial-release-certificates )

[vrozenfe]

If you are asking about arm64 virtio-win drivers in general, than they are already included into virtio-win package. For example, for build 190, available at https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.190-1/ , arm64 viostor driver can be found under xxxxxxxx/virtio-win-0.1.190/viostor/w10/ARM64 path.

Hopefully, we might be able to contribute Win10 virtio-win drivers to community even after Feb 22, 2021.

Best,
Vadim.

[fcicq]

I see the current Win10 Insider ARM64 vhdx, the new signing rule is already enforced? so it will only work in testsigning mode. similar with https://bugzilla.redhat.com/show_bug.cgi?id=1844726

I understand that WHQL signed drivers can be acquired by RHEL subscribers, but I think there is currently none for ARM64?

from 1844726, the deadline seems to be Jan 25 23:59:59 2022 GMT. and MS page is July 1 2021 and you say Feb 22, 2021 (a little confused... explanation is not needed though)

[vrozenfe]

IIRC, Microsoft said that properly cross-signed and time stamped drivers will continue working after cross-signing deprecation date.
After Feb 2021 attestation signed drivers can be another option to the public customers interested in Win10 drivers,
And you are right, currently we don't WHQL ARM64 drivers.

[iwikus]

Any news on this after 3 years? Does binary of guest agent exists for arm64?

[YanVugenfirer]

@iwikus There is no guest agent for the ARM64 platform.
The ARM64 drivers are attestation signed by MS.