From: Kevin Wolf <kwolf@redhat.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] Warn if a qcow (not qcow2) file is opened
Date: Thu, 02 Jul 2009 09:22:59 +0200 [thread overview]
Message-ID: <4A4C6053.9000200@redhat.com> (raw)
In-Reply-To: <5130D93B-F80E-4B4B-8140-F77C7178EC99@web.de>
Andreas Färber schrieb:
> I'm confused now. Only recently someone stepped up, saying that qcow2
> was broken and that qcow should be used instead for safety reasons.
> Now all of a sudden, it's the exact opposite, you're even considering
> replacing qcow with qcow2 for vvfat and dropping qcow support.
Basically, qcow1 is unmaintained. On the one hand this means that its
code is rarely changed and is quite stable in that respect, on the other
hand it means that nobody cares if it's broken e.g. by changes to the
block layer in general. There is no breakage I know of in the current
stable release, however git master has been broken for a month now.
And I'm pretty sure that qcow2 receives more testing than qcow.
Kevin
next prev parent reply other threads:[~2009-07-02 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 14:04 [Qemu-devel] [PATCH] Warn if a qcow (not qcow2) file is opened Avi Kivity
2009-06-30 8:34 ` Kevin Wolf
2009-06-30 13:32 ` Anthony Liguori
2009-06-30 13:53 ` Kevin Wolf
2009-06-30 13:57 ` Avi Kivity
2009-06-30 14:21 ` Paul Brook
2009-06-30 14:40 ` Daniel P. Berrange
2009-06-30 16:42 ` Anthony Liguori
2009-07-01 17:14 ` Andreas Färber
2009-07-02 7:22 ` Kevin Wolf [this message]
2009-06-30 12:05 ` Amit Shah
2009-06-30 12:53 ` 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=4A4C6053.9000200@redhat.com \
--to=kwolf@redhat.com \
--cc=andreas.faerber@web.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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).