|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: [PATCH]: kexec: framework and i386
Hi, Kazuo
Good work!
Could you explain usage of your tool?
For using your tool, do I need xen-syms, vmlinux(with debug option),
and so on?
Can this tool extract only dom0 from coredump file?
Can this tool also extract xen or domU?
Best Regards,
Akio Takebe
>I forgot attach my scripts and readme.
>
>On 4/24/06, Kazuo Moriwaka <moriwaka@xxxxxxxxxxxxx> wrote:
>> Hi,
>>
>> On 4/24/06, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
>> > > When a panic occurs, Linux kexec jumps into the preloaded
>> > > kdump kernel (if any). This kernel then reinitiases the
>> > > hardware, using its own device drivers and uses these to
>> > > write out the dump to disk. ISTR that the dump format is
>> > > currently ELF, although I remember some talk on the Fastboot
>> > > ML about adding some extra headers to make OS debugging easier.
>> >
>> > Is Xen and the dom0 kernel dumped as as separate ELF cores?
>>
>> I'm working on clipping domain image from whole-machine dump for x86_32
>> now.
>> Now my prototype reads ELF core and write dom0 image.
>>
>> todo:
>> - Output format is not ELF core yet. Xen domain core image
>> format(works with gdbserverxen).
>> - register information is not work well.
>
>--
>Kazuo Moriwaka
>
>-------------------------------text/plain-------------------------------
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|