All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Sergio Lopez <slp@redhat.com>,
	Prashant Dewan <linux_learner@outlook.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	"virtio-fs@redhat.com" <virtio-fs@redhat.com>
Subject: Re: [Virtio-fs] vhost_set_vring_kick failed
Date: Mon, 30 May 2022 18:11:54 -0400	[thread overview]
Message-ID: <YpVBKsogLU8/5kiV@redhat.com> (raw)
In-Reply-To: <20220526080646.vsfmqgxyiglhe64r@mhamilton>

On Thu, May 26, 2022 at 10:06:46AM +0200, Sergio Lopez wrote:
> On Thu, May 26, 2022 at 08:49:34AM +0100, Stefan Hajnoczi wrote:
> > 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)

So looks like following gave error message. There is no error messsage
from the actual thread which failed. This is just the main thread
waiting.

    if let Err(e) = daemon.wait() {
        match e {
            HandleRequest(PartialMessage) => info!("Client disconnected, shutting down"),
            _ => error!("Waiting for daemon failed: {:?}", e),
        }
    }

I can't find "InvalidParam" in rust virtiofsd code. Does that mean,
that this error is being returned by one of the crates we are using.

Prashant, you could try running rust virtiofsd with option "-d" to enable
debug messages and that might show something interesting.

Also, if you are able to reproduce the problem all the time, I think
you can start virtiofsd under gdb and see where exactly is it failing.

Thanks
Vivek

> > 
> > virtiofsd terminated. I have CCed Sergio and German, who may have
> > suggestions about what to check next.
> 
> Hi,
> 
> Could you please tell us which QEMU version are you running, and paste
> here the its command line?
> 
> Thanks,
> Sergio.



> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://listman.redhat.com/mailman/listinfo/virtio-fs


  reply	other threads:[~2022-05-30 22:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  5:34 [Virtio-fs] vhost_set_vring_kick failed Prashant Dewan
2022-05-26  7:49 ` Stefan Hajnoczi
2022-05-26  8:06   ` Sergio Lopez
2022-05-30 22:11     ` Vivek Goyal [this message]
2022-05-31 22:25       ` Pra.. Dew..
2022-05-31 22:50         ` Vivek Goyal
2022-06-01  6:01         ` Sergio Lopez
  -- strict thread matches above, loose matches on Subject: below --
2022-06-01 19:12 Pra.. Dew..
2022-05-31 18:33 Pra.. Dew..
2022-05-26 16:07 Pra.. Dew..
2022-05-31 10:50 ` Sergio Lopez
2022-05-24 14:29 Prashant Dewan
2022-05-25 16:02 ` Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YpVBKsogLU8/5kiV@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=linux_learner@outlook.com \
    --cc=slp@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-fs@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.