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

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Tue, Aug 24, 2010 at 05:26:00PM -0700, Kalpesh Zinjuwadia wrote:
> Hi all:
> 
> I can start domU manually; however, I can't automatically start domU by 
> putting the domU name in xendomains variable in /etc/rc.conf. I think the 
> problem is with associating vif with bridge. I've put the required info below 
> and greatly appreciate any help to resolve this issue. Let me know if more 
> info is needed.
> 
> Thanks,
> Kalpesh
> 
> /etc/rc.conf file snippet:
> . . .
> xenbackendd=YES
> xend=YES
> xendomains="nbsd03"
> 
> On dom0 console I get following (I had to note down the error manually as 
> copy-paste was not possible for this)
> 
> Xbd backend attach device vnd0d for domain1 Failed to read 
> /local/domain/0/backend/console/1/0/script (no such file or directory)
> 
> Error: device 0(vif) could not be connected. Hotplug scripts not working.
> 
> Starting local daemons
> 
> 
> DomU Config File:
> #  -*- mode: python; -*-
> kernel = "/netbsd-XEN3_DOMU"
> memory = 160
> name = "nbsd03"
> ip = "10.11.204.184"
> netmask = "255.255.255.0"
> gateway = "10.11.204.254"
> vif = [ 'bridge=bridge1' ]
> disk = [ 'file:/dsk/nbsd03/nbsd03.img,0x01,w' ]
> 
> bridge1 is created and below is the ifconfig output for it.
> 
> netbsdjasper# ifconfig bridge1
> bridge1: flags=41<UP,RUNNING> mtu 1500
> [...]
> xenbackendd.log
> brconfig: unable to get interface flags: Device not configured

How is the bridge interface created at boot ?
/etc/ifconfig.bridge1 ?

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