From: Niraj Tolia <ntolia@gmail.com>
To: Ian Pratt <ian.pratt@cl.cam.ac.uk>
Cc: James Harper <jamesh@bendigoit.com.au>,
Keir Fraser <keir.fraser@cl.cam.ac.uk>,
"xen-devel@lists.sourceforge.net"
<xen-devel@lists.sourceforge.net>
Subject: Re: Re: almost working
Date: Fri, 2 Jul 2004 17:39:17 +0100 [thread overview]
Message-ID: <7e45e2ac0407020939eb8b05b@mail.gmail.com> (raw)
In-Reply-To: <E1BgPr3-0003yk-00@mta1.cl.cam.ac.uk>
> I suspect adding devfs support wouldn't be too hard, but its
> probably not high on the list of priorities for us. Do any
> common distros use it by default?
>
> > having booted my new domain, 'xm list' in dom0 hung for ages with 100% cpu time until I hit ctrl-C. trying it again worked fine though.
>
> 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.
Niraj
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-07-02 16:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 5:19 can't mount root... devfs??? James Harper
2004-06-30 5:54 ` Ian Pratt
2004-06-30 6:43 ` Keir Fraser
2004-06-30 9:38 ` James Harper
2004-06-30 9:57 ` Keir Fraser
2004-06-30 9:59 ` Ian Pratt
2004-06-30 23:14 ` Ian Pratt
2004-07-02 2:58 ` James Harper
2004-07-02 7:09 ` Keir Fraser
2004-07-02 7:32 ` Ian Pratt
2004-07-02 13:52 ` almost working James Harper
2004-07-02 15:21 ` Ian Pratt
2004-07-02 16:39 ` Niraj Tolia [this message]
2004-07-02 17:04 ` Ian Pratt
2004-07-06 16:11 ` Keir Fraser
2004-07-06 22:34 ` Jody Belka
2004-07-06 22:58 ` Ian Pratt
2004-07-07 7:10 ` Keir Fraser
2004-07-07 14:56 ` No module named xen.xm error Rune Johan Andresen
2004-07-07 15:06 ` Tom Wilkie
2004-07-07 15:24 ` Rune Johan Andresen
2004-07-07 15:09 ` Ian Pratt
2004-07-09 6:19 ` Re: almost working Jody Belka
2004-07-09 9:35 ` James Harper
2004-07-09 9:54 ` Jody Belka
2004-07-09 9:48 ` Keir Fraser
2004-07-09 11:19 ` Ian Pratt
2004-07-09 11:53 ` Jody Belka
2004-07-13 15:00 ` Niraj Tolia
2004-07-13 15:13 ` Ian Pratt
2004-07-13 15:27 ` Keir Fraser
2004-07-14 1:37 ` James Harper
2004-07-03 10:24 ` James Harper
2004-07-03 11:36 ` Keir Fraser
2004-07-04 12:37 ` xen
2004-07-06 14:53 ` ron minnich
2004-07-04 14:41 ` Jody Belka
2004-06-30 14:16 ` can't mount root... devfs??? Mark Williamson
2004-06-30 14:19 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e45e2ac0407020939eb8b05b@mail.gmail.com \
--to=ntolia@gmail.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=jamesh@bendigoit.com.au \
--cc=keir.fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.