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


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

To: Jiri Denemark <jdenemar@xxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC][PATCH] Increase hotplug timeout
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Thu, 16 Apr 2009 11:48:58 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 16 Apr 2009 03:49:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090415144142.GA9633@xxxxxxxxxx>
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>
Newsgroups: chiark.mail.xen.devel
References: <20090415144142.GA9633@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Jiri Denemark writes ("[Xen-devel] [RFC][PATCH] Increase hotplug timeout"):
> 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.

That's a very long time.  All of that for just one domain ?

> 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.

I think very few people have configurations like yours.

Perhaps it would be best to make the timeout configurable, but leave
the default unchanged ?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>