From: Ulrich Hecht <uli@suse.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qcow1 compression
Date: Wed, 7 Jan 2009 18:24:39 +0100 [thread overview]
Message-ID: <200901071824.40113.uli@suse.de> (raw)
Hi!
I have received a bug report from one of our users about compression in
qcow(1). He converted disk images to qcow with compression, and the
resulting images did not work. I looked into block-qcow.c and found
several huge and, as it seems, long-standing bugs. For instance,
QCOW_OFLAG_COMPRESSED is never set anywhere, causing compressed data to
be returned verbatim on reading.
I'd like to get people's opinion on whether there is any point in fixing
this stuff, considering that there is qcow2, and that it never worked to
begin with. Perhaps a patch removing it would make more sense...
CU
Uli
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
next reply other threads:[~2009-01-07 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 17:24 Ulrich Hecht [this message]
2009-01-07 17:56 ` [Qemu-devel] qcow1 compression Kevin Wolf
2009-01-08 12:15 ` Ulrich Hecht
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=200901071824.40113.uli@suse.de \
--to=uli@suse.de \
--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).