From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com
Subject: [PATCH 0/3] block: Fix external snapshot with VM state
Date: Tue, 17 Dec 2019 15:59:36 +0100 [thread overview]
Message-ID: <20191217145939.5537-1-kwolf@redhat.com> (raw)
This fixes bdrv_invalidate_cache_all() for some kinds of graphs where
part of the nodes are active and others are inactive. This is a scenario
that happens when libvirt takes an external snapshot with VM state.
This was reported in:
https://bugzilla.redhat.com/show_bug.cgi?id=1781637
('qemu crashed when do mem and disk snapshot')
Based-on: <20191216170857.11880-1-kwolf@redhat.com>
('iotests: Remove duplicated blockdev_create()')
Kevin Wolf (3):
block: Activate recursively even for already active nodes
hmp: Allow using qdev ID for qemu-io command
iotests: Test external snapshot with VM state
block.c | 50 +++++++++++------------
monitor/hmp-cmds.c | 28 ++++++++-----
hmp-commands.hx | 8 ++--
tests/qemu-iotests/280 | 83 ++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/280.out | 50 +++++++++++++++++++++++
tests/qemu-iotests/group | 1 +
6 files changed, 181 insertions(+), 39 deletions(-)
create mode 100755 tests/qemu-iotests/280
create mode 100644 tests/qemu-iotests/280.out
--
2.20.1
next reply other threads:[~2019-12-17 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 14:59 Kevin Wolf [this message]
2019-12-17 14:59 ` [PATCH 1/3] block: Activate recursively even for already active nodes Kevin Wolf
2019-12-18 17:02 ` Kevin Wolf
2019-12-19 12:46 ` Max Reitz
2019-12-17 14:59 ` [PATCH 2/3] hmp: Allow using qdev ID for qemu-io command Kevin Wolf
2019-12-17 14:59 ` [PATCH 3/3] iotests: Test external snapshot with VM state Kevin Wolf
2019-12-19 14:26 ` Max Reitz
2019-12-19 15:47 ` Kevin Wolf
2020-01-02 13:25 ` Dr. David Alan Gilbert
2020-01-06 16:06 ` Kevin Wolf
2020-02-10 12:31 ` Dr. David Alan Gilbert
2020-02-10 13:37 ` Kevin Wolf
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=20191217145939.5537-1-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).