From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, fam@euphon.net, den@virtuozzo.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2 2/2] iotests: test external snapshot with bitmap copying
Date: Wed, 5 Jun 2019 16:51:45 +0200 [thread overview]
Message-ID: <235f1fe9-d878-7afd-ccf4-2b4f899a93b3@redhat.com> (raw)
In-Reply-To: <20190517152111.206494-3-vsementsov@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
On 17.05.19 17:21, Vladimir Sementsov-Ogievskiy wrote:
> This test shows that external snapshots and incremental backups are
> friends.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> tests/qemu-iotests/254 | 52 ++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/254.out | 52 ++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/group | 1 +
> 3 files changed, 105 insertions(+)
> create mode 100755 tests/qemu-iotests/254
> create mode 100644 tests/qemu-iotests/254.out
This test fails for me with qcow (v1).
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-05 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 15:21 [Qemu-devel] [PATCH v2 0/2] bitmaps: merge bitmaps from different nodes Vladimir Sementsov-Ogievskiy
2019-05-17 15:21 ` [Qemu-devel] [PATCH v2 1/2] qapi: support external bitmaps in block-dirty-bitmap-merge Vladimir Sementsov-Ogievskiy
2019-05-17 22:45 ` John Snow
2019-05-20 15:23 ` Eric Blake
2019-05-17 15:21 ` [Qemu-devel] [PATCH v2 2/2] iotests: test external snapshot with bitmap copying Vladimir Sementsov-Ogievskiy
2019-05-18 1:31 ` John Snow
2019-05-20 7:47 ` Vladimir Sementsov-Ogievskiy
2019-05-20 22:50 ` John Snow
2019-06-05 14:51 ` Max Reitz [this message]
2019-06-05 15:08 ` [Qemu-devel] [Qemu-block] " Vladimir Sementsov-Ogievskiy
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=235f1fe9-d878-7afd-ccf4-2b4f899a93b3@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=den@virtuozzo.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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 NNTP newsgroup(s).