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

On Tue, 06 Jul 2004 17:11:04 +0100, Keir Fraser
<keir.fraser@xxxxxxxxxxxx> wrote:
> > > Not good. I think xend is getting more robust over time.
> >
> > 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.
> I think many people had been seeing problems of this ilk, so you will
> probably be delighted to hear that these bugs have been squashed by
> today's checkins.
> It was a combination of a simple stupid bug in the device-driver code,
> coupled with faulty error handling in xend.

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

BTW what has the start_trace option for xend been replaced by?


>  -- Keir

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