On Sun, 8 Oct 2006 20:01:16 +0200, Manuel Bouyer <bouyer@antioche.eu.org>
wrote:

> On Sun, Oct 08, 2006 at 01:57:01PM -0400, Steven M. Bellovin wrote:
> > I don't have a bridge= entry -- I relied on the text that says 
> > 
> > 	You may have one created
> > 	with sensible defaults using an empty vif clause
> > 
> > which is what I have.  What should the line say?  I tried
> > 
> > 	vif = [ '', 'bridge=bridge0' ]
> 
> This would create 2 entries; you should have
> vif = [ 'bridge=bridge0']
> > 
> > 
> > 	Error: Device 0 (vif) could not be connected. Hotplug scripts not
> > working.
> > 
> > (bridge0 was properly created at boot time, and 'brconfig -a' shows that
> > it's there.)
> 
> If you want your domU connected to this bridge you have to specify it;
> it won't do it automagically.

That's what vif-bridge does, right?

Anyway, fixing the config file has gotten me past that point; it's now
failing on 

	Error: Device 0 (vbd) could not be connected. Hotplug scripts not
working.

Tracing scripts/block shows no obvious failures.  I assume that vbd is the
block device; my disk= line is

	disk = [ 'file:/home/xen/haaretz.vnd,wd0a,w' ]

though I suppose I could change it to use a vnd device.
> 
> > 
> > Where does /local/domain... come from?  It's being passed to the
> > vif-bridge script.  It looks like a file name, but I don't have /local on
> > my machine -- should I?  I don't see anything about it in the Cambridge
> > install guide or at http://wiki.onetbsd.org/index.php/xen3-install:xen
> 
> It's the xenstore. See the xenstore-* commands so list entries and
> get values.
> 
Gotcha -- I see mention of that in the Developer's manual.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb