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

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

Other question I had (and never asked so far) was if we have multiple guest 
domainname put in xendomains param in rc.conf, I assume the order of creating 
them is as specified in the param. Does it also guarantee that a given VM is up 
and running before next VM is going to be created. I know that the definition 
of "up and running" is subject to user interpretation. What I want to find out 
is if there's any way to serialize the VM creation and have hook which checks 
(using xm commands) if the given VM has reached a particular state before going 
to next VM.

I could think of two ways to do that. Pl let me know which one I should go with 
or if you have any better alternative.
1) Put hooks in xendomains script itself to check if given VM is active. Put 
sleep to wait if required.
2) Get rid off the auto-creation of VM. That is, xendomains in rc.conf is 
empty. Have a custom script to be called during init (after xend/xenbackend of 
course) that creates the domains (using xm create) serially and makes sure one 
is up before next is created.

Thanks,
Kalpesh

-----Original Message-----
From: Kalpesh Zinjuwadia 
Sent: Wednesday, August 25, 2010 4:09 PM
To: 'Manuel Bouyer'
Cc: port-xen%netbsd.org@localhost
Subject: RE: Problem with auto-starting DomU on NetBSD5.0.2 running Xen3.3 - 
SOLVED

Looks like auto_ifconfig was set to NO in rc.conf, due to which the interfaces 
were not created in /etc/rc.d/network script. Hence, xendomains complained 
about not able to connect the vif to bridge. I still don't know how the bridge 
got created later on.

Once, I set auto_ifconfig to YES, the bridge was created and xen had no problem 
creating the guest domain.

Thanks Manuel for helping me narrow down the issue.

Kalpesh

-----Original Message-----
From: Manuel Bouyer [mailto:bouyer%antioche.eu.org@localhost] 
Sent: Wednesday, August 25, 2010 2:36 PM
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 02:06:27PM -0700, Kalpesh Zinjuwadia wrote:
> Here you go...
> 

looks good, xen is started near the end.
Next thing would be to boot single user and check that
/etc/rc.d/network start
does indeed create the bridge.

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