From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Wolf Subject: Re: [Qemu-devel] qcow2 corruption observed, fixed by reverting old change Date: Wed, 11 Feb 2009 10:57:28 +0100 Message-ID: <4992A108.8070304@suse.de> References: <20090211070049.GA27821@shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm-devel To: Jamie Lokier Return-path: Received: from ns.suse.de ([195.135.220.2]:58939 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752567AbZBKJu2 (ORCPT ); Wed, 11 Feb 2009 04:50:28 -0500 In-Reply-To: <20090211070049.GA27821@shareable.org> Sender: kvm-owner@vger.kernel.org List-ID: Jamie Lokier schrieb: > Although there are many ways to make Windows blue screen in KVM, in > this case I've narrowed it down to the difference in > qemu/block-qcow2.c between kvm-72 and kvm-73 (not -83). This must be one of SVN revisions 5003 to 5008 in upstream qemu. Can you narrow it down to one of these? I certainly don't feel like reviewing all of them once again. Do I understand correctly that your image fails with the kvm-73 version of block-qcow2.c and afterwards boots with kvm-72? So the image is not really corrupted but it's more likely an IO error which brings the OS down? Kevin