qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] Python-lang gdb script to extract x86_64 guest vmcore from qemu coredump
Date: Mon, 28 Oct 2013 09:50:36 +0100	[thread overview]
Message-ID: <526E255C.2030302@redhat.com> (raw)
In-Reply-To: <CAJSP0QW61f6GhWELtDeUZqbBsrTWs5p8ca59_o5yy8sZNV+2cg@mail.gmail.com>

On 10/11/13 19:54, Stefan Hajnoczi wrote:
> On Thu, Sep 12, 2013 at 9:46 PM, Laszlo Ersek <lersek@redhat.com> wrote:
>> When qemu dies unexpectedly, for example in response to an explicit
>> abort() call, or (more importantly) when an external signal is delivered
>> to it that results in a coredump, sometimes it is useful to extract the
>> guest vmcore from the qemu process' memory image. The guest vmcore might
>> help understand an emulation problem in qemu, or help debug the guest.
>>
>> This script reimplements (and cuts many features of) the
>> qmp_dump_guest_memory() command in gdb/Python,
>>
>>   https://sourceware.org/gdb/current/onlinedocs/gdb/Python-API.html
>>
>> working off the saved memory image of the qemu process. The docstring in
>> the patch (serving as gdb help text) describes the limitations relative to
>> the QMP command.
>>
>> Dependencies of qmp_dump_guest_memory() have been reimplemented as needed.
>> I sought to follow the general structure, sticking to original function
>> names where possible. However, keeping it simple prevailed in some places.
>>
>> The patch has been tested with a 4 VCPU, 768 MB, RHEL-6.4
>> (2.6.32-358.el6.x86_64) guest:
> 
> I tried this out with qemu-kvm-1.1.2 and it worked after a few minor
> tweaks due to memory data structure changes.  I did hit a problem with
> crash since the vmlinux was 32-bit and the guest dump was 64-bit.  But
> from what I can tell dump-guest-memory works as advertised.
> 
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

Could someone please pick up the patch?

Thanks!
Laszlo

  reply	other threads:[~2013-10-28  8:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12 19:46 [Qemu-devel] [PATCH] Python-lang gdb script to extract x86_64 guest vmcore from qemu coredump Laszlo Ersek
2013-09-20 16:49 ` Laszlo Ersek
2013-10-11 17:54 ` Stefan Hajnoczi
2013-10-28  8:50   ` Laszlo Ersek [this message]
2013-10-14  7:45 ` Stefan Hajnoczi
2013-12-16 14:55 ` Michael S. Tsirkin
2013-12-16 23:35 ` Anthony Liguori

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=526E255C.2030302@redhat.com \
    --to=lersek@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 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).