Ian Campbell writes ("Re: [PATCH] libxl: Increase device model startup timeout
to 1min."):
> On Fri, 2015-07-03 at 12:30 +0100, Ian Jackson wrote:
> > So papering over this with an increase in the timeout is probably
> > proper.
>
> Yes :-/
>
> > I'm tempted to suggest increasing the timeout onl
On Fri, 2015-07-03 at 12:30 +0100, Ian Jackson wrote:
> So papering over this with an increase in the timeout is probably
> proper.
Yes :-/
> I'm tempted to suggest increasing the timeout only on Linux.
How tempted? Or shall I apply this patch?
Ian.
___
Anthony PERARD writes ("Re: [PATCH] libxl: Increase device model startup
timeout to 1min."):
> On Thu, Jul 02, 2015 at 01:38:37PM +0100, Ian Jackson wrote:
> > I'm starting to think that this might be a real bug but that the bug
> > might be "Linux's I/O subsystem sometimes produces appalling late
On Thu, Jul 02, 2015 at 01:38:37PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("Re: [PATCH] libxl: Increase device model startup
> timeout to 1min."):
> > I have tested an increase timeout this night. And here are the result.
> >
> > The machine is a AMD Opteron(tm) Processor 4284, with 8G
Anthony PERARD writes ("Re: [PATCH] libxl: Increase device model startup
timeout to 1min."):
> I have tested an increase timeout this night. And here are the result.
>
> The machine is a AMD Opteron(tm) Processor 4284, with 8G of RAM and 8 pCPU.
> It's running Ubuntu 14.04, with Xen 4.4. On top o
On Wed, Jul 01, 2015 at 04:03:55PM +0100, Stefano Stabellini wrote:
> On Tue, 30 Jun 2015, Ian Jackson wrote:
> > > > * The number and nature of parallel operations done in the stress
> > > > test is unreasonable for the provided hardware:
> > > > => the timeout is fine
> > >
> > > I d
On Tue, 30 Jun 2015, Ian Jackson wrote:
> > > * The number and nature of parallel operations done in the stress
> > > test is unreasonable for the provided hardware:
> > > => the timeout is fine
> >
> > I don't know if it is our place to make this call. Should we really be
> > decidin
Stefano Stabellini writes ("Re: [PATCH] libxl: Increase device model startup
timeout to 1min."):
> On Tue, 30 Jun 2015, Ian Jackson wrote:
> > Anthony PERARD writes ("Re: [PATCH] libxl: Increase device model startup
> > timeout to 1min."):
> > In the third case we probably need a general-purpose
On Tue, 30 Jun 2015, Ian Jackson wrote:
> Anthony PERARD writes ("Re: [PATCH] libxl: Increase device model startup
> timeout to 1min."):
> > On Mon, Jun 29, 2015 at 03:51:57PM +0100, Ian Campbell wrote:
> > > Nor does it really answer Ian's question in
> > > <21901.33163.547929.321...@mariner.uk.x
Anthony PERARD writes ("Re: [PATCH] libxl: Increase device model startup
timeout to 1min."):
> On Mon, Jun 29, 2015 at 03:51:57PM +0100, Ian Campbell wrote:
> > Nor does it really answer Ian's question in
> > <21901.33163.547929.321...@mariner.uk.xensource.com> I think.
>
> I only know what happe
On Mon, 2015-06-29 at 17:09 +0100, Anthony PERARD wrote:
> On Mon, Jun 29, 2015 at 03:51:57PM +0100, Ian Campbell wrote:
> > On Mon, 2015-06-29 at 15:23 +0100, Anthony PERARD wrote:
> > > OK. What about:
> >
> > I'm afraid none of that really explains why QEMU taking >10s is
> > reasonable/expect
On Mon, Jun 29, 2015 at 03:51:57PM +0100, Ian Campbell wrote:
> On Mon, 2015-06-29 at 15:23 +0100, Anthony PERARD wrote:
> > On Fri, Jun 26, 2015 at 05:41:07PM +0100, Ian Campbell wrote:
> > > On Fri, 2015-06-26 at 12:57 +0100, Anthony PERARD wrote:
> > > > On a busy host, QEMU may take more than 1
On Mon, 2015-06-29 at 15:23 +0100, Anthony PERARD wrote:
> On Fri, Jun 26, 2015 at 05:41:07PM +0100, Ian Campbell wrote:
> > On Fri, 2015-06-26 at 12:57 +0100, Anthony PERARD wrote:
> > > On a busy host, QEMU may take more than 10s to start.
> >
> > Please show your working here so that in 2 years
On Fri, Jun 26, 2015 at 05:41:07PM +0100, Ian Campbell wrote:
> On Fri, 2015-06-26 at 12:57 +0100, Anthony PERARD wrote:
> > On a busy host, QEMU may take more than 10s to start.
>
> Please show your working here so that in 2 years when we want to know
> why this value was chosen we don't have to
On Fri, 2015-06-26 at 12:57 +0100, Anthony PERARD wrote:
> On a busy host, QEMU may take more than 10s to start.
Please show your working here so that in 2 years when we want to know
why this value was chosen we don't have to go scrobbling around in the
ML archives looking for the data you gathere
15 matches
Mail list logo
