On Thu, May 26, 2022 at 05:34:42AM +0000, Prashant Dewan wrote:
> Hello Stefan,
> 
> Here is the output from virtofsd..
> 
> ------------------------------------
> - Journal begins at Thu 2022-05-26 04:23:42 UTC, ends at Thu 2022-05-26 04:41:57 UTC. --
> May 26 04:24:13 localhost systemd[1]: Started virtio-fs vhost-user device daemon.<<Placeholder: run this daemon as non-privileged user>>.
> May 26 04:24:13 localhost virtiofsd[505]: [2022-05-26T04:24:13Z INFO  virtiofsd] Waiting for vhost-user socket connection...
> May 26 04:27:11 device-3e4b479e2ee9c647 virtiofsd[505]: [2022-05-26T04:27:11Z INFO  virtiofsd] Client connected, servicing requests
> May 26 04:27:33 device-3e4b479e2ee9c647 virtiofsd[505]: [2022-05-26T04:27:33Z ERROR virtiofsd] Waiting for daemon failed: HandleRequest(InvalidParam)

virtiofsd terminated. I have CCed Sergio and German, who may have
suggestions about what to check next.

Stefan

> May 26 04:27:33 device-3e4b479e2ee9c647 systemd[1]: virtiofsd.service: Deactivated successfully.
> May 26 04:27:33 device-3e4b479e2ee9c647 systemd[1]: virtiofsd.service: Scheduled restart job, restart counter is at 1.
> 
> ________________________________
> From: Stefan Hajnoczi
> Sent: Wednesday, May 25, 2022 4:02 PM
> To: Prashant Dewan
> Cc: virtio-fs@redhat.com
> Subject: Re: [Virtio-fs] vhost_set_vring_kick failed
> 
> On Tue, May 24, 2022 at 02:29:12PM +0000, Pra Dew wrote:
> > I am trying to setup virtfs using KVM and QEMU.
> >
> >
> >   1.  Inside the VM, I do
> >      *   mount -t virtiofs myfs /dev/myfile  --succeeds
> >      *   cd /dev/myfile  -hangs
> >
> >
> >   1.  The host logs -
> >
> >  qemu-system: Failed to write msg. Wrote -1 instead of 20.
> 
> Sending a vhost-user protocol message failed. It is likely that the
> virtiofsd process terminated and the UNIX domain socket closed on QEMU.
> 
> Is there any output from virtiofsd?
> 
> Stefan