Hi Michael, while testing the following kernel patches I realized there is currently a size limitation of 4 MB with virtio on QEMU side: https://lore.kernel.org/netdev/cover.1632327421.git.linux_...@crudebyte.com/
So with those kernel patches applied I can mount 9pfs on Linux guest with the 9p 'msize' (maximum message size) option with a value of up to 4186112 successfully. If I try to go higher with 'msize' then the system would hang with the following QEMU error: qemu-system-x86_64: virtio: too many write descriptors in indirect table Which apparently is due to the amount of scatter gather lists on QEMU virtio side currently being hard coded to 1024 (i.e. multiplied by 4k page size => 4 MB): ./include/hw/virtio/virtio.h: #define VIRTQUEUE_MAX_SIZE 1024 Is that hard coded limit carved into stone for some reason or would it be OK if I change that into a runtime variable? If that would be Ok, maybe something similar that I did with those kernel patches, i.e. retaining 1024 as an initial default value and if indicated from guest side that more is needed, increasing the SG list amount subsequently according to whatever is needed by guest? And as I am not too familiar with the virtio protocol, is that current limit already visible to guest side? Because obviously it would make sense if I change my kernel patches so that they automatically limit to whatever QEMU supports instead of causing a hang. Best regards, Christian Schoenebeck
