From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mlik9-0008SA-NW for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:27:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mlik3-0008Ot-21 for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:27:16 -0400 Received: from [199.232.76.173] (port=35749 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mlik2-0008Oe-4T for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:27:10 -0400 Received: from mx20.gnu.org ([199.232.41.8]:20784) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mlik1-0006Og-Bt for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:27:09 -0400 Received: from mail2.shareable.org ([80.68.89.115]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mlik0-0002WZ-Eb for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:27:08 -0400 Date: Thu, 10 Sep 2009 13:27:01 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] More qcow2 bugs? - qemu-img convert/commit Message-ID: <20090910122701.GA32178@shareable.org> References: <20090909232654.GA20719@shareable.org> <4AA8B865.8000809@redhat.com> <4AA8B9B3.9040002@redhat.com> <20090910094413.GA31632@shareable.org> <4AA8CAED.2050409@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AA8CAED.2050409@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: qemu-devel@nongnu.org Kevin Wolf wrote: > Am 10.09.2009 11:44, schrieb Jamie Lokier: > > Kevin Wolf wrote: > >> Actually, first of all, which qemu version are you using? > > > >>> The tool I used is qemu-img from kvm-88, which is the most recent > >>> release on kvm's home page. > > > > Dated 12 July 2009. > > Sorry, seems I missed the kvm-88 part. The date of the fix I mentioned > is 19 July 2009, so I assume your problem is already fixed with current > git master. It looks like the right fix, and a simple mistake caused the bug. Thanks, -- Jamie