xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Anthony PERARD <anthony.perard@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel@lists.xen.org, Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH V3] libxl: Increase device model startup timeout to 1min.
Date: Tue, 14 Jul 2015 07:17:23 +0100	[thread overview]
Message-ID: <55A4C593020000780009077E@mail.emea.novell.com> (raw)
In-Reply-To: <1436283671.25646.254.camel@citrix.com>

>>> On 07.07.15 at 17:41, <ian.campbell@citrix.com> wrote:
> On Tue, 2015-07-07 at 16:14 +0100, Ian Jackson wrote:
>> Anthony PERARD writes ("[PATCH V3] libxl: Increase device model startup 
> timeout to 1min."):
>> > On a busy host, QEMU may take more than 10s to load and start.
>> > 
>> > This is likely due to a bug in Linux where the I/O subsystem sometime
>> > produce high latency under load and result in QEMU taking a long time to
>> > load every single dynamic libraries.
>> 
>> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
> 
> Applied.

So is this the "answer" to "Problems with merlot* AMD Opteron 6376
systems"?

Jan

  reply	other threads:[~2015-07-14  6:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 11:57 [PATCH] libxl: Increase device model startup timeout to 1min Anthony PERARD
2015-06-26 16:41 ` Ian Campbell
2015-06-29 14:23   ` Anthony PERARD
2015-06-29 14:51     ` Ian Campbell
2015-06-29 16:09       ` Anthony PERARD
2015-06-30  3:08         ` Dario Faggioli
2015-06-30 14:04         ` Ian Jackson
2015-06-30 15:58           ` Stefano Stabellini
2015-06-30 16:40             ` Ian Jackson
2015-07-01 15:03               ` Stefano Stabellini
2015-07-02 11:11                 ` Anthony PERARD
2015-07-02 12:38                   ` Ian Jackson
2015-07-03 11:21                     ` Anthony PERARD
2015-07-03 11:30                       ` Ian Jackson
2015-07-07 13:44                         ` Ian Campbell
2015-07-07 13:47                           ` Ian Jackson
2015-07-07 14:37                             ` [PATCH V2] " Anthony PERARD
2015-07-07 14:41                               ` Ian Jackson
2015-07-07 15:09                                 ` [PATCH V3] " Anthony PERARD
2015-07-07 15:14                                   ` Ian Jackson
2015-07-07 15:41                                     ` Ian Campbell
2015-07-14  6:17                                       ` Jan Beulich [this message]
2015-07-14  7:55                                         ` Ian Campbell
2015-07-14  9:25                                           ` Dario Faggioli
2015-07-14  9:37                                             ` Ian Campbell
2015-07-14 10:52                                               ` Dario Faggioli
2015-07-14 14:23                                                 ` Dario Faggioli
2015-07-14 14:48                                                   ` Ian Campbell

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=55A4C593020000780009077E@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).