From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lm1ny-0000kZ-LV for qemu-devel@nongnu.org; Tue, 24 Mar 2009 04:16:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lm1nx-0000jz-0C for qemu-devel@nongnu.org; Tue, 24 Mar 2009 04:16:14 -0400 Received: from [199.232.76.173] (port=43248 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lm1nw-0000jw-Ty for qemu-devel@nongnu.org; Tue, 24 Mar 2009 04:16:12 -0400 Received: from naru.obs2.net ([84.20.150.76]:35995 helo=narury.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Lm1nw-0004Hp-Iq for qemu-devel@nongnu.org; Tue, 24 Mar 2009 04:16:12 -0400 Date: Tue, 24 Mar 2009 10:16:08 +0200 From: Riku Voipio Subject: Re: [Qemu-devel] qcow2 snaphot loading Message-ID: <20090324081608.GA17229@kos.to> References: <200903231745.08889.clemens.kol@gmx.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200903231745.08889.clemens.kol@gmx.at> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Clemens Kolbitsch Cc: qemu-devel@nongnu.org On Mon, Mar 23, 2009 at 05:45:08PM +0100, Clemens Kolbitsch wrote: > I just upgraded from rev. 6600 to head and ran into problems loading snapshots > (I also checked this with the 0.10.1 release on the homepage) because the old > revision keeps crashing my Xserver from time to time. > "Error -22 when loading VM state". ..snip.. > then, back in block.c (bdrv_check_byte_request): ...snip... > and snapshot loading exists with the error above. In case this is an error, > could someone have a look? Maybe, there is just no backwards compatibility to > old base images (which would be too bad, but at least I'd know the problem). this was broken in svn commit 6677: Fix CVE-2008-0928 - insufficient block device address range checking (Anthony Liguori) savevm writes to the block device after data...