virtio-fs.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: virtiofs-bot@sinrega.org
To: virtio-fs@redhat.com
Subject: [Virtio-fs] [virtiofsd] Issue opened: Allow for reconnection after the client disconnects
Date: Tue, 11 Oct 2022 12:58:32 +0000 (UTC)	[thread overview]
Message-ID: <14027.122101108582901062@us-mta-435.us.mimecast.lan> (raw)

It'd be nice to give the user the possibility to choose if virtiofsd should retry to listen on the same socket after the connection from the client side has been closed.
In practice, there are a few use case where this can be useful, like VM reboot or a potential VM migration (on the same host). When these use cases are triggered, the VM might close the connection with the vhost-user backend, leading to the termination of the virtiofsd process.
Adding a CLI option `--keep-listening` to virtiofsd would give the user a way to choose if the virtiofsd process should terminate or keep listening after the client (the VMM) disconnected.
---
https://gitlab.com/virtio-fs/virtiofsd/-/issues/62


                 reply	other threads:[~2022-10-11 12:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=14027.122101108582901062@us-mta-435.us.mimecast.lan \
    --to=virtiofs-bot@sinrega.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).