Bug 695654

Summary:	[patch] Implement BOOT_TIMEOUT
Product:	Red Hat Enterprise Linux 6	Reporter:	Alexander Todorov <atodorov>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	crobinso, dallan, eblake, xen-maint, yoyzhang
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	695653	Environment:
Last Closed:	2011-04-14 20:07:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Alexander Todorov 2011-04-12 10:18:39 UTC

+++ This bug was initially created as a clone of Bug #695653 +++

Created attachment 491448 [details]
patch to implement BOOT_TIMEOUT functionality

Description of problem:
AFAIK when guests are marked as autostart all of them are started at once. The same is true when guests are started/resumed from the libvirt-guests init script. 

In my case it puts load on the system and starting 10 guests at once appears to be slower (time from boot to login prompt) than starting them one after the other.

Attached is a small patch to sleep $BOOT_TIMEOUT seconds before starting the next guest. 


Version-Release number of selected component (if applicable):
git as of today.

How reproducible:
Always

Steps to Reproduce:
1. Create several KVM guests and let libvirt-guests script start them
2.
3.
  
Actual results:
All guests are started at once. It is not possible to start guests one after the other.

Expected results:


Additional info:
Similar functionality exists when shutting down guests.