Arun Khan wrote: > Is there a way in virt-manager / libvirtd (or hand edit some file) to > specify the boot order of the VMs that are configured as "Start at > boot time"
Normally independent systems have no coordination on boot ordering. A virtual machine is simulating a real machine and therefore generally also does not have any coordination between booting the independent systems. > Among the VMs one is a DB server and a few app servers that connect > to the DB server. > ... > Similar to the init script naming convention in /etc/rc?.d (S00, S99 > etc.), I have named the VMs like 00-<VM_name>, 01-<VM_name> etc. > > The DB server name starting with a 00 prefix and the app servers with > a 99 prefix, with the expectation that the DB server will boot first > and be ready for connection requests coming from the app servers when > they boot up. Additionally, in the app servers I have added up to 45 > sec time out in grub. But most of these will boot up in parallel. Just specifying the order would be insufficient. One would actually need to wait for the other. > When the host system boots up, I find the applications (in the app > server) complaining about their respective connections to the backend > database (to the DB server). I have to restart the db connections > manually and then the applications come up fine. IMNHO this means that the systems that are dependent upon the other system are not configured properly. If those were real hardware and not virtual hardware then you would have this exact same problem. How would it be handled if those were real machines instead of virtual machines? Instead of trying to do boot them up in a particular order I think it would be much better to fix the underlying problems. Fix their configuration so that if they need an external resource that they will handle booting with that external resources offline. Bob
signature.asc
Description: Digital signature
