From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: liju.gopinath@oracle.com, Ian.Campbell@citrix.com
Subject: how to generate a smaller core with xm dump-core
Date: Thu, 15 Jan 2015 11:31:35 +0800 [thread overview]
Message-ID: <54B73497.1030500@oracle.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 956 bytes --]
Hi Maintainers,
We are facing issue collecting coredump using the xm dump mechanism in
Dom0.
We face couple of such issues daily, where the VMs panic s and the SA
team is supposed to collect the core.
The actual problem is that where the VMs are having huge RAM like 32+ GB
RAMs dumping the core using *xm dump* generated core of almost the same
size.
And also when the RAM size is huge the time taken to dump is also huge.
Transferring this core dump of this huge size to another system for
analysis is really a pain. I am looking for some solution where we can
generate smaller core using *xm dump* or any other tool.
Something similar to *makedumpfile* which eliminates the zero and
unnecessary pages, which results in core of smaller size.
This has become a hot issue and we terribly need this feature.
Can you come across with anything or are you aware of any feature which
could cater our need….?
thanks
zduan
[-- Attachment #1.2: Type: text/html, Size: 1562 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:[~2015-01-15 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 3:31 Zhenzhong Duan [this message]
2015-01-15 10:20 ` how to generate a smaller core with xm dump-core Ian Campbell
2015-01-15 16:16 ` Don Slutz
2015-01-16 8:39 ` Zhenzhong Duan
2015-01-16 10:14 ` Ian Campbell
2015-01-16 11:38 ` Daniel Kiper
2015-01-30 22:47 ` Don Slutz
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=54B73497.1030500@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=liju.gopinath@oracle.com \
--cc=xen-devel@lists.xen.org \
/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.