From: Laszlo Ersek <lersek@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>,
"Juerg Haefliger" <juergh@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU savevm RAM page offsets
Date: Tue, 13 Aug 2013 18:58:37 +0200 [thread overview]
Message-ID: <520A65BD.3030408@redhat.com> (raw)
In-Reply-To: <520A641F.5040608@redhat.com>
(apologies for responding to myself)
On 08/13/13 18:51, Laszlo Ersek wrote:
> On 08/13/13 18:03, Andreas Färber 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.
>
> 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 (= hwaddr).
Laszlo
next prev parent reply other threads:[~2013-08-13 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 13:30 [Qemu-devel] QEMU savevm RAM page offsets Juerg Haefliger
2013-08-13 16:03 ` Andreas Färber
2013-08-13 16:51 ` Laszlo Ersek
2013-08-13 16:58 ` Laszlo Ersek [this message]
2013-08-13 17:52 ` Juerg Haefliger
2013-08-13 18:07 ` Paolo Bonzini
2013-08-13 19:06 ` Juerg Haefliger
2013-08-13 19:25 ` Laszlo Ersek
2013-08-16 6:12 ` Juerg Haefliger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=520A65BD.3030408@redhat.com \
--to=lersek@redhat.com \
--cc=afaerber@suse.de \
--cc=juergh@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).