[Xen-devel] extremely long xend startup time causing /etc/init.d/xendomains not to run?

[Sean Dague <sean@xxxxxxxxx>]

I've started to notice the following issue, and would like to see if anyone
else has seen it before digging too deep.

When rebooting a xen system that has auto starting domains, they mostly
don't start.

On one system that tries to start 5 DomU instances, it appears only the last
one (alphabetically) ends up starting.  On the system with only 2 DomU
instances, nothing starts.  Neither of these are very speedy machines (700 &
800 Mhz respectively), so a timing problem with /etc/init.d/xend starting is
probably exacerbated in this environment.

Sanity confirmation on this would be really useful, so if anyone else has
seen this please also post back. :)

        -Sean

-- 
__________________________________________________________________

Sean Dague                                       Mid-Hudson Valley
sean at dague dot net                            Linux Users Group
http://dague.net                                 http://mhvlug.org

There is no silver bullet.  Plus, werewolves make better neighbors
than zombies, and they tend to keep the vampire population down.
__________________________________________________________________

Attachment: pgp2XFclEdL8a.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel