XEN3 DOMU troubles

I'm having similiar issues to what Steve had reported in his
thread
(http://mail-index.netbsd.org/port-xen/2006/10/08/0004.
html) except
even after I include "vif = [ 'bridge=bridge0' ]"
in my config file, I
still get the "Error: Device 0 (vif) could not be
connected.  Hotplut
scripts not working." error.

brconfig -a shows the bridge0 interface is up and running:
bridge0: flags=41<UP,RUNNING>
            Configuration:
                        priority 32768 hellotime 2 fwddelay
15 maxage 20
                        ipfilter disabled flags 0x0
            Interfaces:
                        ex0 flags=3<LEARNING,DISCOVER>
                                    port 1 priority 128
            Address cache (max cache: 100, timeout: 1200):
                         00:0a:95:d6:1c:8a ex0 4294967143
flags=0<>

Here is my guest domain file contents:
name = "nbsdu"
kernel = "/home/msun/netbsd-INSTALL_XEN3_DOMU"
memory = 96
vif = [ 'bridge=bridge0' ]
disk = [ 'file:/home/msun/nbsd-disk,0x01,w' ]
root = "/dev/wd0a"

I'm running off the binaries from
"NetBSD-daily/HEAD/200610250000Z/",
anybody have any ideas what's going on?

Thanks,
Mike

On Sat, Nov 04, 2006 at 11:36:19PM -0500, Mike Sun wrote:
> I'm having similiar issues to what Steve had reported
in his thread
> (http://mail-index.netbsd.org/port-xen/2006/10/08/0004.
html) except
> even after I include "vif = [ 'bridge=bridge0'
]" in my config file, I
> still get the "Error: Device 0 (vif) could not be
connected.  Hotplut
> scripts not working." error.
> 
> brconfig -a shows the bridge0 interface is up and
running:
> bridge0: flags=41<UP,RUNNING>
>            Configuration:
>                        priority 32768 hellotime 2
fwddelay 15 maxage 20
>                        ipfilter disabled flags 0x0
>            Interfaces:
>                        ex0
flags=3<LEARNING,DISCOVER>
>                                    port 1 priority 128
>            Address cache (max cache: 100, timeout:
1200):
>                         00:0a:95:d6:1c:8a ex0
4294967143 flags=0<>
> 
> Here is my guest domain file contents:
> name = "nbsdu"
> kernel =
"/home/msun/netbsd-INSTALL_XEN3_DOMU"
> memory = 96
> vif = [ 'bridge=bridge0' ]
> disk = [ 'file:/home/msun/nbsd-disk,0x01,w' ]
> root = "/dev/wd0a"
> 
> I'm running off the binaries from
"NetBSD-daily/HEAD/200610250000Z/",
> anybody have any ideas what's going on?

Look at messages from xenbackendd in /var/log/messages, it
may give a hint
at what's going wrong. You may also want to add some debug
output (redirected
to a file) to /usr/pkg/etc/xen/scripts/* 

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

On Sun, Nov 05, 2006 at 08:26:13PM +0100, Manuel Bouyer
wrote:
> Look at messages from xenbackendd in /var/log/messages,
it may give a hint
> at what's going wrong. You may also want to add some
debug output (redirected
> to a file) to /usr/pkg/etc/xen/scripts/* 

I had the same problem with very few clues about what was
wrong. 

Eventually I discovered I had to start xend *then*
xenbackendd, and
now I have a windows installer running in a hvm domain.

--
Dan.

On Thu, Nov 09, 2006 at 05:23:54PM +1100, Daniel Carosone
wrote:
> [...]
> Eventually I discovered I had to start xend *then*
xenbackendd, and

Sure. But the rc.d xenbackendd script depends on xend, isn't
it ?

-- 
Manuel Bouyer, LIP6, Universite Paris VI.          
Manuel.Bouyerlip6.fr
     NetBSD: 26 ans d'experience feront toujours la
difference
--

On Thu, Nov 09, 2006 at 08:43:13AM +0100, Manuel Bouyer
wrote:
> On Thu, Nov 09, 2006 at 05:23:54PM +1100, Daniel
Carosone wrote:
> > [...]
> > Eventually I discovered I had to start xend *then*
xenbackendd, and
> 
> Sure. But the rc.d xenbackendd script depends on xend,
isn't it ?

probably, but I was being lazy and just
"forcestart"ing them directly
from /usr/pkg/mumble/rc.d/mumble/example/mumble, because
they don't
get installed anywhere rcorder will find them.

--
Dan.

On Thu, Nov 09, 2006 at 06:50:56PM +1100, Daniel Carosone
wrote:
> On Thu, Nov 09, 2006 at 08:43:13AM +0100, Manuel Bouyer
wrote:
> > Sure. But the rc.d xenbackendd script depends on
xend, isn't it ?
>
> probably, but I was being lazy and just
"forcestart"ing them directly
> from /usr/pkg/mumble/rc.d/mumble/example/mumble,
because they don't get
> installed anywhere rcorder will find them.

You should use "onestart" instead of
"forcestart" for such things.
"onestart" will not ignore any startup checks, it
will only assume
variable=YES in rc.conf.

However rc dependencies are checked by rcorder so it won't
make a
difference in this case. :-(

	Geert

On Thu, Nov 09, 2006 at 06:50:56PM +1100, Daniel Carosone
wrote:
> On Thu, Nov 09, 2006 at 08:43:13AM +0100, Manuel Bouyer
wrote:
> > On Thu, Nov 09, 2006 at 05:23:54PM +1100, Daniel
Carosone wrote:
> > > [...]
> > > Eventually I discovered I had to start xend
*then* xenbackendd, and
> > 
> > Sure. But the rc.d xenbackendd script depends on
xend, isn't it ?
> 
> probably, but I was being lazy and just
"forcestart"ing them directly
> from /usr/pkg/mumble/rc.d/mumble/example/mumble,
because they don't
> get installed anywhere rcorder will find them.

I have

# install rc.d scripts in-place
PKG_RCD_SCRIPTS=yes

in my /etc/mk.conf, and it DTRT.

Regards,
Alistair