From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, Roger Pau Monne <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Ian Jackson <ian.jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH for-4.6] libxl: increase hotplug timeout to 40s
Date: Wed, 5 Aug 2015 10:58:39 +0100 [thread overview]
Message-ID: <1438768719.9747.41.camel@citrix.com> (raw)
In-Reply-To: <20150804102612.GY26074@zion.uk.xensource.com>
On Tue, 2015-08-04 at 11:26 +0100, Wei Liu wrote:
> On Tue, Aug 04, 2015 at 12:02:55PM +0200, Roger Pau Monne wrote:
> > The default libxl timeout for hotplug scripts execution is too low,
> > when
> > launching 40 HVM guests in parallel, all using the same file as disk,
> > execution times of ~20s are expected. Increase the timeout to 40s in
> > order
> > to be sure hotplug scripts have enough time to execute.
> >
> > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> > Reported-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > ---
> > Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> > Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > Cc: Ian Campbell <ian.campbell@citrix.com>
> > Cc: Wei Liu <wei.liu2@citrix.com>
>
> As I understand this from the discussion in the other thread, there is
> no regression in hotplug scripts. Increasing the timeout is a reasonable
> solution for 4.6.
>
> Acked-by: Wei Liu <wei.liu2@citrix.com>
>
> Might be worth mentioning this is short term solution in commit message
> though.
After consultation on IRC I added "This is a short term solution" and
applied, thanks.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-08-05 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 10:02 [PATCH for-4.6] libxl: increase hotplug timeout to 40s Roger Pau Monne
2015-08-04 10:26 ` Wei Liu
2015-08-05 9:58 ` Ian Campbell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1438768719.9747.41.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.