Vadim Rozenfeld

@marioroy I will try to add more resolutions/memory allocation support in the next release.

In my understanding a proper 9p fs solution for Windows should come in two pieces - some sort of bus driver (virtio device) and a network file system driver (so-called...

virtio-fs is not a part of build 185. It was initially included in build 186. I will try to build a new RPM and make it public soon, hopefully by...

@milsav92 Thanks a lot for reporting this issue. Can you please post the qemu command line along with qemu version? Hopefully this this information will help us to reproduce the...

I will ask QE to reproduce and analyse this issue. Thanks, Vadim.

@milsav92 Thaks a lot for your update. Our QE should be testing exactly the same platforms - Win10 21H1/Win11 and WS2022 right now. Honestly, I don't think that this is...

@milsav92 The work is still in progress. There is a bug in RH bugzilla for tracing this issue https://bugzilla.redhat.com/show_bug.cgi?id=2020998 Sorry for the inconvenience. Vadim.

I've just pushed the viostor related fix https://github.com/virtio-win/kvm-guest-drivers-windows/pull/824 In both case (viostor and vioscsi) setting discard_granularity to 16/32M (Hyper-V uses 32M) makes Windows to work with large slabs (clusters) which...

@savchenko Can you please give a try to virtio-scsi to see if it has the same problem? Thanks, Vadim.

@savchenko Can you dump the qemu command line with "ps -aux" command for both virtio and scsi cases? Can you also confirm that 215 works fine for virtio (viostor.sys) case?...