From: Avi Kivity <avi@qumranet.com>
To: david ahern <daahern@cisco.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: tools to dump guest memory and generate core file
Date: Mon, 17 Mar 2008 10:59:27 +0200 [thread overview]
Message-ID: <47DE32EF.5090903@qumranet.com> (raw)
In-Reply-To: <47DDDF43.9020008@cisco.com>
david ahern wrote:
> Does anyone know of tools that can dump memory for a qemu guest with addresses
> as seen by the guest and generate a core file? For instance, say you know the
> guest is running a 32-bit linux kernel with a 1G/3G split. Then you would want
> to dump 1G of memory starting 0xc0000000 and create an ELF core file. The core
> file could then be analyzed using tools like crash (or gdb for the truly
> adventurous).
>
> I know VMware can take a snapshot and generate such a core file. Does a similar
> tool exist for qemu? I see that the qemu console supports a raw memory dump, so
> it should be possible. (Note I am not talking about a core file of the qemu
> process, but rather a core file based on guest memory addressing.)
>
>
You might try connecting with gdb and using the generate-core-file command.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-03-17 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 3:02 tools to dump guest memory and generate core file david ahern
2008-03-17 8:59 ` Avi Kivity [this message]
2008-03-17 23:36 ` david ahern
2008-03-18 6:15 ` Avi Kivity
2008-03-18 9:30 ` Uri Lublin
2008-03-19 0:19 ` david ahern
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=47DE32EF.5090903@qumranet.com \
--to=avi@qumranet.com \
--cc=daahern@cisco.com \
--cc=kvm-devel@lists.sourceforge.net \
/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