From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46096) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9H4M-0001cz-Lq for qemu-devel@nongnu.org; Tue, 13 Aug 2013 12:03:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V9H4D-0007QW-9f for qemu-devel@nongnu.org; Tue, 13 Aug 2013 12:03:38 -0400 Received: from cantor2.suse.de ([195.135.220.15]:56725 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V9H4D-0007QC-1p for qemu-devel@nongnu.org; Tue, 13 Aug 2013 12:03:29 -0400 Message-ID: <520A58CD.9000404@suse.de> Date: Tue, 13 Aug 2013 18:03:25 +0200 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] QEMU savevm RAM page offsets List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juerg Haefliger Cc: qemu-devel@nongnu.org Hi, Am 13.08.2013 15:30, schrieb Juerg Haefliger: > I'm writing/extending a little tool (courtesy of Andrew @pikewerks) > that dumps the RAM pages from a savevm file to a raw memory dump file > so that it can be analysed using tools that require a raw dump as > input. Can't you just use QEMU's guest-memory-dump API? Either directly or after loadvm'ing it. Regards, Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg