Unable to start a Xen3 DOMU

I have a Xen3 DOM0 kernel running on a fairly recent
-current (I'm not
certain of the exact date, but it's 4.99.3, from within the
last week, I
believe -- I'm trying to run an absolutely up-to-date one,
but I haven't
been able to build -current for the last day or so....)  I'm
trying to run
a Xen3 DOMU now, but I can't get it to fire up.  When I do
'xm create -c',
I get

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

Tracing vif-bridge shows this:

 +
PATH=/bin:/usr/bin:/usr/pkg/bin:/sbin:/usr/sbin:/usr/pkg/sbi
n
+ export PATH
+ xpath=/local/domain/0/backend/vif/5/0
+ xstatus=2
+ xenstore-read /local/domain/0/backend/vif/5/0/bridge
xenstore-read: couldn't read path
/local/domain/0/backend/vif/5/0/bridge
+ xbridge=

I have xend and xenbackendd running (via rc.d); I haven't
yet started
xendomains, since its purpose seems to be to start/stop
DOMUs and I don't
have any yet.

(Btw, I've built a NetBSD DOMU image by manually untarring
install sets in
the VND disk and doing other useful things, such as creating
its /dev,
editing its rc.conf, etc -- that all seemed easier than
running sysinst on
it.)

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

On Sun, Oct 08, 2006 at 12:45:05PM -0400, Steven M. Bellovin
wrote:
> I have a Xen3 DOM0 kernel running on a fairly recent
-current (I'm not
> certain of the exact date, but it's 4.99.3, from within
the last week, I
> believe -- I'm trying to run an absolutely up-to-date
one, but I haven't
> been able to build -current for the last day or so....)
 I'm trying to run
> a Xen3 DOMU now, but I can't get it to fire up.  When I
do 'xm create -c',
> I get
> 
> 	Error: Device 0 (vif) could not be connected. Hotplug
scripts not
> working.
> 
> Tracing vif-bridge shows this:
> 
>  +
PATH=/bin:/usr/bin:/usr/pkg/bin:/sbin:/usr/sbin:/usr/pkg/sbi
n
> + export PATH
> + xpath=/local/domain/0/backend/vif/5/0
> + xstatus=2
> + xenstore-read /local/domain/0/backend/vif/5/0/bridge
> xenstore-read: couldn't read path
/local/domain/0/backend/vif/5/0/bridge
> + xbridge=
> 
> I have xend and xenbackendd running (via rc.d); I
haven't yet started
> xendomains, since its purpose seems to be to start/stop
DOMUs and I don't
> have any yet.

Can you show your config file ? I guess you don't have a
'bridge=xxx' 
entry for your vif ...
If this is intended, you can change vif-bridge to not try to
read
/local/domain/0/backend/vif/5/0/bridge and configure the vif
with a
bridge.

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

On Sun, Oct 08, 2006 at 12:45:05PM -0400, Steven M. Bellovin
wrote:
> I have a Xen3 DOM0 kernel running on a fairly recent
-current (I'm not
> certain of the exact date, but it's 4.99.3, from within
the last week, I
> believe -- I'm trying to run an absolutely up-to-date
one, but I haven't
> been able to build -current for the last day or so....)
 I'm trying to run
> a Xen3 DOMU now, but I can't get it to fire up.  When I
do 'xm create -c',
> I get
> 
> 	Error: Device 0 (vif) could not be connected. Hotplug
scripts not
> working.
> 
> Tracing vif-bridge shows this:
> 
>  +
PATH=/bin:/usr/bin:/usr/pkg/bin:/sbin:/usr/sbin:/usr/pkg/sbi
n
> + export PATH
> + xpath=/local/domain/0/backend/vif/5/0
> + xstatus=2
> + xenstore-read /local/domain/0/backend/vif/5/0/bridge
> xenstore-read: couldn't read path
/local/domain/0/backend/vif/5/0/bridge
> + xbridge=
> 
> I have xend and xenbackendd running (via rc.d); I
haven't yet started
> xendomains, since its purpose seems to be to start/stop
DOMUs and I don't
> have any yet.

Can you show your config file ? I guess you don't have a
'bridge=xxx' 
entry for your vif ...
If this is intended, you can change vif-bridge to not try to
read
/local/domain/0/backend/vif/5/0/bridge and configure the vif
with a
bridge.

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

On Sun, 8 Oct 2006 19:38:19 +0200, Manuel Bouyer
<bouyerantioche.eu.org>
wrote:

> 
> Can you show your config file ? I guess you don't have
a 'bridge=xxx' 
> entry for your vif ...
> If this is intended, you can change vif-bridge to not
try to read
> /local/domain/0/backend/vif/5/0/bridge and configure
the vif with a
> bridge.
> 
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' ]

but that didn't do it; I got

	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.)

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 h
ttp://wiki.onetbsd.org/index.php/xen3-installen

I've attached the config file; it's only slightly modified
from the
example given.


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

On Sun, 8 Oct 2006 19:38:19 +0200, Manuel Bouyer
<bouyerantioche.eu.org>
wrote:

> 
> Can you show your config file ? I guess you don't have
a 'bridge=xxx' 
> entry for your vif ...
> If this is intended, you can change vif-bridge to not
try to read
> /local/domain/0/backend/vif/5/0/bridge and configure
the vif with a
> bridge.
> 
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' ]

but that didn't do it; I got

	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.)

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 h
ttp://wiki.onetbsd.org/index.php/xen3-installen

I've attached the config file; it's only slightly modified
from the
example given.


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

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.

> 
> 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 h
ttp://wiki.onetbsd.org/index.php/xen3-installen

It's the xenstore. See the xenstore-* commands so list
entries and
get values.

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

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.

> 
> 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 h
ttp://wiki.onetbsd.org/index.php/xen3-installen

It's the xenstore. See the xenstore-* commands so list
entries and
get values.

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

On Sun, 8 Oct 2006 20:01:16 +0200, Manuel Bouyer
<bouyerantioche.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 h
ttp://wiki.onetbsd.org/index.php/xen3-installen
> 
> 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.columbi
a.edu/~smb

On Sun, Oct 08, 2006 at 02:19:04PM -0400, Steven M. Bellovin
wrote:
> > 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?

Yes, but you have to tell him to what bridge is has to
connect

> 
> 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' ]

Change wd0a with 0x01

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

On Sun, 8 Oct 2006 20:01:16 +0200, Manuel Bouyer
<bouyerantioche.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 h
ttp://wiki.onetbsd.org/index.php/xen3-installen
> 
> 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.columbi
a.edu/~smb