Some guest systems do not come up after reboot despite they are configured to do so

Submitted by yngens on Thu, 04/17/2014 - 03:06

When our Cloudmin system had just several guest KVM systems, they would easily come up after rebooting the main Cloudmin server. However, I don't remmeber exactly when, but with their number growing more than 10 or so, some guest systems do not come up after reboot despite they are configured to do so. Then we have to start them up manually every time. I believe Cloudmin attempts to start up all the guest systems at once and that's when some guest systems fail to pass through the bottleneck. Unfortunately, Cloudmin doesn't try to start failed systems later. So it would be nice if Cloudmin could start only some definite number of gust systems at one instance, take some break, then start another party of guest system, take another break, so on and on till all the guest systems are up.

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Thu, 04/17/2014 - 11:36

Yes, this could be due to too many VMs being started at the same time.

Also, can you check if the VMs that aren't being started are listed in /etc/init.d/cloudmin-kvm on the host system?

Submitted by yngens on Sat, 04/19/2014 - 00:45

I will check on next reboot as currently all the systems are up. But I am pretty sure everything is listed there, because we set all guest systems to auto-start after reboot. I just believe Cloudmin reboot script needs to be modified to start guest systems in several separate groups.

Submitted by JamieCameron on Sat, 04/19/2014 - 16:50

Ok, what I will do in the next release is add a 10s delay between when VMs are started at boot time.

Submitted by Issues on Sat, 05/03/2014 - 16:51

Automatically closed -- issue fixed for 2 weeks with no activity.