On Wed, 12 Sep 2007 06:09:08 am Manuel Bouyer wrote:
> On Tue, Sep 11, 2007 at 04:04:20PM -0400, Thor Lancelot Simon wrote:
> > > didn't return anything either. I can't explain why xm is looking for a
> > > signal.py on your system.
> >
> > It might be error-handling code and not the actual source of the problem.
> > Scrolling up the ktrace output a bit I find:
> >
> >    165      1 python2.4 CALL  connect(3,0x839d428,0x1b)
> >    165      1 python2.4 NAMI  "/var/run/xend/xmlrpc.sock"
> >    165      1 python2.4 RET   connect -1 errno 2 No such file or
> > directory
> >
> > This looks more serious.  ps shows:
>
> Yes, this is probably the real cause
>
> > root     102  0.0  1.2 6672  3252 ?     I     1:37PM 0:00.00 /usr/pk    0
> >  102 1  5172  10  0 6672  3252 wait     I    ?     0:00.00
> > /usr/pkg/bin/python2.4 /usr/pkg/sbin/xend start root     103  0.0  2.6
> > 7072  6792 ?     Ia    1:37PM 0:03.95 /usr/pk    0  103 102     0   2  0
> > 7072  6792 netcon   Ia   ?     0:03.95 /usr/pkg/bin/python2.4
> > /usr/pkg/sbin/xend start
> >
> > And indeed there is no /var/run/xend/xmlrpc.sock, though there is in fact
> > a /var/run/xend.
>
> Did you redo a MAKEDEV xen in /dev/ ?
> Do you have /kern mounted ?

Was there a pullup for the xen devices? I seem to remember there was a device 
missing.

Sarton