domU auto start order

[Ranbir]

Hi All,

Is it possible to auto start domU's listed in /etc/xen/auto in a
particular order?  I imagine it is, but my reading comprehension or my
searching skills suck, because I can't find anything about this.

Thanks,

Ranbir

[Barrow H Kwan]

this is how I did.    files in /etc/xen/auto is just a symbolic link to 
/etc/xen.   eg /etc/xen/myvm01, /etc/xen/myvm02, /etc/xen/myvm03, to start 
the VM in the order of 02 -> 01 -> 03, I create a link under /etc/xen/auto

/etc/xen/auto/1myvm02 -> /etc/xen/myvm02
/etc/xen/auto/2myvm01 -> /etc/xen/myvm01
/etc/xen/auto/3myvm03 -> /etc/xen/myvm03

I think there is a better way to do it...

=================
Barrow Kwan
ThoughtWorks, Inc.

New from ThoughtWorks: Mingle, an Agile project management application.
Mingle. Project Intelligence. Powerfully Simple.
More at http://studios.thoughtworks.com

Kanwar Ranbir Sandhu  
Sent by: [e-mail]
02/26/08 06:15 PM

To
[e-mail]
cc

Subject
[Fedora-xen] domU auto start order

Hi All,

Is it possible to auto start domU's listed in /etc/xen/auto in a
particular order?  I imagine it is, but my reading comprehension or my
searching skills suck, because I can't find anything about this.

Thanks,

Ranbir

[Richard W.M. Jones]

On Tue, Feb 26, 2008 at 09:15:51PM -0500, Kanwar Ranbir Sandhu wrote:
> Is it possible to auto start domU's listed in /etc/xen/auto in a
> particular order?  I imagine it is, but my reading comprehension or my
> searching skills suck, because I can't find anything about this.

Yes if you order the names of the start-up scripts alphabetically.

However note that this probably doesn't do what you think you want it
to do: There is no general way to say "don't start domain Y until
domain X is up and running", because basically there is no good
definition for "up and running".  eg. Should it mean that the kernel
is up, or it's reached the login prompt, or all services on X are
listening ...?  You can't easily test for these conditions, so just
ordering the boots only has a minimal benefit.

Rich.

[Dustin Henning]

I don't know if the virt-manager created domains are affected by
this, but there is a setting in one of the xend configs that allows you to
set how long to wait before starting each domain, this would allow you to at
least have one domain close to (if not fully) loaded before the next starts.
However, I don't know if this is the reason Kanwar wants to change the boot
order anyway.  Additionally, this setting extends the Dom0 boot by the
number of domains multiplied by the length of the delay.
    Dustin

-----Original Message-----
From: [e-mail] [mailto:[e-mail]]
On Behalf Of Richard W.M. Jones
Sent: Tuesday, March 04, 2008 06:52
To: Kanwar Ranbir Sandhu
Cc: [e-mail]
Subject: Re: [Fedora-xen] domU auto start order

On Tue, Feb 26, 2008 at 09:15:51PM -0500, Kanwar Ranbir Sandhu wrote:
> Is it possible to auto start domU's listed in /etc/xen/auto in a
> particular order?  I imagine it is, but my reading comprehension or my
> searching skills suck, because I can't find anything about this.

Yes if you order the names of the start-up scripts alphabetically.

However note that this probably doesn't do what you think you want it
to do: There is no general way to say "don't start domain Y until
domain X is up and running", because basically there is no good
definition for "up and running".  eg. Should it mean that the kernel
is up, or it's reached the login prompt, or all services on X are
listening ...?  You can't easily test for these conditions, so just
ordering the boots only has a minimal benefit.

Rich.