From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HlVJy-0000LH-4V for qemu-devel@nongnu.org; Tue, 08 May 2007 15:26:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HlVJv-0000Fa-Uq for qemu-devel@nongnu.org; Tue, 08 May 2007 15:26:01 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HlVJv-0000FX-Na for qemu-devel@nongnu.org; Tue, 08 May 2007 15:25:59 -0400 Received: from phoenix.bawue.net ([193.7.176.60] helo=mail.bawue.net) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HlVCn-0003jZ-Vf for qemu-devel@nongnu.org; Tue, 08 May 2007 15:18:38 -0400 Received: from lagash (intrt.mips-uk.com [194.74.144.130]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bawue.net (Postfix) with ESMTP id F068684421 for ; Tue, 8 May 2007 21:16:01 +0200 (CEST) Received: from ths by lagash with local (Exim 4.67) (envelope-from ) id 1HlVBA-0004IC-HG for qemu-devel@nongnu.org; Tue, 08 May 2007 20:16:56 +0100 Date: Tue, 8 May 2007 20:16:56 +0100 Subject: Re: [Qemu-devel] qcow2 images going corrupt Message-ID: <20070508191656.GA13638@networkno.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: From: Thiemo Seufer Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Csaba Henk wrote: > Hi, > > I'm running qemu 0.9.0 on a Linux host. > > I'm using a qcow2 image. I run qemu in daemon mode. When I'm to finish my > session with the guest, I go to the monitor, do a "savevm whatever", > "commit all", "q". > > What I see that the image becomes corrupt very often (qemu-img sees it > as a raw image). (I do the "commit all" only because I suffer and I don't > have any better idea in mind -- I guess it shouldn't have an effect on > the correctness of disk handling). > > Any idea what's wrong? Or a fault-proof way of leaving qemu? There was a bug in the qcow2 support which is fixed in CVS. You can use qcow instead, or upgrade to a recent-ish CVS version of qemu. Thiemo