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] Problem starting xend in latest 3.4 release candidate

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Problem starting xend in latest 3.4 release candidate
From: Simon Horman <horms@xxxxxxxxxxxx>
Date: Wed, 6 May 2009 08:42:10 +1000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "echo@xxxxxxxxxxxx" <echo@xxxxxxxxxxxx>
Delivery-date: Tue, 05 May 2009 15:42:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C625A93D.A0AD%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: <1241494838.5578.6.camel@xxxxxxxxxxxxxxxxxxxxx> <C625A93D.A0AD%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Tue, May 05, 2009 at 08:28:45AM +0100, Keir Fraser wrote:
> On 05/05/2009 04:40, "Tim Post" <echo@xxxxxxxxxxxx> wrote:
> 
> > I'm really, really bewildered. Any help is appreciated. I can't tell if
> > this is due to upgrading, or if some other strange problem has appeared
> > on my system. My Python is not the best :)
> > 
> > Last night, it worked. Today, it doesn't .. and I can't think of
> > anything that happened overnight , especially since the system was shut
> > down.
> 
> Looks like xend has probably tried to persist something and got itself
> confused in the process. Try deleting /var/lib/xen/* before starting xend.

I saw a very similar problem the other day, which was
caused by an empty file in /var/lib/xen/
I never got to the bottom of how the file became empty.

-- 
Simon Horman
  VA Linux Systems Japan K.K. Satellite Lab in Sydney, Australia
  H: www.vergenet.net/~horms/            W: www.valinux.co.jp/en


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

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