From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LZE3H-0004SZ-Pb
	for qemu-devel@nongnu.org; Mon, 16 Feb 2009 19:43:07 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LZE3H-0004Ra-9Q
	for qemu-devel@nongnu.org; Mon, 16 Feb 2009 19:43:07 -0500
Received: from [199.232.76.173] (port=50843 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LZE3G-0004RT-SW
	for qemu-devel@nongnu.org; Mon, 16 Feb 2009 19:43:07 -0500
Received: from mail2.shareable.org ([80.68.89.115]:57372)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1LZE3G-0001gF-E8
	for qemu-devel@nongnu.org; Mon, 16 Feb 2009 19:43:06 -0500
Date: Tue, 17 Feb 2009 00:43:04 +0000
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] qcow2 corruption observed,
	fixed by reverting old change
Message-ID: <20090217004304.GC20713@shareable.org>
References: <20090211070049.GA27821@shareable.org> <4992A108.8070304@suse.de>
	<20090211114126.GC31997@shareable.org> <4992C77D.4030104@suse.de>
	<20090211164814.GA7161@shareable.org> <49995FA4.3070508@suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49995FA4.3070508@suse.de>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@lvivier.info>, kvm-devel <kvm@vger.kernel.org>

Kevin Wolf wrote:
> >> By the way and completely off-topic: Have you already tried to use the
> >> VHD patches? I would really like to know if they fix your problems.
> > 
> > Are those patches in kvm-83?  I still have the image that was causing
> > problems way back, and I'm converting it to raw now with kvm-83 to see
> > if it now matches the raw image produced by VPC's own tool.
> 
> Avi mentioned the patches in the kvm-84 announcement yesterday, so it
> seems they are not in kvm-83.

Ok.  I did the conversion from VHD to raw with "kvm-83-img convert"
and it gave a different result to MSVPC - i.e. wrong.  I'll try it
again sometime with kvm-84.

-- Jamie