On Mon, May 23, 2005 at 09:36:00PM +0200, Juan RP wrote:
> On Mon, 23 May 2005 21:32:27 +0200
> Manuel Bouyer <bouyer@antioche.eu.org> wrote:
> 
> > The only issue I've noticed here is:
> >    601 python2.3 CALL  open(0xbd7da8fd,6,0xbfbfded8)
> >    601 python2.3 NAMI  "/dev/xenevt"
> >    601 python2.3 RET   open -1 errno 2 No such file or directory
> > 
> > It looks like you're missing this device on this system, run 'MAKEDEV
> > xen' in /dev/ and try again.
> 
> [juan@Mandylion][~]> ls -l /dev/xen*
> crw-------  1 root  wheel  143, 0 Apr  5 02:08 /dev/xencons
> crw-------  1 root  wheel  141, 0 Apr  5 02:08 /dev/xenevt
> [juan@Mandylion][~]>
> 
> As I said, it works when using a kernel without those changes.

From where does the "Failed to map domain control interface" you mentionned
comes from ? In the ktrace output you sent, xend never writes this
message. But it does write a traceback with a "No such file or directory" error
to /var/log/xend-debug.log

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--