[Crash-utility] how to generate xen hypervisor core though kdump or other way?

Wed Oct 3 23:03:24 UTC 2012

Now I updated  crash tool, but  the issue  still  exists,  It reports as follow:

Osuse12:/mnt/disk/kenel_debug/sles11sp2 # crash --hyper -f xen-syms-4.1.3_02-0.5.1  xen-syms-dbg-4.1.3_02-0.5.1  /mnt/disk/crash/2012-09-30-19\:03/vmcore 

crash 6.1.0
Copyright (C) 2002-2012  Red Hat, Inc.
Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
Copyright (C) 1999-2006  Hewlett-Packard Co
Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
Copyright (C) 2005, 2011  NEC Corporation
Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
This program is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions.  Enter "help copying" to see the conditions.
This program has absolutely no warranty.  Enter "help warranty" for details.

GNU gdb (GDB) 7.3.1
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...

WARNING: crashing_cpu not found.                                       
crash: invalid kernel virtual address: 523b4fd7c071bf18  type: "fill_pcpu_struct"
WARNING: cannot fill pcpu_struct.

crash: cannot read cpu_info.

> Date: Wed, 3 Oct 2012 11:39:24 -0400
> From: anderson at redhat.com
> To: crash-utility at redhat.com
> Subject: Re: [Crash-utility] how to generate xen hypervisor core though kdump or other way?
> 
> 
> 
> ----- Original Message -----
> > 
> > 
> > yes, it works well.
> > 
> > 
> > title Xen -- SUSE Linux Enterprise Server 11 SP2 - 3.0.38-0.5
> > root (hd0,0)
> > kernel /boot/xen.gz vga=mode-0x317 crashkernel=128M at 16M
> > module /boot/vmlinuz-3.0.38-0.5-xen
> > root=/dev/disk/by-id/ata-WDC_WD3200BEVS-08VAT2_WD-WXD0AA9V4924-part1
> > resume=/dev/disk/by-id/ata-WDC_WD3200BEVS-08VAT2_WD-WXD0AA9V4924-part5
> > showopts vga=0x317
> > module /boot/initrd-3.0.38-0.5-xen
> > 
> > 
> > HjCloud:/mnt/winimg/crash/# echo c >/proc/sysrq-trigger
> > 
> > 
> > HjCloud:/mnt/winimg/crash/2012-09-30-19:03 # ls
> > README.txt System.map-3.0.13-0.27-xen vmcore
> > vmlinux-3.0.13-0.27-xen.gz
> > 
> > 
> > 
> > 
> > 
> > HjCloud:/mnt/winimg/crash/2012-09-30-19:03 # crash -f
> > /boot/xen-syms-4.1.3_02-0.5.1 /boot/xen-syms-dbg-4.1.3_02-0.5.1
> > vmcore
> > 
> > crash 5.1.9
> > Copyright (C) 2002-2011 Red Hat, Inc.
> > Copyright (C) 2004, 2005, 2006 IBM Corporation
> > Copyright (C) 1999-2006 Hewlett-Packard Co
> > Copyright (C) 2005, 2006 Fujitsu Limited
> > Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
> > Copyright (C) 2005 NEC Corporation
> > Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
> > Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
> > This program is free software, covered by the GNU General Public License,
> > and you are welcome to change it and/or distribute copies of it under
> > certain conditions. Enter "help copying" to see the conditions.
> > This program has absolutely no warranty. Enter "help warranty" for
> > details.
> > 
> > crash: /boot/xen-syms-dbg-4.1.3_02-0.5.1: no .gnu_debuglink section
> > GNU gdb (GDB) 7.0
> > Copyright (C) 2009 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later
> > <http://gnu.org/licenses/gpl.html>
> > This is free software: you are free to change and redistribute it.
> > There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> > and "show warranty" for details.
> > This GDB was configured as "x86_64-unknown-linux-gnu"...
> > 
> > WARNING: crashing_cpu not found.
> > crash: invalid kernel virtual address: 523b4fd7c071bf18 type: "fill_pcpu_struct"
> > WARNING: cannot fill pcpu_struct.
> > 
> > crash: cannot read cpu_info.
> > 
> > Do you think my method is right?
> 
> Daniel would know better than I do, but I think you might need to upgrade 
> from crash 5.1.9 to support more recent versions of the Xen hypervisor?
> 
> Dave
> 
>  
> > 
> > 
> > > Date: Wed, 3 Oct 2012 03:18:28 -0700
> > > From: daniel.kiper at oracle.com
> > > To: duanshuidao at hotmail.com; crash-utility at redhat.com
> > > Subject: Re: [Crash-utility] how to generate xen hypervisor core
> > > though kdump or other way?
> > > 
> > > Hi,
> > > 
> > > > My server is Suse Linux SLES11 sp2 verison ,
> > > > 
> > > > HjCloud:~ # uname -a
> > > > Linux HjCloud 3.0.38-0.5-xen #1 SMP Fri Aug 3 09:02:17 UTC 2012
> > > > (358029e) x86_64 x86_64 x86_64 > GNU/Linux
> > > > 
> > > > I know to get dom0 kdump core by "echo c >/proc/sysrq-trigger ",
> > > > 
> > > > but don't know how to get xen hypervisor core, then how to
> > > > analysis
> > > > the hypervisor core by Crash software.
> > > > 
> > > > Can you help me?
> > > 
> > > Does it work? If yes then /proc/vmcore
> > > contains proper memory image with
> > > Xen dump. Just get copy of it,
> > > get xen-syms (or something like that;
> > > I do not know how it is called in SLES)
> > > and pass them to crash tool. That is it.
> > > 
> > > Daniel
> > 
> > --
> > Crash-utility mailing list
> > Crash-utility at redhat.com
> > https://www.redhat.com/mailman/listinfo/crash-utility
> 
> --
> Crash-utility mailing list
> Crash-utility at redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/crash-utility/attachments/20121003/19a79fe6/attachment.htm>