All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wen Congyang <wency@cn.fujitsu.com>
To: Sheldon <shaohef@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [help]: how to use HMP command dump-guest-memory
Date: Thu, 19 Jul 2012 15:41:22 +0800	[thread overview]
Message-ID: <5007BA22.10605@cn.fujitsu.com> (raw)
In-Reply-To: <5007B765.9000306@linux.vnet.ibm.com>

At 07/19/2012 03:29 PM, Sheldon Wrote:
> thank you.
> can you tell me what's the difference between memsave and
> dump-guest-memory without -p option?

IIRC, memsave only contains memory. The core generated by
dump-guest-memory contains registers' value, and you can use
crash to deal with it.

> and what's the difference between *kernel coredump *and
> dump-guest-memory with -p option?

kernel coredump? Do you mean kdump?

They are almost the same. The core generated by dump-guest-memory
contains some registers' value which is not included in the core
generated by kdump.

The kdump runs in the guest, while dump-guest-memory runs in
the host. If you forget to start kdump, you can use dump-guest-memory
to get the core.

Thanks
Wen Congyang

> 
> On 07/19/2012 01:42 PM, Wen Congyang wrote:
>> At 07/19/2012 12:47 AM, Sheldon Wrote:
>>> I want to dump all guest's memory to file ./guestcore
>>> I execute this command as follow:
>>> (qemu) dump-guest-memory -p protocol file:./guestcore
>>> invalid char in expression
>> Please try this command:
>> dump-guest-memory -p file:./guestcore
>>
>> Thanks
>> Wen Congyang
>>
>>>
>>>
>>>
>>>
>>>
> 
> 
> 

  reply	other threads:[~2012-07-19  7:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 16:47 [Qemu-devel] [help]: how to use HMP command dump-guest-memory Sheldon
2012-07-19  5:42 ` Wen Congyang
2012-07-19  7:29   ` Sheldon
2012-07-19  7:41     ` Wen Congyang [this message]
2012-07-19  7:53       ` HATAYAMA Daisuke
2012-07-19  9:25       ` Sheldon

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=5007BA22.10605@cn.fujitsu.com \
    --to=wency@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shaohef@linux.vnet.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.