<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Thank you Sergio. Is there a patch I could use to make it work with an older version?</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Thanks</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Prashant</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div>
<div><br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0);">
<br>
<hr tabindex="-1" style="display:inline-block; width:98%;">
<b>From:</b> Sergio Lopez<br>
<b>Sent:</b> Tuesday, May 31, 2022 10:50 AM<br>
<b>To:</b> Pra.. Dew..<br>
<b>Cc:</b> Stefan Hajnoczi; virtio-fs@redhat.com; gmaglione@redhat.com; Vivek Goyal<br>
<b>Subject:</b> Re: [Virtio-fs] vhost_set_vring_kick failed
<div><br>
</div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On Thu, May 26, 2022 at 04:07:36PM +0000, Pra.. Dew.. wrote:<br>
> Thanks for the response. The version of the qemu is 5.1.0 and here is the comandline..<br>
> <br>
> <br>
> [/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]<br>
<br>
Thanks for the details. I knew that we didn't support older versions,<br>
but didn't want to reply that without explaining why.<br>
<br>
I've just took a look, and the origin of this incompatibility is this<br>
change in "hw/virtio/vhost-user.c":<br>
<br>
qemu-5.1.0:<br>
<br>
typedef struct VhostUserMemRegMsg {<br>
uint32_t padding;<br>
VhostUserMemoryRegion region;<br>
} VhostUserMemRegMsg;<br>
<br>
qemu-upstream (since 3009edff8192991293fe9e2b50b0d90db83c4a89):<br>
<br>
typedef struct VhostUserMemRegMsg {<br>
uint64_t padding;<br>
VhostUserMemoryRegion region;<br>
} VhostUserMemRegMsg;<br>
<br>
Note how "padding" has changed from uint32_t to uint64_t.<br>
<br>
This means we only support QEMU versions starting 5.2.0.<br>
<br>
Regards,<br>
Sergio.<br>
</div>
</span></font></div>
</div>
</body>
</html>