qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Jun Koi <junkoi2004@gmail.com>, Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] dump-guest-memory command?
Date: Fri, 16 May 2014 13:30:32 +0200	[thread overview]
Message-ID: <5375F6D8.3080006@redhat.com> (raw)
In-Reply-To: <CA+g7VZ3GpK494RaqhxfwCU+WqbG8RZ=UPG1FOA79BhtrSO7jow@mail.gmail.com>

On 05/16/14 11:59, Jun Koi wrote:

> - is it true that dump-guest-memory just write down physical memory
> page, and does not consider the virtual-memory concept?

No, it isn't.

Basically, "dump-guest-memory" supports two modes of operation, "paging
enabled" and "paging disabled".

Many (most?) people dump for the "crash" utility, which is super smart,
and extra paging info is not needed. For "crash" we just dump the
guest-phys memory ranges the way the guest sees them, and that's it;
"crash" figures out everything from that.

If you want to use "gdb" rather than "crash", or need the guest-virtual
addresses in the ELF vmcore for some other reason, then you should
invoke "dump-guest-memory" with paging enabled.

Enter "help dump-guest-memory" at the qemu monitor prompt, and look for
the "-p" option.

Laszlo

  parent reply	other threads:[~2014-05-16 12:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16  6:24 [Qemu-devel] dump-guest-memory command? Jun Koi
2014-05-16  7:03 ` Greg Kurz
2014-05-16  8:40   ` Jun Koi
2014-05-16  8:45     ` Andreas Färber
2014-05-16  8:51       ` Jun Koi
2014-05-16 10:00         ` Greg Kurz
2014-05-16  9:51     ` Greg Kurz
2014-05-16  9:59       ` Jun Koi
2014-05-16 10:15         ` Greg Kurz
2014-05-16 11:30         ` Laszlo Ersek [this message]
2014-05-16 13:01           ` Jun Koi
2014-05-16 15:38             ` Laszlo Ersek

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=5375F6D8.3080006@redhat.com \
    --to=lersek@redhat.com \
    --cc=gkurz@linux.vnet.ibm.com \
    --cc=junkoi2004@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).