[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] libxl: crash fails to load vmcore when the guest memory greater than 4G
Hi, Daniel Thanks for replying. The latest crash tool has the same problem. Following are the results. When the guest memory greater than 4G(such as 8G), crash load vmcore failed. [root@localhost sdb]# crash vmlinux redhat_5.5_32_hvm_8G.core crash 7.0.6 Copyright (C) 2002-2014 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.6 Copyright (C) 2013 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 "i686-pc-linux-gnu"... crash: read error: kernel virtual address: c0787540 type: "possible" WARNING: cannot read cpu_possible_map crash: read error: kernel virtual address: c06fffe0 type: "online" WARNING: cannot read cpu_online_map crash: read error: kernel virtual address: c068a340 type: "system_utsname" crash: vmlinux and redhat_5.5_32_hvm_8G.core do not match! Usage: crash [OPTION]... NAMELIST MEMORY-IMAGE (dumpfile form) crash [OPTION]... [NAMELIST] (live system form) Enter "crash -h" for details. When the guest memory less than 4G(such as 3G), it's ok. [root@localhost sdb]# crash vmlinux redhat_5.5_32_hvm_3G.core crash 7.0.6 Copyright (C) 2002-2014 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.6 Copyright (C) 2013 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 "i686-pc-linux-gnu"... KERNEL: vmlinux DUMPFILE: redhat_5.5_32_hvm_3G.core CPUS: 8 DATE: Tue Jun 3 07:42:19 2014 UPTIME: 00:25:11 LOAD AVERAGE: 0.00, 0.00, 0.00 TASKS: 203 NODENAME: localhost.localdomain RELEASE: 2.6.18-194.el5PAE VERSION: #1 SMP Tue Mar 16 22:00:21 EDT 2010 MACHINE: i686 (2400 Mhz) MEMORY: 3.2 GB PANIC: "" PID: 0 COMMAND: "swapper" TASK: c06893c0 (1 of 8) [THREAD_INFO: c0701000] CPU: 0 STATE: TASK_RUNNING (ACTIVE) WARNING: panic task not found crash> --------------------------------------------------------------------- Sender: Daniel Kiper [mailto:dkiper@xxxxxxxxxxxx] Send Time: 2014年6月5日 20:31 To: Zhangwei (FF) CC: vincent.hanquez@xxxxxxxxxxxxx; stefano.stabellini@xxxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxx; Chenguoping; Xuzhichuang Topic: Re: [Xen-devel] libxl: crash fails to load vmcore when the guest memory greater than 4G On Thu, Jun 05, 2014 at 08:11:28AM +0000, Zhangwei (FF) wrote: > Description of problem: > > A crash dump of a redhat5.5(32 bit) pae xen guest when the guest memory > greater than 4G is not traceable, since crash can't figure out the phys_addr. > But it??s ok when the guest memory less than 4G. > And so is it in the case of a suse11sp1(32 bit) pae xen guest. > > Xen version: 4.1.2 > dom0 version: suse11sp2(64bit) > How reproducible: Always > > Steps to Reproduce: > 1. Start redhat5.5??32bit?? pae guest with memory greater than 4G 2. > Take a crash dump of guest: xl dump-core <domid> > <path-to-corefile-to-save> 3. crash vmlinux <path-to-corefile-to-save> > -- where vmlinux is the unstripped vmlinux image that was used > to generate the bootable vmlinuz of the redhat5.5(32bit) pae guest. > > > Actual results: > [root@localhost sdb]# crash vmlinux redhat_5.5_32_hvm_8G.core > > crash 4.1.2-4.el5 Oh... Please do not use such ancient version of crash. Download latest version from http://people.redhat.com/anderson/ build it and voila... If it does not work drop me a line. Daniel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |