WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] trying to debug xen4 & qemu-dm, Xen reports "core dump

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] trying to debug xen4 & qemu-dm, Xen reports "core dump failed"
From: 0bo0 <0.bugs.only.0@xxxxxxxxx>
Date: Tue, 26 Jan 2010 14:12:18 -0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 26 Jan 2010 14:12:38 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=UCegIAv56pCggDX/QOp+R5ScFa/T3/jjmWX4aPTJqkg=; b=pVwyVlSZAFWbhu4vYzaJky1DxiV4gyJX3yKsy7uwmpwwg+nxOtriiU8chdZa9GttRK MQjIqop8SPjkHvYjXImveuOz1RBrYBIqd4qyRSYU0lP/22RnvF9CU3cq6qwFBV99sAJD I2uwvzb5Wde16mf18Fxo8efi0uvNTd8XHOsL0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QXExPorKUcpihkBVRwH0wjQWKyvjQkexrdCmIsKqLQ6u0Xm6g1UUnscPox0mnrn9Ck CGo2DbTC1PjsUh7SEv1pKhWZ1aqX3oTK3cP/Lj9IfdGUFz9wIPWJn9ikh2PerQOZz4aF ABilKztnn403y0seSeJVoR5dDRGrUKnCW8lGU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C785113A.77E2%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <c67eed301001261325h6be0ae0rbc8c751069455abb@xxxxxxxxxxxxxx> <C785113A.77E2%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Jan 26, 2010 at 1:38 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>