From: "Zhangwei (FF)" <zw.zhang@huawei.com>
To: "vincent.hanquez@eu.citrix.com" <vincent.hanquez@eu.citrix.com>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Chenguoping <chenguoping@huawei.com>,
Xuzhichuang <xuzhichuang@huawei.com>
Subject: libxl: crash fails to load vmcore when the guest memory greater than 4G
Date: Thu, 5 Jun 2014 08:11:28 +0000 [thread overview]
Message-ID: <0337BCB04941314E9480C9AB7D19454F2F191638@SZXEMA509-MBS.china.huawei.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2511 bytes --]
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
Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 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.
GNU gdb 6.1
Copyright 2004 Free Software Foundation, Inc.
GDB 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.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "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 [-h [opt]][-v][-s][-i file][-d num] [-S] [mapfile] [namelist] [dumpfile]
Enter "crash -h" for details.
Does anyone has any idea on this? Look forward to your reply.
Thank you.
[-- Attachment #1.2: Type: text/html, Size: 18402 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2014-06-05 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 8:11 Zhangwei (FF) [this message]
2014-06-05 12:31 ` libxl: crash fails to load vmcore when the guest memory greater than 4G Daniel Kiper
2014-06-06 2:00 ` Zhangwei (FF)
2014-06-06 21:22 ` Daniel Kiper
2014-06-10 1:50 ` Zhangwei (FF)
2014-06-10 18:14 ` Don Slutz
[not found] ` <53974B10.8000200@terremark.com>
2014-06-11 19:18 ` Daniel Kiper
2014-06-12 1:02 ` Zhangwei (FF)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0337BCB04941314E9480C9AB7D19454F2F191638@SZXEMA509-MBS.china.huawei.com \
--to=zw.zhang@huawei.com \
--cc=chenguoping@huawei.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vincent.hanquez@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xuzhichuang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.