at least in my case changing the value to 30 seconds is not enough, we
had to change it to 5 minutes
I suggest you let the user change it as he wishes.
On Thu, Jan 16, 2014 at 6:21 PM, Martin Kletzander mklet...@redhat.comwrote:
On Thu, Jan 16, 2014 at 04:11:07PM +, Daniel P. Berrange
On Mon, Jan 20, 2014 at 04:33:09PM +0200, Pavel Fux wrote:
at least in my case changing the value to 30 seconds is not enough, we
had to change it to 5 minutes
What is the scenario in which you're seeing this problem ? Is it a problem
when you are running lots of machines at once on a host ?
On Thu, Jan 09, 2014 at 09:22:06AM +0100, Martin Kletzander wrote:
There is a number of reported issues when we fail starting a domain.
Turns out that, in some scenarios like high load, 3 second timeout is
not enough for qemu to start up to the phase where the socket is
created. Since the
On Thu, Jan 16, 2014 at 04:11:07PM +, Daniel P. Berrange wrote:
On Thu, Jan 09, 2014 at 09:22:06AM +0100, Martin Kletzander wrote:
There is a number of reported issues when we fail starting a domain.
Turns out that, in some scenarios like high load, 3 second timeout is
not enough for
There is a number of reported issues when we fail starting a domain.
Turns out that, in some scenarios like high load, 3 second timeout is
not enough for qemu to start up to the phase where the socket is
created. Since the timeout is configurable and there is no downside
of waiting longer, raise
