From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MlWo7-0004QG-3r for qemu-devel@nongnu.org; Wed, 09 Sep 2009 19:42:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlWo2-0004Pi-4G for qemu-devel@nongnu.org; Wed, 09 Sep 2009 19:42:34 -0400 Received: from [199.232.76.173] (port=50763 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlWo1-0004Pf-Va for qemu-devel@nongnu.org; Wed, 09 Sep 2009 19:42:30 -0400 Received: from mail-ew0-f221.google.com ([209.85.219.221]:33622) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MlWo1-0005kj-FZ for qemu-devel@nongnu.org; Wed, 09 Sep 2009 19:42:29 -0400 Received: by ewy21 with SMTP id 21so870403ewy.8 for ; Wed, 09 Sep 2009 16:42:28 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <4AA83D63.1070101@gnu.org> Date: Thu, 10 Sep 2009 01:42:27 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <20090909232654.GA20719@shareable.org> In-Reply-To: <20090909232654.GA20719@shareable.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: More qcow2 bugs? - qemu-img convert/commit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: qemu-devel@nongnu.org > 37% is large enough to be a clue: Does it simply expand the qcow2 file > without reading the backing file at all? A quick strace shows that > indeed, it does *open* the backing file and it does read the backing > file's header, but after that it doesn't read it at all. > > Did I miss something obvious which means this is ok? > > Should the output of "qemu-img convert" be identical to the backing > file after "qemu-img commit", assuming they are the same format? I would have thought so. Paolo