From: Csaba Henk <csaba-ml@creo.hu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: qcow2 images going corrupt
Date: Wed, 9 May 2007 12:47:24 +0000 (UTC) [thread overview]
Message-ID: <slrnf43gmr.td.csaba-ml@beastie.creo.hu> (raw)
In-Reply-To: 20070508191656.GA13638@networkno.de
On 2007-05-08, Thiemo Seufer <ths@networkno.de> wrote:
> There was a bug in the qcow2 support which is fixed in CVS. You can use
> qcow instead, or upgrade to a recent-ish CVS version of qemu.
Oh yeah, thanks, I see. I really could as well have looked it up
myself...
What I *don't* understand is that why has not the Qemu team made a
bugfix release immediately? This is a _serious bug_. It can cause data
loss. As it did for me.
Csaba
next prev parent reply other threads:[~2007-05-09 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 16:15 [Qemu-devel] qcow2 images going corrupt Csaba Henk
2007-05-08 19:16 ` Thiemo Seufer
2007-05-09 12:47 ` Csaba Henk [this message]
[not found] ` <8B924B0C-001F-11DC-B4CF-0005025B95B5@hotmail.com>
2007-05-12 0:27 ` [Qemu-devel] " C.W. Betts
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=slrnf43gmr.td.csaba-ml@beastie.creo.hu \
--to=csaba-ml@creo.hu \
--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).