From: Keir Fraser <keir.fraser@eu.citrix.com>
To: 0bo0 <0.bugs.only.0@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: trying to debug xen4 & qemu-dm, Xen reports "core dump failed"
Date: Tue, 26 Jan 2010 22:30:18 +0000 [thread overview]
Message-ID: <C7851D7A.77EB%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <c67eed301001261412l72d0fccem46067159eb6e1bf0@mail.gmail.com>
On 26/01/2010 22:12, "0bo0" <0.bugs.only.0@gmail.com> wrote:
> On Tue, Jan 26, 2010 at 1:38 PM, Keir Fraser <keir.fraser@eu.citrix.com>
> wrote:
>> As root:
>> echo '/var/core/core.%e.%u.%p' > /proc/sys/kernel/core_pattern
>>
>> Now try starting your guest. It fails, and hopefully you have a core file in
>> /var/core/. You can load it into gdb as 'gdb /usr/lib/xen/qemu-dm
>> /var/core/name-of-core-file' and then execute bt command at the gdb prompt.
>> That hopefully tells us where qemu-dm crashed.
>
> bash
> ulimit -c unlimited
Actually that probably only enable core dumps for the shell you are running.
Qemu-dm will inherit its ulimits from xend. So you need to enable core dumps
by running 'ulimit -c unlimited' before you start xend, or put it in the
startup script that starts xend. You could also script the echo to
/proc/sys/kernel/core_pattern, but it's definitely safe to do that later
from a shall, as it's a global value, rather than per-process.
-- Keir
next prev parent reply other threads:[~2010-01-26 22:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 18:36 trying to debug xen4 & qemu-dm, Xen reports "core dump failed" 0bo0
2010-01-26 18:36 ` Konrad Rzeszutek Wilk
2010-01-26 18:55 ` 0bo0
2010-01-26 21:10 ` Keir Fraser
2010-01-26 21:25 ` 0bo0
2010-01-26 21:38 ` Keir Fraser
2010-01-26 22:12 ` 0bo0
2010-01-26 22:30 ` Keir Fraser [this message]
2010-01-26 22:47 ` 0bo0
2010-01-27 0:25 ` 0bo0
2010-01-27 0:59 ` 0bo0
2010-01-27 8:27 ` Keir Fraser
2010-01-27 9:10 ` Keir Fraser
2010-01-27 15:41 ` 0bo0
2010-01-27 15:46 ` Keir Fraser
2010-01-27 16:19 ` Sander Eikelenboom
2010-01-27 16:22 ` 0bo0
2010-01-27 16:40 ` 0bo0
2010-01-28 22:08 ` 0bo0
2010-01-27 16:20 ` 0bo0
2010-01-27 8:27 ` Keir Fraser
2010-01-29 0:21 ` Justin T. Gibbs
2010-01-29 0:42 ` 0bo0
2010-01-29 0:44 ` Justin T. Gibbs
2010-01-29 0:54 ` 0bo0
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=C7851D7A.77EB%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=0.bugs.only.0@gmail.com \
--cc=xen-devel@lists.xensource.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.