Vadim Rozenfeld

Which driver are you trying to install viostor or vioscsi ?

I don't have 185 on my testing machine at the moment, but 190 looks quite fine: [ vrozenfe@panda virtio-win-0.1.190]$ ls -la vioscsi/2k8R2/amd64/ total 761 dr-xr-xr-x 2 vrozenfe vrozenfe 2048 Mar...

@xiandaicxsj Pushed tag 'mm237" which is corresponding with build 217 https://github.com/virtio-win/kvm-guest-drivers-windows/wiki/Builds-and-tags-mapping Best, Vadim.

@m9x3mos Was it a BSOD? Can you post the bugcheck code or even better a screenshot from the failing VM. Can you post the qemu command line. Since this project...

@m9x3mos Can you please post the qemu command line? Thanks, Vadim.

@m9x3mos Thanks. Yeah, it makes sense niw Assertion failed: (n >= 2 && n

Code 52 refers to that Windows cannot verify the digital signature for the drivers required for this device. What is your Windows architecture (32/64-bit) and what is the qxl-dod driver...

The same issue as https://github.com/virtio-win/virtio-win-guest-tools-installer/issues/33 Please try disabling pvpanic, qemuserial and qemucfg. In any case the problem will be fixed in the next build. Best, Vadim.

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...

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...