From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] qcow2 corruption - seems to be fixed in kvm-85 and later :-)
Date: Sun, 9 Aug 2009 10:19:43 +0100 [thread overview]
Message-ID: <20090809091943.GA32524@shareable.org> (raw)
Hi,
Sometimes it's nice to find a mail with good news.
A while back I reported corruption with qcow2, with the subject
"qcow2 corruption observed, fixed by reverting old change".
I'd noticed that kvm-83 was corrupting a Windows 2k disk image, which
was failing to boot, blue screening quite early.
I found there was a qcow2 bug introduced from kvm-72 to kvm-73, and
another from kvm-76 to kvm-77. Reverting both fixed this symptom.
In order to check the bug later, I kept a copy of the disk image which
blue screened.
It still crashes with kvm-84. The release notes indicate there were
some qcow2 fixes in that version; they were not enough to fix this
problem.
There were more qcow2 fixes in kvm-85.
Happily, I can now report that kvm-85 and kvm-88 both boot this image
with no apparent problems, and I will be deleting this junk disk image
now that I'm confident no further testing is required :-)
Thanks!
-- Jamie
reply other threads:[~2009-08-09 9:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090809091943.GA32524@shareable.org \
--to=jamie@shareable.org \
--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).