RE: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3

[Kalpesh Zinjuwadia <kzinjuwadia%force10networks.com@localhost>]

I added the required commands in vif-bridge; however, I don't see the output 
anywhere (checked xenbackendd.log, xend.log, xend-debug.log, console). Don't 
know where it got logged. Then I added it to xendomains script right under 
xendomains_start() and saw output during bootup. I DIDN'T see bridge1 in 
ifconfig -a. ifconfig bridge1 failed too with device not configured error msg.

BTW, in my xend-config.sxp, I have default config for network-script and 
vif-script. The comment says that by default the bridge name is xenbr0. 
However, I'm using bridge1 in vif param in domU config file. I added 
bridge=bridge1 in the network-script below and xenbackendd core dumped :(

Does this give any leads?

xend-config.sxp:
. . .
(network-script network-bridge)
(vif-script vif-bridge)
. . .

Dmesg output showing xenbackendd cored:
. . .
pid 265 (xenbackendd), uid 0: exited on signal 11 (core dumped)
pid 263 (xenbackendd), uid 0: exited on signal 11 (core dumped)
pid 284 (xenbackendd), uid 0: exited on signal 11 (core dumped)
xbd backend: detach device vnd0d for domain 1
xvif1.0: disconnecting
pid 272 (xenbackendd), uid 0: exited on signal 11 (core dumped)

Thanks,
Kalpesh

-----Original Message-----
From: Manuel Bouyer [mailto:bouyer%antioche.eu.org@localhost] 
Sent: Wednesday, August 25, 2010 10:22 AM
To: Kalpesh Zinjuwadia
Cc: port-xen%netbsd.org@localhost
Subject: Re: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3

On Wed, Aug 25, 2010 at 10:13:26AM -0700, Kalpesh Zinjuwadia wrote:
> I fixed ifconfig.bridge1 file. However, still get same error. On console I 
> see a new log which I didn't see earlier. Xen-debug.log says brctl not found. 
> Can this be the root cause?

No, I get it on occasion too. It's some linux leftover in a script.
I have no more idea what's going on then. If after boot the bridge
exists and is properly configured, I can't see why the xen tools would
find it after boot, but not at boot time ...

Maybe in /usr/pkg/etc/xen/scripts/vif-bridge, you could add
ifconfig -a
brconfig -a
echo  xbridge $xbridge
in the 2) case, to see what's going on ? output of these commands should
end in the xenbackendd.log

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