From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qemu-iotests: add qed.py image manipulation utility
Date: Thu, 26 Jul 2012 06:33:17 -0600 [thread overview]
Message-ID: <5011390D.1010605@redhat.com> (raw)
In-Reply-To: <1343286523-8212-1-git-send-email-stefanha@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On 07/26/2012 01:08 AM, Stefan Hajnoczi wrote:
> The qed.py utility can inspect and manipulate QED image files. It can
> be used for testing to see the state of image metadata and also to
> inject corruptions into the image file. It also has a scrubbing feature
> to copy just the metadata out of an image file, allowing users to share
> broken image files without revealing data in bug reports.
>
> This has lived in my local repo for a long time but could be useful
> to others. There are two use cases:
>
> 1. qemu-iotests that need to manipulate (e.g. corrupt) QED image files.
> 2. Users that want to inspect or recover their QED image files.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2. See
or later?
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
prev parent reply other threads:[~2012-07-26 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 7:08 [Qemu-devel] [PATCH v2] qemu-iotests: add qed.py image manipulation utility Stefan Hajnoczi
2012-07-26 11:34 ` Kevin Wolf
2012-07-26 12:11 ` Stefan Hajnoczi
2012-07-26 12:33 ` Eric Blake [this message]
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=5011390D.1010605@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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.