Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Crash Utility (http://www.linux-archive.org/crash-utility/)
-   -   how to generate xen hypervisor core though kdump or other way? (http://www.linux-archive.org/crash-utility/709271-how-generate-xen-hypervisor-core-though-kdump-other-way.html)

Daniel Kiper 10-03-2012 10:18 AM

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@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

hu jun 10-03-2012 10:56 AM

how to generate xen hypervisor core though kdump or other way?
 
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@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? *



> Date: Wed, 3 Oct 2012 03:18:28 -0700
> From: daniel.kiper@oracle.com
> To: duanshuidao@hotmail.com; crash-utility@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@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

Herbert van den Bergh 10-03-2012 03:27 PM

how to generate xen hypervisor core though kdump or other way?
 
Use the crash --hyper flag.



Thanks,

Herbert.



On 10/3/12 3:56 AM, hu jun wrote:





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@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? *







> Date: Wed, 3 Oct 2012 03:18:28 -0700

> From: daniel.kiper@oracle.com

> To: duanshuidao@hotmail.com; crash-utility@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@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility





--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

Dave Anderson 10-03-2012 03:39 PM

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@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@oracle.com
> > To: duanshuidao@hotmail.com; crash-utility@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@redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

hu jun 10-03-2012 11:03 PM

how to generate xen hypervisor core though kdump or other way?
 
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@redhat.com
> To: crash-utility@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@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@oracle.com
> > > To: duanshuidao@hotmail.com; crash-utility@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@redhat.com
> > https://www.redhat.com/mailman/listinfo/crash-utility
>
> --
> Crash-utility mailing list
> Crash-utility@redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

Daniel Kiper 10-04-2012 10:20 AM

how to generate xen hypervisor core though kdump or other way?
 
Hi,

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

[...]

As I remember "crash xen-syms-dbg-4.1.3_02-0.5.1 /mnt/disk/crash/2012-09-30-19:03/vmcore"
should be sufficient. If it still does not work
please send me output from following command:

# readelf -Wa /mnt/disk/crash/2012-09-30-19:03/vmcore

Daniel

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

hu jun 10-05-2012 04:43 AM

how to generate xen hypervisor core though kdump or other way?
 
HjCloud:/mnt/winimg/kenel_debug/sles11sp2/usr/boot # crash vmlinux-3.0.13-0.27-xen.gz ../lib/debug/boot/vmlinux-3.0.13-0.27-xen.debug /mnt/winimg/crash/2012-09-30-19:03/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: vmlinux-3.0.13-0.27-xen.gz: original filename unknown
Use "-f vmlinux-3.0.13-0.27-xen.gz" on command line to prevent this message.

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"...

KERNEL: vmlinux-3.0.13-0.27-xen.gz
DEBUGINFO: ../lib/debug/boot/vmlinux-3.0.13-0.27-xen.debug
DUMPFILE: /mnt/winimg/crash/2012-09-30-19:03/vmcore
CPUS: 2
DATE: Sun Sep 30 19:02:52 2012
UPTIME: 07:45:24
LOAD AVERAGE: 0.32, 0.23, 0.14
TASKS: 207
NODENAME: HjCloud
RELEASE: 3.0.13-0.27-xen
VERSION: #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b)
MACHINE: x86_64 (2793 Mhz)
MEMORY: 3.6 GB
PANIC: "[27924.896523] Oops: 0002 [#1] SMP " (check log for details)
PID: 7450
COMMAND: "bash"
TASK: ffff8800cfbf61c0 [THREAD_INFO: ffff8800cba86000]
CPU: 1
STATE: TASK_RUNNING (PANIC)


Osuse12:/mnt/disk/kenel_debug/sles11sp2 # crash 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.

Osuse12:/mnt/disk/kenel_debug/sles11sp2 # readelf -Wa /mnt/disk/
.Trash-0/ crash/ iso/ kenel_debug/ lost+found/ xen_vm_config/
Osuse12:/mnt/disk/kenel_debug/sles11sp2 # readelf -Wa /mnt/disk/crash/2012-
2012-09-30-19:03/ 2012-10-01-08:11/ 2012-1003-1946.57-sles10sp4.10.core
Osuse12:/mnt/disk/kenel_debug/sles11sp2 # readelf -Wa /mnt/disk/crash/2012-09-30-19:03/
README.txt System.map-3.0.13-0.27-xen vmcore vmlinux-3.0.13-0.27-xen.gz
Osuse12:/mnt/disk/kenel_debug/sles11sp2 # readelf -Wa /mnt/disk/crash/2012-09-30-19:03/vmcore
ELF Header:
Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
Class: ELF64
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: CORE (Core file)
Machine: Advanced Micro Devices X86-64
Version: 0x1
Entry point address: 0x0
Start of program headers: 64 (bytes into file)
Start of section headers: 0 (bytes into file)
Flags: 0x0
Size of this header: 64 (bytes)
Size of program headers: 56 (bytes)
Number of program headers: 8
Size of section headers: 0 (bytes)
Number of section headers: 0
Section header string table index: 0

There are no sections in this file.

There are no sections in this file.

Program Headers:
Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
NOTE 0x000200 0x0000000000000000 0x0000000000000000 0x001898 0x001898 0
LOAD 0x001a98 0xffff810000000000 0x0000000000000000 0x0a0000 0x0a0000 RWE 0
LOAD 0x0a1a98 0xffff810000100000 0x0000000000100000 0xf00000 0xf00000 RWE 0
LOAD 0xfa1a98 0xffff810009000000 0x0000000009000000 0xb68a1000 0xb68a1000 RWE 0
LOAD 0xb7842a98 0xffff8100bf8a7000 0x00000000bf8a7000 0x110000 0x110000 RWE 0
LOAD 0xb7952a98 0xffff8100bfa0f000 0x00000000bfa0f000 0x0b7000 0x0b7000 RWE 0
LOAD 0xb7a09a98 0xffff8100bfdff000 0x00000000bfdff000 0x001000 0x001000 RWE 0
LOAD 0xb7a0aa98 0xffff810100000000 0x0000000100000000 0x3c000000 0x3c000000 RWE 0

There is no dynamic section in this file.

There are no relocations in this file.

There are no unwind sections in this file.

No version information found in this file.

Notes at offset 0x00000200 with length 0x00001898:
Owner Data size Description
CORE 0x00000150 NT_PRSTATUS (prstatus structure)
Xen 0x00000020 Unknown note type: (0x01000002)
CORE 0x00000150 NT_PRSTATUS (prstatus structure)
Xen 0x00000020 Unknown note type: (0x01000002)
Xen 0x00000050 Unknown note type: (0x01000001)
VMCOREINFO 0x000004f5 Unknown note type: (0x00000000)
VMCOREINFO_XEN 0x00000fe4 Unknown note type: (0x00000000)

> Date: Thu, 4 Oct 2012 03:20:17 -0700
> From: daniel.kiper@oracle.com
> To: duanshuidao@hotmail.com; crash-utility@redhat.com
> Subject: Re: [Crash-utility] how to generate xen hypervisor core though kdump or other way?
>
> Hi,
>
> > Now I updated crash tool, but the issue still exists, It reports as follow:
>
> [...]
>
> As I remember "crash xen-syms-dbg-4.1.3_02-0.5.1 /mnt/disk/crash/2012-09-30-19:03/vmcore"
> should be sufficient. If it still does not work
> please send me output from following command:
>
> # readelf -Wa /mnt/disk/crash/2012-09-30-19:03/vmcore
>
> Daniel

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

Daniel Kiper 10-05-2012 08:05 AM

how to generate xen hypervisor core though kdump or other way?
 
Hi,

> 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: vmlinux-3.0.13-0.27-xen.gz: original filename unknown
> Use "-f vmlinux-3.0.13-0.27-xen.gz" on command line to prevent this message.
>
> 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"...
>
> KERNEL: vmlinux-3.0.13-0.27-xen.gz
> DEBUGINFO: ../lib/debug/boot/vmlinux-3.0.13-0.27-xen.debug
> DUMPFILE: /mnt/winimg/crash/2012-09-30-19:03/vmcore
> CPUS: 2
> DATE: Sun Sep 30 19:02:52 2012
> UPTIME: 07:45:24
> LOAD AVERAGE: 0.32, 0.23, 0.14
> TASKS: 207
> NODENAME: HjCloud
> RELEASE: 3.0.13-0.27-xen
> VERSION: #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b)
> MACHINE: x86_64 (2793 Mhz)
> MEMORY: 3.6 GB
> PANIC: "[27924.896523] Oops: 0002 [#1] SMP " (check log for details)
> PID: 7450
> COMMAND: "bash"
> TASK: ffff8800cfbf61c0 [THREAD_INFO: ffff8800cba86000]
> CPU: 1
> STATE: TASK_RUNNING (PANIC)

[...]

It looks that crash tool reads only dom0 part.
However, it looks that there is also some info
about Xen hypervisor state, too. I heard that
it is possible to do that in that way but personally
I did not such things. I think that you should
first check SLES documentation (man crash?)/groups/...
As I know this distribution use strongly customized
things (e.g. Linux Kernel) and they could behave
differently then vanilla one.

I am going to check that once but
now I am working on other things.

Daniel

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

Daniel Kiper 10-05-2012 08:37 AM

how to generate xen hypervisor core though kdump or other way?
 
Hi,

> 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: vmlinux-3.0.13-0.27-xen.gz: original filename unknown
> Use "-f vmlinux-3.0.13-0.27-xen.gz" on command line to prevent this message.
>
> 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"...
>
> KERNEL: vmlinux-3.0.13-0.27-xen.gz
> DEBUGINFO: ../lib/debug/boot/vmlinux-3.0.13-0.27-xen.debug
> DUMPFILE: /mnt/winimg/crash/2012-09-30-19:03/vmcore
> CPUS: 2
> DATE: Sun Sep 30 19:02:52 2012
> UPTIME: 07:45:24
> LOAD AVERAGE: 0.32, 0.23, 0.14
> TASKS: 207
> NODENAME: HjCloud
> RELEASE: 3.0.13-0.27-xen
> VERSION: #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b)
> MACHINE: x86_64 (2793 Mhz)
> MEMORY: 3.6 GB
> PANIC: "[27924.896523] Oops: 0002 [#1] SMP " (check log for details)
> PID: 7450
> COMMAND: "bash"
> TASK: ffff8800cfbf61c0 [THREAD_INFO: ffff8800cba86000]
> CPU: 1
> STATE: TASK_RUNNING (PANIC)

[...]

One more question. What is the size of crash dump file?
Is it almost equal to:
<machine_memory_size> - <memory_reserved_for_crash_kernel>

Daniel

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

hu jun 10-05-2012 11:46 AM

how to generate xen hypervisor core though kdump or other way?
 
> Date: Fri, 5 Oct 2012 01:37:37 -0700
> From: daniel.kiper@oracle.com
> To: duanshuidao@hotmail.com
> CC: crash-utility@redhat.com
> Subject: RE: [Crash-utility] how to generate xen hypervisor core though kdump or other way?
>
> Hi,
>
> > 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: vmlinux-3.0.13-0.27-xen.gz: original filename unknown
> > Use "-f vmlinux-3.0.13-0.27-xen.gz" on command line to prevent this message.
> >
> > 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"...
> >
> > KERNEL: vmlinux-3.0.13-0.27-xen.gz
> > DEBUGINFO: ../lib/debug/boot/vmlinux-3.0.13-0.27-xen.debug
> > DUMPFILE: /mnt/winimg/crash/2012-09-30-19:03/vmcore
> > CPUS: 2
> > DATE: Sun Sep 30 19:02:52 2012
> > UPTIME: 07:45:24
> > LOAD AVERAGE: 0.32, 0.23, 0.14
> > TASKS: 207
> > NODENAME: HjCloud
> > RELEASE: 3.0.13-0.27-xen
> > VERSION: #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b)
> > MACHINE: x86_64 (2793 Mhz)
> > MEMORY: 3.6 GB
> > PANIC: "[27924.896523] Oops: 0002 [#1] SMP " (check log for details)
> > PID: 7450
> > COMMAND: "bash"
> > TASK: ffff8800cfbf61c0 [THREAD_INFO: ffff8800cba86000]
> > CPU: 1
> > STATE: TASK_RUNNING (PANIC)
>
> [...]
>
> One more question. What is the size of crash dump file?
> Is it almost equal to:
> <machine_memory_size> - <memory_reserved_for_crash_kernel>
>
> Daniel

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility


All times are GMT. The time now is 04:42 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.