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/
Home Products Support Community News


[Xen-devel] xen debugger ??

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xen debugger ??
From: sanket hase <shase@xxxxxxxxxxxxxx>
Date: Sat, 17 Nov 2007 01:32:09 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 16 Nov 2007 22:32:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20070728)

Hurdle race continues ..


xm create now fails silently ....

xen412:/etc/xen# xm create -c freebsd_xen
Using config file "./freebsd_xen".
Started domain freebsd-xen


Note: no errror msg :(


From xend.log ... all that I see is domain has crashed ..

[2007-11-17 00:58:19 20661] DEBUG (__init__:1072) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '3d49b1cd-0bea-d78d-34e5-6ff6cb1d5d0a', 'on_reboot': 'restart', 'start_time': '1195279099.88', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'image': "(linux (kernel /boot/kernel) (args 'root=/dev/xbd769a boot_verbose,boot_single,vfs.root.mountfrom=ufs:/dev/xbd769a,kern.hz=100') (rtc_timeoffset 0) (notes))", 'name': 'freebsd-xen'} [2007-11-17 00:58:19 20661] DEBUG (__init__:1072) Storing domain details: {'console/ring-ref': '176977', 'console/port': '2', 'name': 'freebsd-xen', 'console/limit': '1048576', 'vm': '/vm/3d49b1cd-0bea-d78d-34e5-6ff6cb1d5d0a', 'domid': '28', 'cpu/0/availability': 'online', 'memory/target': '262144', 'control/platform-feature-multiprocessor-suspend': '1', 'store/ring-ref': '181035', 'store/port': '1'} [2007-11-17 00:58:19 20661] DEBUG (__init__:1072) XendDomainInfo.handleShutdownWatch [2007-11-17 00:58:19 20661] WARNING (__init__:1072)* Domain has crashed: name=freebsd-xen id=28.* [2007-11-17 00:58:20 20661] ERROR (__init__:1072) VM freebsd-xen restarting too fast (1.779341 seconds since the last restart). Refusing to restart to avoid loops. [2007-11-17 00:58:20 20661] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=28 [2007-11-17 00:58:20 20661] DEBUG (__init__:1072) XendDomainInfo.destroyDomain(28)


I tried xm dmesg which dumps kernel stack ....


Can I somehow get a stack-trace for this crash ? And all this boils down to if there are ways to increase the verbosity of xend.log or dmesg ...
Or if there are better ways to debug it ?

Looking forward to hear from you fellas ...


Xen-devel mailing list

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