Thank you Sergio. Is there a patch I could use to make it work with an older
version?
Thanks
Prashant
________________________________
From: Sergio Lopez
Sent: Tuesday, May 31, 2022 10:50 AM
To: Pra.. Dew..
Cc: Stefan Hajnoczi; virtio-fs@redhat.com; gmagli...@redhat.com; Vivek Goyal
Subject: Re: [Virtio-fs] vhost_set_vring_kick failed
On Thu, May 26, 2022 at 04:07:36PM +0000, Pra.. Dew.. wrote:
> Thanks for the response. The version of the qemu is 5.1.0 and here is the
> comandline..
>
>
> [/usr/bin/qemu-system-test-machine test --enable-kvm -display none -mon
> mon-console,mode=readline -chardev
> socket,host=,port=5001,server,nowait,id=mon-console -device
> virtio-serial-device,max_ports=2 -device
> virtconsole,chardev=console,name=console -chardev
> socket,host=,port=5000,server,nowait,id=console -netdev
> tap,id=tap0,ifname=tap0,vhost=on,script=no,downscript=no -device
> virtio-net-device,netdev=tap0 -device vhost-vsock-device,guest-cid=4 -object
> rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0
> -chardev socket,id=char0,path=/run/vm001-vhost-fs.sock -device
> vhost-user-fs-device,queue-size=2,chardev=char0,tag=myfs -object
> memory-backend-memfd,id=mem,size=4G,share=on -kernel
> /var/lib/are/images/active/kernel.bin -dtb
> /var/lib/are/images/active/device-tree.dtb -device
> virtio-blk-device,drive=writable,serial=writable -drive
> file=/var/lib/are/volumes/writable.bin,if=none,id=writable,format=raw -device
> virtio-blk-device,drive=rootfs,serial=rootfs -drive
> file=/var/lib/are/images/active/rootfs/rootfs.bin,if=none,id=rootfs,format=raw,readonly]
Thanks for the details. I knew that we didn't support older versions,
but didn't want to reply that without explaining why.
I've just took a look, and the origin of this incompatibility is this
change in "hw/virtio/vhost-user.c":
qemu-5.1.0:
typedef struct VhostUserMemRegMsg {
uint32_t padding;
VhostUserMemoryRegion region;
} VhostUserMemRegMsg;
qemu-upstream (since 3009edff8192991293fe9e2b50b0d90db83c4a89):
typedef struct VhostUserMemRegMsg {
uint64_t padding;
VhostUserMemoryRegion region;
} VhostUserMemRegMsg;
Note how "padding" has changed from uint32_t to uint64_t.
This means we only support QEMU versions starting 5.2.0.
Regards,
Sergio.
_______________________________________________
Virtio-fs mailing list
Virtio-fs@redhat.com
https://listman.redhat.com/mailman/listinfo/virtio-fs
