From: Xingbo Wu <wuxb45@gmail.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] disk image: self-organized format or raw file
Date: Tue, 12 Aug 2014 15:23:38 -0400 [thread overview]
Message-ID: <CABPa+v0SjGFJBt3ZD-9-VyPPCy5QWNPwFBa+DGrsAxS3D7wXPA@mail.gmail.com> (raw)
In-Reply-To: <20140812185207.GH14001@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
On Tue, Aug 12, 2014 at 2:52 PM, Richard W.M. Jones <rjones@redhat.com>
wrote:
> On Tue, Aug 12, 2014 at 07:46:30PM +0100, Daniel P. Berrange wrote:
> > Taking the compression feature - arguably the biggest benefit of that
> > is when you distribute disk images. eg if someone provides a root disk
> > image on a web server, using compression in qcow2 can dramatically
> > lower the download size, while still allowing QEMU to directly run
> > from that qcow2 file. Sure you could wrap your disk images in gzip
> > and then convert to your local filesystem at time of use but this
> > introduces multiple extra steps.
>
> It would be nice if qemu could handle xz-compressed files
> transparently, since (when prepared correctly) these files are
> seekable.
>
> I have written code to do this here:
>
> https://github.com/libguestfs/nbdkit/tree/master/plugins/xz
>
> I believe it's ideal for read-only backing file, the xz-compressed image
would be very space efficient for distribution :).
Would you consider replace xz with lz4? it has faster decompression speed
(~500MB/s)[1] and client-side decompression would be made painless.
[1]
http://linuxaria.com/article/linux-compressors-comparison-on-centos-6-5-x86-64-lzo-vs-lz4-vs-gzip-vs-bzip2-vs-lzma
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> libguestfs lets you edit virtual machines. Supports shell scripting,
> bindings from many languages. http://libguestfs.org
>
--
Cheers!
吴兴博 Wu, Xingbo <wuxb45@gmail.com>
[-- Attachment #2: Type: text/html, Size: 2898 bytes --]
next prev parent reply other threads:[~2014-08-12 19:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 23:38 [Qemu-devel] disk image: self-organized format or raw file 吴兴博
2014-08-12 0:52 ` Fam Zheng
2014-08-12 10:46 ` 吴兴博
2014-08-12 11:19 ` Fam Zheng
[not found] ` <CABPa+v1a7meoEtjLkwygjuZEABTqd8q3efGWJvAsAr-mLTQb-A@mail.gmail.com>
[not found] ` <20140812113916.GB2803@T430.redhat.com>
2014-08-12 12:03 ` 吴兴博
2014-08-12 12:21 ` Fam Zheng
2014-08-12 13:08 ` Kirill Batuzov
2014-08-12 13:23 ` Eric Blake
2014-08-12 13:45 ` 吴兴博
2014-08-12 14:07 ` Eric Blake
2014-08-12 14:14 ` 吴兴博
2014-08-12 15:30 ` Eric Blake
2014-08-12 16:22 ` Xingbo Wu
2014-08-13 1:29 ` Fam Zheng
2014-08-13 15:42 ` Kevin Wolf
2014-08-12 18:39 ` Richard W.M. Jones
2014-08-12 18:46 ` Daniel P. Berrange
2014-08-12 18:52 ` Richard W.M. Jones
2014-08-12 19:23 ` Xingbo Wu [this message]
2014-08-12 20:14 ` Richard W.M. Jones
2014-08-13 15:54 ` Kevin Wolf
2014-08-13 16:38 ` Xingbo Wu
2014-08-13 18:32 ` Kevin Wolf
2014-08-13 21:04 ` Xingbo Wu
2014-08-13 21:35 ` Eric Blake
2014-08-14 2:42 ` Xingbo Wu
2014-08-14 9:06 ` Kevin Wolf
2014-08-14 20:53 ` Xingbo Wu
2014-08-15 10:46 ` 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=CABPa+v0SjGFJBt3ZD-9-VyPPCy5QWNPwFBa+DGrsAxS3D7wXPA@mail.gmail.com \
--to=wuxb45@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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 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).