From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] qemu-iotests: Test qcow2 header rewrites
Date: Tue, 3 Apr 2012 18:32:20 +0200 [thread overview]
Message-ID: <1333470742-20405-1-git-send-email-kwolf@redhat.com> (raw)
Some bugs related to rewriting the qcow2 header (as it happens e.g. during
qemu-img rebase) have been fixed recently. Here is the test case for it.
Kevin Wolf (2):
qemu-iotests: qcow2.py
qemu-iotests: Test unknown qcow2 header extensions
tests/qemu-iotests/031 | 72 +++++++++++++++
tests/qemu-iotests/031.out | 76 ++++++++++++++++
tests/qemu-iotests/group | 1 +
tests/qemu-iotests/qcow2.py | 207 +++++++++++++++++++++++++++++++++++++++++++
4 files changed, 356 insertions(+), 0 deletions(-)
create mode 100755 tests/qemu-iotests/031
create mode 100644 tests/qemu-iotests/031.out
create mode 100755 tests/qemu-iotests/qcow2.py
--
1.7.6.5
next reply other threads:[~2012-04-03 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 16:32 Kevin Wolf [this message]
2012-04-03 16:32 ` [Qemu-devel] [PATCH 1/2] qemu-iotests: qcow2.py Kevin Wolf
2012-04-03 16:32 ` [Qemu-devel] [PATCH 2/2] qemu-iotests: Test unknown qcow2 header extensions 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=1333470742-20405-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--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).