qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 3/3] iotests: Test external snapshot with VM state
Date: Thu, 19 Dec 2019 15:26:31 +0100	[thread overview]
Message-ID: <e4212782-78ef-6bc9-f0e4-9a069c47a77b@redhat.com> (raw)
In-Reply-To: <20191217145939.5537-4-kwolf@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1837 bytes --]

On 17.12.19 15:59, Kevin Wolf wrote:
> This tests creating an external snapshot with VM state (which results in
> an active overlay over an inactive backing file, which is also the root
> node of an inactive BlockBackend), re-activating the images and
> performing some operations to test that the re-activation worked as
> intended.
> 
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  tests/qemu-iotests/280     | 83 ++++++++++++++++++++++++++++++++++++++
>  tests/qemu-iotests/280.out | 50 +++++++++++++++++++++++
>  tests/qemu-iotests/group   |  1 +
>  3 files changed, 134 insertions(+)
>  create mode 100755 tests/qemu-iotests/280
>  create mode 100644 tests/qemu-iotests/280.out

[...]

> diff --git a/tests/qemu-iotests/280.out b/tests/qemu-iotests/280.out
> new file mode 100644
> index 0000000000..5d382faaa8
> --- /dev/null
> +++ b/tests/qemu-iotests/280.out
> @@ -0,0 +1,50 @@
> +Formatting 'TEST_DIR/PID-base', fmt=qcow2 size=67108864 cluster_size=65536 lazy_refcounts=off refcount_bits=16
> +
> +=== Launch VM ===
> +Enabling migration QMP events on VM...
> +{"return": {}}
> +
> +=== Migrate to file ===
> +{"execute": "migrate", "arguments": {"uri": "exec:cat > /dev/null"}}
> +{"return": {}}
> +{"data": {"status": "setup"}, "event": "MIGRATION", "timestamp": {"microseconds": "USECS", "seconds": "SECS"}}
> +{"data": {"status": "active"}, "event": "MIGRATION", "timestamp": {"microseconds": "USECS", "seconds": "SECS"}}
> +{"data": {"status": "completed"}, "event": "MIGRATION", "timestamp": {"microseconds": "USECS", "seconds": "SECS"}}
> +
> +VM is now stopped:
> +completed
> +{"execute": "query-status", "arguments": {}}
> +{"return": {"running": false, "singlestep": false, "status": "postmigrate"}}

Hmmm, I get a finish-migrate status here (on tmpfs)...

Max


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

  reply	other threads:[~2019-12-19 14:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 14:59 [PATCH 0/3] block: Fix external snapshot with VM state Kevin Wolf
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 [this message]
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=e4212782-78ef-6bc9-f0e4-9a069c47a77b@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@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).