On Thu, Apr 14, 2011 at 02:32:36PM -0600, Eric Blake wrote: > Without more code on the libvirt front, I think you're stuck renaming > the guests to enforce naming order (assuming that libvirt even goes by > sorted name order, as opposed to readdir() order where you have no control). I solved this problem in my own application, a layer above libvirt. I simply make all of my domains non-persistent. When the node reboots, nothing starts up. My application detects that domains that should be running aren't and defines/starts them. It's easy at that point to start them up in whatever order I want and give whatever delay between startups. Even if you don't have some overarching managing application (like, if you're managing one node instead of hundreds), you could easily do something similar with a cron job. --Igor
Attachment:
signature.asc
Description: Digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list