xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: 0bo0 <0.bugs.only.0@gmail.com>
To: Keir Fraser <keir.fraser@eu.citrix.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 14:12:18 -0800	[thread overview]
Message-ID: <c67eed301001261412l72d0fccem46067159eb6e1bf0@mail.gmail.com> (raw)
In-Reply-To: <C785113A.77E2%keir.fraser@eu.citrix.com>

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
echo '/var/core/core.%e.%u.%p' > /proc/sys/kernel/core_pattern
mkdir -p /var/core
cat /proc/sys/kernel/core_pattern
/var/core/core.%e.%u.%p

xm create /etc/xen/vm/test.cfg
  Using config file "/etc/xen/vm/test.cfg".
  Error: Domain 'test' does not exist.

ls -al /var/core
  total 8
  drwxr-xr-x  2 root root 4096 2010-01-26 13:48 ./
  drwxr-xr-x 18 root root 4096 2010-01-26 13:48 ../

@ syslog, though, i do see ....

Jan 26 14:09:17 server kernel: [  547.023464] kjournald starting.
Commit interval 15 seconds
Jan 26 14:09:17 server kernel: [  547.118565] EXT3-fs: mounted
filesystem with ordered data mode.
Jan 26 14:09:18 server logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/3/51712
Jan 26 14:09:18 server logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/3/51744
Jan 26 14:09:18 server logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/3/51728
Jan 26 14:09:18 server kernel: [  548.456142] qemu-dm[6791]: segfault
at 7fff7ee4169a ip 000000000047b974 sp 00007fff7ee40210 error 4 in
qemu-dm[400000+10b000]
Jan 26 14:09:18 server logger: /etc/xen/scripts/vif-bridge: online
XENBUS_PATH=backend/vif/3/0
Jan 26 14:09:18 server kernel: [  548.697863] device vif3.0 entered
promiscuous mode
Jan 26 14:09:19 server kernel: [  548.828028] br02: port 1(vif3.0)
entering forwarding state
Jan 26 14:09:19 server kernel: [  548.984448] physdev match: using
--physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
non-bridged traffic is not supported anymore.
Jan 26 14:09:19 server logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge online for vif3.0, bridge br02.
Jan 26 14:09:19 server logger: /etc/xen/scripts/vif-bridge: Writing
backend/vif/3/0/hotplug-status connected to xenstore.
Jan 26 14:09:19 server logger: /etc/xen/scripts/block: Writing
backend/vbd/3/51712/physical-device fd:d to xenstore.
Jan 26 14:09:19 server kernel: [  549.267962] (cdrom_add_media_watch()
file=/usr/src/packages/BUILD/kernel-xen-2.6.31.8/linux-2.6.31/drivers/xen/blkback/cdrom.c,
line=108) nodename:backend/vbd/3/51712
Jan 26 14:09:19 server kernel: [  549.474577] (cdrom_is_type()
file=/usr/src/packages/BUILD/kernel-xen-2.6.31.8/linux-2.6.31/drivers/xen/blkback/cdrom.c,
line=95) type:0
Jan 26 14:09:19 server logger: /etc/xen/scripts/block: Writing
backend/vbd/3/51712/hotplug-status connected to xenstore.
Jan 26 14:09:20 server logger: /etc/xen/scripts/block: Writing
backend/vbd/3/51728/physical-device fd:e to xenstore.
Jan 26 14:09:20 server kernel: [  550.443509] (cdrom_add_media_watch()
file=/usr/src/packages/BUILD/kernel-xen-2.6.31.8/linux-2.6.31/drivers/xen/blkback/cdrom.c,
line=108) nodename:backend/vbd/3/51728
Jan 26 14:09:20 server kernel: [  550.657671] (cdrom_is_type()
file=/usr/src/packages/BUILD/kernel-xen-2.6.31.8/linux-2.6.31/drivers/xen/blkback/cdrom.c,
line=95) type:0
Jan 26 14:09:20 server logger: /etc/xen/scripts/block: Writing
backend/vbd/3/51728/hotplug-status connected to xenstore.
Jan 26 14:09:21 server logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vkbd/3/0
Jan 26 14:09:21 server logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/console/3/0
Jan 26 14:09:22 server kernel: [  552.224799] br02: port 1(vif3.0)
entering disabled state
Jan 26 14:09:22 server kernel: [  552.335801] br02: port 1(vif3.0)
entering disabled state
Jan 26 14:09:22 server logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vfb/3/0
Jan 26 14:09:22 server logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/3/51728
Jan 26 14:09:22 server logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/3/51712
Jan 26 14:09:22 server logger: /etc/xen/scripts/vif-bridge: offline
XENBUS_PATH=backend/vif/3/0
Jan 26 14:09:22 server logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/3/51728
Jan 26 14:09:22 server logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/3/51712
Jan 26 14:09:22 server logger: /etc/xen/scripts/vif-bridge: brctl
delif br02 vif3.0 failed
Jan 26 14:09:22 server logger: /etc/xen/scripts/vif-bridge: ifconfig
vif3.0 down failed
Jan 26 14:09:22 server kernel: [  552.662465] physdev match: using
--physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
non-bridged traffic is not supported anymore.
Jan 26 14:09:22 server logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge offline for vif3.0, bridge br02.
Jan 26 14:09:22 server logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vif/3/0
Jan 26 14:09:23 server logger: /etc/xen/scripts/block: Writing
backend/vbd/3/51744/physical-device fd:f to xenstore.
Jan 26 14:09:23 server logger: /etc/xen/scripts/block: Writing
backend/vbd/3/51744/hotplug-status connected to xenstore.
Jan 26 14:09:23 server logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/3/51744
Jan 26 14:09:23 server logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/3/51744

  reply	other threads:[~2010-01-26 22:12 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 [this message]
2010-01-26 22:30         ` Keir Fraser
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=c67eed301001261412l72d0fccem46067159eb6e1bf0@mail.gmail.com \
    --to=0.bugs.only.0@gmail.com \
    --cc=keir.fraser@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).