qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Dave Anderson <anderson@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [Qemu-devel] [RFC] dump memory when host pci device is used by guest
Date: Sat, 26 Nov 2011 08:27:14 -0200	[thread overview]
Message-ID: <4ED0BF02.1020704@web.de> (raw)
In-Reply-To: <4ECA0696.2070603@cn.fujitsu.com>

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

On 2011-11-21 06:06, Wen Congyang wrote:
> At 11/18/2011 08:46 PM, Jan Kiszka Write:
>> On 2011-11-16 14:29, Dave Anderson wrote:
>>>
>>>
>>> ----- Original Message -----
>>>> Hi, all
>>>>
>>>> 'virsh dump' can not work when host pci device is used by guest. We have
>>>> discussed this issue here:
>>>> http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg00736.html
>>>>
>>>> We have determined to introduce a new command dump to dump memory.
>>>> The core file's format can be elf.
>>>>
>>>> I created a kdump-elf vmcore, and found that it can be used by both
>>>> crash and gdb:
>>>>
> 
>>> From an enterprise/support point of view, the wholesale replacement
>>> of the current use of the savevm dumpfile format by "virsh dump" with
>>> this ELF style format would be a *huge* improvement. 
>>
>> Yes, fully agree. Would be cool if that could actually work for both
>> crash and gdb. Looking forward!
> 
> Because the memory size for x86 machine can greater than 4G, so we should
> create elf64 format core file for 32bit OS.
> 
> I create a vmcore: the guest OS is 32-bit, and the vmcore is elf64 format.
> I can use crash to anaylyze it, but gdb can not do the same thing.
> 
> I create a kdump-elf64 vmcore on 32-bit machine, and gdb still can not anaylyze
> it.
> 
> Does gdb support elf64 format core file on x86 box?
> 

Dunno, but I'm trying to pull in some interested gdb folks.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2011-11-26 10:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16  8:27 [Qemu-devel] [RFC] dump memory when host pci device is used by guest Wen Congyang
2011-11-16 16:29 ` Dave Anderson
2011-11-18 12:46   ` Jan Kiszka
2011-11-21  8:06     ` Wen Congyang
2011-11-26 10:27       ` Jan Kiszka [this message]
2011-11-26 21:45         ` Sergio Durigan Junior
2011-11-29  5:41 ` [Qemu-devel] [RFC][PATCH] introduce a new monitor command 'dump' to dump guest's memory Wen Congyang

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=4ED0BF02.1020704@web.de \
    --to=jan.kiszka@web.de \
    --cc=anderson@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sergiodj@redhat.com \
    --cc=wency@cn.fujitsu.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).