This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [RFC][PATCH] Increase hotplug timeout

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [RFC][PATCH] Increase hotplug timeout
From: Jiri Denemark <jdenemar@xxxxxxxxxx>
Date: Wed, 15 Apr 2009 16:41:42 +0200
Delivery-date: Wed, 15 Apr 2009 07:42:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)

When a process in dom0 is writing huge amount of data to a disk in parallel to
creating new domain, it may take quite a lot of time until all hotplug scripts
finish. For example, on my system it takes almost 5 minutes to start all
hotplug scripts.

So it seems 100 seconds is not enough for such scenarios as xend would give up
waiting for hotplug scripts too early. What do you think about the attached
patch, which increases the timeout to 10 minutes? Of course, the dark side of
this change is that it would take ages to recognize hotplug scripts are not
really working.

Thanks for your opinions on this.

Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

Attachment: hoplug-timeout.patch
Description: Text document

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>