Vadim Rozenfeld

@Toetje585 That one was for x64 platforms only. But a new stable virtio-win package with the latest ARM64 drivers will be released soon. Vadim.

My bad. Drivers in Win11 folder are actually Win11 arm64. Just messed up with attestation signing submission. Thank you spotting it out. Vadim.

@melfacion @thinkingcap build 229 is completely up to date. If you didn't adjust "IoTimoutValue" https://learn.microsoft.com/en-us/windows-hardware/drivers/storage/registry-entries-for-storport-miniport-drivers - please do it, trying to increase it gradually (60/12/180) and checking if it makes...

Since it is SQL server it might be useful to try reducing the maximum transfer size by specifying "PhysicalBreaks" key in the Registry https://access.redhat.com/solutions/6963779 This key works for virtio-scsi device...

@thinkingcap No problem. There is some open information in the driver code itself https://github.com/virtio-win/kvm-guest-drivers-windows/blob/master/vioscsi/vioscsi.c#L485 "PhysicalBreaks" Registry Key allows to redefine the maximum transfer size supported by vioscsi mini-port driver. Without...

@thinkingcap System disk requires reboot, for data disk disable/enable cycle is enough.

@MaxXor I would try to reduce the transfer size ("PhysicalBreaks") first to see if it helps to solve the problem. Btw, there is a different option to adjust the transfer...

Hi @life777eternal , It is always a good decision to update the drivers with the latest ones, when it is possible. Just please note that we discontinued building Win8/8.1 and...

Sure, we are going to start adding arm64 drivers to the installer in one of the next releases. There is a RH Jira ticket opened for tracing this issue https://issues.redhat.com/browse/RHEL-15469

@AlexMKX Thank you for reporting this issue. Can you please post the qemu command line and if possible to share the crash dump file? Thanks, Vadim.