Particular domU boots before anyother domU on the same host

[Asrai khn]

Hi,

I am wondering how to make sure that a particular domU boots before anyother
domU on the same host. For example this particular domU providing some samba
shares to other domU. Apparently if the dom0 reboots we have to 'mount' the
shares  on  some domU(s) which boots before  domU which providing these
shares.


Any help in this regards will be highly appreciated.

Thanks. Askar

[Daniel P. Berrange]

On Mon, Feb 19, 2007 at 04:52:31PM +0500, Asrai khn wrote:
>  Hi,
>  
>  I am wondering how to make sure that a particular domU boots before anyother
>  domU on the same host. For example this particular domU providing some samba
>  shares to other domU. Apparently if the dom0 reboots we have to 'mount' the
>  shares  on  some domU(s) which boots before  domU which providing these
>  shares. 
The xendomains  init script which is responsible for starting domains at
boot time is pretty simplisitic. It simply does a wildcard on the files in
/etc/xen/auto/*  or saved VMs in /var/lib/xen/save/* so domains will get
started in alphabetical order based on their name. You shouldn't rely on
this  behaviour though, because the way domains are autostarted has changed
in Xen 3.0.4  which will be in Fedora 7 and I can't guarentee the startup
ordering will be the same

So if you want to ensure domains start ina  particular order, I'd not use
the xendomains script at all. Instead just put a bunch of 'xm create'
statements in /etc/rc.d/rc.local to follow your desired ordering exactly.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  [phone] -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|

[Asrai khn]

Hi  Dan

On 2/19/07, Daniel P. Berrange <berrange(a)redhat.com&gt; wrote:
>  The xendomains  init script which is responsible for starting domains at
>  boot time is pretty simplisitic. It simply does a wildcard on the files in
>  /etc/xen/auto/*  or saved VMs in /var/lib/xen/save/* so domains will get
>  started in alphabetical order based on their name. You shouldn't rely on
>  this  behaviour though, because the way domains are autostarted has
>  changed
>  in Xen 3.0.4  which will be in Fedora 7 and I can't guarentee the startup
>  ordering will be the same
>
>  So if you want to ensure domains start ina  particular order, I'd not use
>  the xendomains script at all. Instead just put a bunch of 'xm create'
>  statements in /etc/rc.d/rc.local to follow your desired ordering exactly. 

Alright then we must go for /etc/rc.d/rc.local approach, however I wonders
why xen uses the alphabetic approach when starts domains its kinda weird :)

Thanks. Askar

Regards,
>  Dan.
>  --
>  |=- Red Hat, Engineering, Emerging Technologies, Boston.  [phone]
>  -=|
>  |=-           Perl modules: http://search.cpan.org/~danberr/
>                -=|
>  |=-               Projects: http://freshmeat.net/~danielpb/
>  -=|
>  |=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B
>  9505  -=|
>

[Asrai khn]

On 2/19/07, Daniel P. Berrange <berrange(a)redhat.com&gt; wrote:
>  So if you want to ensure domains start ina  particular order, I'd not use
>  the xendomains script at all. Instead just put a bunch of 'xm create'
>  statements in /etc/rc.d/rc.local to follow your desired ordering exactly. 

By this you mean to stop 'xendomains' service to run when system (dom0)
boots, and putting 'xm create blah.cfg' in rc.local right?

Thanks. Askar