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-users] Re: Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds,

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors
From: "Allen Brooker (AllenJB)" <allen@xxxxxxxxxxxxx>
Date: Sat, 03 Feb 2007 13:22:12 +0000
Delivery-date: Sat, 03 Feb 2007 05:41:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <5bb00b3f0702030442nfe0d98dncaeb4ed667d45fb1@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <45C46034.7000502@xxxxxxxxxxxxx> <5bb00b3f0702030442nfe0d98dncaeb4ed667d45fb1@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv: Gecko/20070102 Thunderbird/ Mnenhy/
Henning Sprang wrote:
On 2/3/07, Allen Brooker <allen@xxxxxxxxxxxxx> wrote:
Below is the contents of /var/log/xend.log for the creation (and crash
and destruction) of the domU.

As far as my experience goes, xend.log is almost always useless to
help with finding problems (as long as you're nmot very deep into the
details of the python code).
What does xend-debug.log and xen-hotplug.log say?


Previously these files had been giving me no messages at all (so I had kind of stopped checking them), but...

It seems that my last set of changes actually got me further than I thought - The last time I changed my domU kernel (which was to use the config file from the xen livecd) I forgot to change the domU's config file (in /etc/xen) to point to the new kernel. I've now corrected this and for the first time on this machine I'm getting kernel output from the domU - granted it's not about to mount the root filesystem, but I suspect I can sort this out from here.

It's still both annoying and weird that previously I've been getting no kernel output at all and no messages to tell me why the domU has crashed after 0.1 seconds. If this happens again, is there anything I can do to try to find out what's going wrong?


Xen-users mailing list