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: fedora-xen-bounces@xxxxxxxxxx [mailto:fedora-xen-bounces@xxxxxxxxxx] On Behalf Of Richard W.M. Jones Sent: Tuesday, March 04, 2008 06:52 To: Kanwar Ranbir Sandhu Cc: fedora-xen@xxxxxxxxxx Subject: Re: 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. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
