From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34061)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lersek@redhat.com>) id 1V9HtJ-0001Uo-NQ
	for qemu-devel@nongnu.org; Tue, 13 Aug 2013 12:56:23 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lersek@redhat.com>) id 1V9HtD-00041Q-Fr
	for qemu-devel@nongnu.org; Tue, 13 Aug 2013 12:56:17 -0400
Received: from mx1.redhat.com ([209.132.183.28]:22448)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lersek@redhat.com>) id 1V9HtD-00041G-5S
	for qemu-devel@nongnu.org; Tue, 13 Aug 2013 12:56:11 -0400
Message-ID: <520A65BD.3030408@redhat.com>
Date: Tue, 13 Aug 2013 18:58:37 +0200
From: Laszlo Ersek <lersek@redhat.com>
MIME-Version: 1.0
References: <CADLDEKvEVSXQeKKrU0Ke9cgMf2VBr=ooTmXrUgmb3C+XEmsSmA@mail.gmail.com>
	<520A58CD.9000404@suse.de> <520A641F.5040608@redhat.com>
In-Reply-To: <520A641F.5040608@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] QEMU savevm RAM page offsets
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?ISO-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>, Juerg Haefliger <juergh@gmail.com>
Cc: qemu-devel@nongnu.org

(apologies for responding to myself)

On 08/13/13 18:51, Laszlo Ersek wrote:
> On 08/13/13 18:03, Andreas F=E4rber wrote:
>> 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.
>=20
> That used to suffer from the exact same problem Juerg described, but I
> fixed it for 1.6.

... note that the savevm file format doesn't need fixing; it is meant
for internal consumption only (ie. guest RAM saved in ram_addr_t space,
then loaded back into ram_addr_t space). It is not meant for external
tools that expect guest-phys addresses (=3D hwaddr).

Laszlo