<HTML><HEAD> <META content="text/html; charset=ISO-8859-1" http-equiv=Content-Type></HEAD> <BODY dir=ltr bgColor=#ffffff text=#000000> <DIV dir=ltr> <DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 14pt"> <DIV><FONT size=4>Hi Daniel:</FONT></DIV> <DIV><FONT size=4></FONT> </DIV> <DIV><FONT size=4>how are you going , daniel?</FONT></DIV> <DIV style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none"> <DIV style="FONT: 10pt tahoma"> <DIV><FONT size=4 face=Calibri></FONT> </DIV> <DIV style="BACKGROUND: #f5f5f5"> <DIV style="font-color: black"><B>From:</B> <A title=herbert.van.den.bergh@oracle.com href="mailto:herbert.van.den.bergh@oracle.com">Herbert van den Bergh</A> </DIV> <DIV><B>Sent:</B> Wednesday, October 03, 2012 11:27 PM</DIV> <DIV><B>To:</B> <A title=crash-utility@redhat.com href="mailto:crash-utility@redhat.com">Discussion list for crash utility usage, maintenance and development</A> ; <A title=duanshuidao@hotmail.com href="mailto:duanshuidao@hotmail.com">hu jun</A> </DIV> <DIV><B>Cc:</B> <A title=daniel.kiper@oracle.com href="mailto:daniel.kiper@oracle.com">daniel.kiper@oracle.com</A> </DIV> <DIV><B>Subject:</B> Re: [Crash-utility] how to generate xen hypervisor core though kdump or other way?</DIV></DIV></DIV> <DIV> </DIV></DIV> <DIV style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">Use the crash --hyper flag.<BR><BR>Thanks,<BR>Herbert.<BR><BR> <DIV class=moz-cite-prefix>On 10/3/12 3:56 AM, hu jun wrote:<BR></DIV> <BLOCKQUOTE cite=mid:COL115-W208BB38849286462E8E918BC850@phx.gbl type="cite"> <STYLE></STYLE> <DIV dir=ltr>yes, it works well.<BR><BR><BR>title Xen -- SUSE Linux Enterprise Server 11 SP2 - 3.0.38-0.5<BR>root (hd0,0)<BR>kernel /boot/xen.gz vga=mode-0x317 crashkernel=128M@16M<BR>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<BR>module /boot/initrd-3.0.38-0.5-xen<BR><BR><BR>HjCloud:/mnt/winimg/crash/# echo c >/proc/sysrq-trigger <BR><BR><BR>HjCloud:/mnt/winimg/crash/2012-09-30-19:03 # ls<BR>README.txt System.map-3.0.13-0.27-xen vmcore vmlinux-3.0.13-0.27-xen.gz<BR><BR><BR><BR><BR><BR>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<BR><BR>crash 5.1.9<BR>Copyright (C) 2002-2011 Red Hat, Inc.<BR>Copyright (C) 2004, 2005, 2006 IBM Corporation<BR>Copyright (C) 1999-2006 Hewlett-Packard Co<BR>Copyright (C) 2005, 2006 Fujitsu Limited<BR>Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.<BR>Copyright (C) 2005 NEC Corporation<BR>Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.<BR>Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.<BR>This program is free software, covered by the GNU General Public License,<BR>and you are welcome to change it and/or distribute copies of it under<BR>certain conditions. Enter "help copying" to see the conditions.<BR>This program has absolutely no warranty. Enter "help warranty" for details.<BR><BR>crash: /boot/xen-syms-dbg-4.1.3_02-0.5.1: no .gnu_debuglink section<BR>GNU gdb (GDB) 7.0<BR>Copyright (C) 2009 Free Software Foundation, Inc.<BR>License GPLv3+: GNU GPL version 3 or later <A class=moz-txt-link-rfc2396E href="http://gnu.org/licenses/gpl.html"><http://gnu.org/licenses/gpl.html></A><BR>This is free software: you are free to change and redistribute it.<BR>There is NO WARRANTY, to the extent permitted by law. Type "show copying"<BR>and "show warranty" for details.<BR>This GDB was configured as "x86_64-unknown-linux-gnu"...<BR><BR>WARNING: crashing_cpu not found. <BR>crash: invalid kernel virtual address: 523b4fd7c071bf18 type: "fill_pcpu_struct"<BR>WARNING: cannot fill pcpu_struct.<BR><BR>crash: cannot read cpu_info.<BR><BR><BR><BR><BR><BR>Do you think my method is right? <BR><BR><BR><BR> <DIV>> Date: Wed, 3 Oct 2012 03:18:28 -0700<BR>> From: <A class=moz-txt-link-abbreviated href="mailto:daniel.kiper@oracle.com">daniel.kiper@oracle.com</A><BR>> To: <A class=moz-txt-link-abbreviated href="mailto:duanshuidao@hotmail.com">duanshuidao@hotmail.com</A>; <A class=moz-txt-link-abbreviated href="mailto:crash-utility@redhat.com">crash-utility@redhat.com</A><BR>> Subject: Re: [Crash-utility] how to generate xen hypervisor core though kdump or other way?<BR>> <BR>> Hi,<BR>> <BR>> > My server is Suse Linux SLES11 sp2 verison ,<BR>> ><BR>> > HjCloud:~ # uname -a<BR>> > 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<BR>> ><BR>> > I know to get dom0 kdump core by "echo c >/proc/sysrq-trigger ",<BR>> ><BR>> > but don't know how to get xen hypervisor core, then how to analysis<BR>> > the hypervisor core by Crash software.<BR>> ><BR>> > Can you help me?<BR>> <BR>> Does it work? If yes then /proc/vmcore<BR>> contains proper memory image with<BR>> Xen dump. Just get copy of it,<BR>> get xen-syms (or something like that;<BR>> I do not know how it is called in SLES)<BR>> and pass them to crash tool. That is it.<BR>> <BR>> Daniel<BR></DIV></DIV><BR> <FIELDSET class=mimeAttachmentHeader></FIELDSET> <BR><PRE wrap="">-- Crash-utility mailing list <A class=moz-txt-link-abbreviated href="mailto:Crash-utility@redhat.com">Crash-utility@redhat.com</A> <A class=moz-txt-link-freetext href="https://www.redhat.com/mailman/listinfo/crash-utility">https://www.redhat.com/mailman/listinfo/crash-utility</A></PRE></BLOCKQUOTE><BR></DIV></DIV></DIV></BODY></HTML>