From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Kaczmarek Subject: Re: (file=event_channel.c, line=137) EVTCHNOP failure: domain 0, error-22, line 137 Date: Sat, 08 Oct 2005 21:50:31 -0400 Message-ID: <1128822631.20180.16.camel@pluto.linsolutions.com> References: <1128788203.6347.18.camel@pluto.linsolutions.com> <8f7fb4981d43c56c9ac8c42c8fbb60b5@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7BIT Return-path: In-reply-to: <8f7fb4981d43c56c9ac8c42c8fbb60b5@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Sat, 2005-10-08 at 18:09 +0100, Keir Fraser wrote: > On 8 Oct 2005, at 17:16, Ted Kaczmarek wrote: > > > > > I hit bug #264 preceding this. > > > > Happens after stoping xend and then starting. > > > > Should I create a new bug or just add to #264. > > It's a different bug. I think my event-channel cleanups have exposed > some problems with xend's state restoration when it is stopped/started. > Will look into it next week... > > -- Keir > I have reproduced this on another box as well, just try to bring up some domU's without a valid root filesystems and try restarting xend. Regards, Ted