From: Jeff Cody <jcody@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] block: qemu-iotests - add basic ability to use binary sample images
Date: Fri, 20 Sep 2013 09:23:44 -0400 [thread overview]
Message-ID: <20130920132344.GM15106@localhost.localdomain> (raw)
In-Reply-To: <523C43C0.8030907@redhat.com>
On Fri, Sep 20, 2013 at 06:46:56AM -0600, Eric Blake wrote:
> On 09/19/2013 09:48 PM, Jeff Cody wrote:
> > For image formats that are not "QEMU native", but supported for
> > compatibility, it is useful to verify that an image created with
> > the 'gold standard' native tool can be read / written to successfully
> > by QEMU.
> >
> > In addition to testing non-native images, this could also be useful to
> > test against image files created by older versions of QEMU.
> >
> > This provides a directory to store small sample images, for use by
> > scripts in tests/qemu-iotests.
> >
> > The MANIFEST file should be updated when a new image is added to the
> > directory, to give some idea about the nature of the image and the
> > data store therein.
> >
> > Image files should be compressed with bzip2.
>
> Why bzip2? xz beats bzip2 in both compression ratio and decompression
> speed; or if you are worried about portability, gzip is present on more
> machines. bzip2 will probably be around for some time, but it is no
> longer the compression engine of choice.
>
iotest-dynamic-1G.vhdx compressed with gzip, xv, and bzip2:
gzip: 102548 bytes
xv: 15892 bytes
bzip2: 874 bytes
I think bzip2 is particularly well suited for image files with
hyper-repetitive consecutive bytes due to its use of RLE. I don't
know that all sample images will have data like that, but chances are
good many will - and even if they don't, bzip2 is not horrible
compared to xz even on normal data.
-Jeff
next prev parent reply other threads:[~2013-09-20 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 3:48 [Qemu-devel] [PATCH 0/2] qemu-iotests with sample images, vhdx read test Jeff Cody
2013-09-20 3:48 ` [Qemu-devel] [PATCH 1/2] block: qemu-iotests - add basic ability to use binary sample images Jeff Cody
2013-09-20 12:32 ` Stefan Hajnoczi
2013-09-20 12:41 ` Jeff Cody
2013-09-20 12:46 ` Eric Blake
2013-09-20 13:23 ` Jeff Cody [this message]
2013-09-20 3:48 ` [Qemu-devel] [PATCH 2/2] block: qemu-iotests for vhdx, read sample dynamic image Jeff Cody
2013-09-20 9:10 ` [Qemu-devel] [PATCH 2/2] block: qemu-iotests for vhdx, read sample dynamic imagee Alex Bennée
2013-09-20 9:18 ` Kevin Wolf
2013-09-20 10:54 ` Alex Bennée
2013-09-20 11:24 ` Jeff Cody
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=20130920132344.GM15106@localhost.localdomain \
--to=jcody@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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.