All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Straub <lukasstraub2@web.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	qemu-block <qemu-block@nongnu.org>,
	"Juan Quintela" <quintela@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Max Reitz" <mreitz@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [PATCH v2 0/4] Introduce 'yank' oob qmp command to recover from hanging qemu
Date: Wed, 20 May 2020 23:05:27 +0200	[thread overview]
Message-ID: <cover.1590008051.git.lukasstraub2@web.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

Hello Everyone,
In many cases, if qemu has a network connection (qmp, migration, chardev, etc.)
to some other server and that server dies or hangs, qemu hangs too.
These patches introduce the new 'yank' out-of-band qmp command to recover from
these kinds of hangs. The different subsystems register callbacks which get
executed with the yank command. For example the callback can shutdown() a
socket. This is intended for the colo use-case, but it can be used for other
things too of course.

Regards,
Lukas Straub

v2:
 -don't touch io/ code anymore
 -always register yank functions
 -'yank' now takes a list of instances to yank
 -'query-yank' returns a list of yankable instances

Lukas Straub (4):
  Introduce yank feature
  block/nbd.c: Add yank feature
  chardev/char-socket.c: Add yank feature
  migration: Add yank feature

 Makefile.objs                 |   1 +
 block/nbd.c                   | 101 ++++++++++++--------
 chardev/char-socket.c         |  24 +++++
 migration/migration.c         |   9 ++
 migration/qemu-file-channel.c |   6 ++
 migration/socket.c            |  11 +++
 qapi/misc.json                |  45 +++++++++
 softmmu/vl.c                  |   2 +
 yank.c                        | 174 ++++++++++++++++++++++++++++++++++
 yank.h                        |  69 ++++++++++++++
 10 files changed, 405 insertions(+), 37 deletions(-)
 create mode 100644 yank.c
 create mode 100644 yank.h

--
2.20.1

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2020-05-20 21:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 21:05 Lukas Straub [this message]
2020-05-20 21:05 ` [PATCH v2 1/4] Introduce yank feature Lukas Straub
2020-05-20 22:48   ` Paolo Bonzini
2020-05-21 15:03   ` Stefan Hajnoczi
2020-05-21 15:42     ` Lukas Straub
2020-05-21 15:48       ` Daniel P. Berrangé
2020-06-17 14:39         ` Stefan Hajnoczi
2020-06-19 16:26           ` Lukas Straub
2020-05-20 21:05 ` [PATCH v2 2/4] block/nbd.c: Add " Lukas Straub
2020-05-20 21:05 ` [PATCH v2 3/4] chardev/char-socket.c: " Lukas Straub
2020-05-20 21:05 ` [PATCH v2 4/4] migration: " Lukas Straub
2020-05-21 15:44   ` Lukas Straub
2020-05-20 23:15 ` [PATCH v2 0/4] Introduce 'yank' oob qmp command to recover from hanging qemu no-reply
2020-05-20 23:21 ` no-reply

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=cover.1590008051.git.lukasstraub2@web.de \
    --to=lukasstraub2@web.de \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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.