From: Jamie Lokier Subject: qcow2 corruption - seems to be fixed in kvm-85 and later :-) Date: Sun, 9 Aug 2009 10:19:43 +0100 Message-ID: <20090809091943.GA32524@shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: qemu-devel@nongnu.org, kvm@vger.kernel.org Return-path: Received: from mail2.shareable.org ([80.68.89.115]:39165 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751674AbZHIJTp (ORCPT ); Sun, 9 Aug 2009 05:19:45 -0400 Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: 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