[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen on Dell PowerEdge 2500 - Crashes after 0.1 seconds, no visible errors

  • To: "Allen Brooker" <allen@xxxxxxxxxxxxx>
  • From: "Henning Sprang" <henning_sprang@xxxxxx>
  • Date: Sat, 3 Feb 2007 13:42:55 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 03 Feb 2007 04:42:49 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=KSKiXRdqCqObV4WStZ7EZPwpMVWiOyGSfNKWjQqhjSZnwGHPw9FQntJGSdzrEVRj+tpBB1wgpD7kNqGQJL/CUn9kLl9jeSh6MGYs/6Jjb5Ze/f09td2Ub3+NtCu28RNPLcD2CguxnMwzUiSEsFsDrKNn7NreRiO1iqwjD2BD+N0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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?


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.