<div dir="ltr">Actually I was using a bash script works like semaphore in before/after_vm_start. As a result that a parallel problem occured: four vms read the same number at the same time, so I abandoned this way.<div>Now I just add a random delay period before vm start, not very well.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/24 Itamar Heim <span dir="ltr"><<a href="mailto:iheim@redhat.com" target="_blank">iheim@redhat.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div>On 05/23/2013 04:23 PM, lofyer wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div>
Can host hooks be used to implement the following policy to avoid "boot<br>
storm"?<br>
<br>
1.count and sort VMs awaiting for boot.<br>
2.If the count is less than or equal to, for example 5, then boot all<br>
VMs and exit the script.<br>
3.Otherwise, boot and dequeue vm0 to vm4, and minus the count by 5.<br>
4.Sleep some time, and go to step 2.<br></div></div>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<u></u>mailman/listinfo/users</a><br>
</blockquote>
<br>
hooks run one on vm-start one by one. would be a bit tricky to do the above.<br>
roy - didn't you add some mechanism to throttle boot storms in the engine?<br>
</blockquote></div><br></div></div>