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


Re: [Xen-devel] Re: almost working

To: Niraj Tolia <ntolia@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: almost working
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 13 Jul 2004 16:13:20 +0100
Cc: Keir Fraser <keir.fraser@xxxxxxxxxxxx>, Ian Pratt <ian.pratt@xxxxxxxxxxxx>, James Harper <jamesh@xxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Tue, 13 Jul 2004 16:16:39 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 13 Jul 2004 16:00:11 BST." <7e45e2ac0407130800610e9a06@xxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > > I have seen a number of ''heisenbugs" with xend. They especially occur
> > > when I stop xend and start it again. Every now and then a 'xend start'
> > > does nothing and sends no output to console. Commands such as 'xm
> > > list' will give a 'Connection refused' error. A 'xend stop' followed
> > > by a 'xend start' usually fixes this but there have been a few times
> > > where I have had to repeat the cycle a couple of times.
> > >
> > > Also, sometimes after a reboot, a domain creation just fails and the
> > > 'xm create' command does not return. There are no error messages from
> > > xend. Even though I suspect that things are hosed at this point in
> > > time, a 'xend stop' works. However xend will not startup again and
> > > gives a 'IOError: [Errno 16] Device or resource busy' error. The
> > > problem cannot be reproduced as the  same create command works after
> > > another reboot.

> Just FYI, I still see most of the above bugs. Running the latest and greatest.

I've actually found that xend has been very stable for me for the
last few days. How are other people finding it?

I think there's real merit in cleaning out old installations
before doing a new install e.g.:

 rm -rf "/etc/xen /usr/lib/python2.2/site-packages/xen* /usr/lib/libxc* 

If you still get problems, please post any output.

I know of two outstanding Xen bugs, both of which Keir
understands and is about to vanquish:

 * instability after shutting a domain down on a CPU other than CPU 0.

 * dom0 oops when hitting local block devices hard from within
dom0 while doing block io from other domains.

Let's get these two fixed then see where we are.


This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
Xen-devel mailing list