From mboxrd@z Thu Jan 1 00:00:00 1970 From: Akio Takebe Subject: Re: Re: [PATCH]: kexec: framework and i386 Date: Tue, 25 Apr 2006 10:15:24 +0900 Message-ID: <6AC66805BACE46takebe_akio@jp.fujitsu.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Kazuo Moriwaka , Ian Pratt Cc: Akio Takebe , Magnus Damm , xen-devel@lists.xensource.com, Mark Williamson List-Id: xen-devel@lists.xenproject.org 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 wrote: >> Hi, >> >> On 4/24/06, Ian Pratt 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@lists.xensource.com >http://lists.xensource.com/xen-devel