From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LXBjj-0001WP-Th for qemu-devel@nongnu.org; Wed, 11 Feb 2009 04:50:31 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LXBji-0001Vs-7r for qemu-devel@nongnu.org; Wed, 11 Feb 2009 04:50:31 -0500 Received: from [199.232.76.173] (port=58609 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LXBji-0001Vn-4j for qemu-devel@nongnu.org; Wed, 11 Feb 2009 04:50:30 -0500 Received: from ns.suse.de ([195.135.220.2]:58941 helo=mx1.suse.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LXBjh-0002mG-Mx for qemu-devel@nongnu.org; Wed, 11 Feb 2009 04:50:29 -0500 Message-ID: <4992A108.8070304@suse.de> Date: Wed, 11 Feb 2009 10:57:28 +0100 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] qcow2 corruption observed, fixed by reverting old change References: <20090211070049.GA27821@shareable.org> In-Reply-To: <20090211070049.GA27821@shareable.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: qemu-devel@nongnu.org, kvm-devel 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