From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Jim Fehlig <jfehlig@suse.com>,
xen-devel@lists.xensource.com,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [libvirt test] 58119: regressions - FAIL
Date: Fri, 26 Jun 2015 17:44:59 +0100 [thread overview]
Message-ID: <21901.33163.547929.321814@mariner.uk.xensource.com> (raw)
In-Reply-To: <20150626115501.GL3393@perard.uk.xensource.com>
Anthony PERARD writes ("Re: [Xen-devel] [libvirt test] 58119: regressions - FAIL"):
> FYI, I have looked at how long it takes for QEMU to start, from libxl point
> of view, and from strace point of view.
>
> For libxl, I have look at the time difference between a call to
> libxl__ev_xswatch_register('device-model/$domid/path') and
> libxl__qmp_initialize():
> cat deltatime | sort | uniq -c
> 2754 0:00:00
> 1309 0:00:01
> 12 0:00:02
> 8 0:00:03
> 5 0:00:04
> 1 0:00:05
> 4 0:00:06
> 7 0:00:07
> 6 0:00:08
> 1 0:00:09
> 2 0:00:10
> 16 timeout: 0:00:10
Is this information from merlot ?
> >From straces, it is the time between the execve() call and when QEMU
> respond to a QMP connection. The average is 0.316729, and the standard
> deviation is 0.460369 (The average and std deviation does not take into
> account the QEMUs that timed out). But, out of the 3386 QEMU startup,
> there are 26 run that took between 2s and 10s, and there are 14
> more qemu run that have timed out.
>
> I'm going to send a patch to ask to increase the timeout.
I think you have not explained why these long startup times are to be
expected. If they are _not_ expected, we should not be covering up
for them by increasing the timeout.
Ian.
next prev parent reply other threads:[~2015-06-26 16:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 4:37 [libvirt test] 58119: regressions - FAIL osstest service user
2015-06-08 9:22 ` Ian Campbell
2015-06-13 0:38 ` Jim Fehlig
2015-06-15 14:30 ` Anthony PERARD
2015-06-17 8:48 ` Ian Campbell
2015-06-17 9:47 ` Ian Jackson
2015-06-18 15:18 ` Ian Campbell
2015-06-18 16:02 ` Ian Campbell
2015-06-23 18:44 ` Jim Fehlig
2015-06-24 8:32 ` Ian Campbell
2015-06-23 18:53 ` Jim Fehlig
2015-06-23 11:15 ` Anthony PERARD
2015-06-23 12:57 ` Ian Campbell
2015-06-23 13:32 ` Anthony PERARD
2015-06-26 11:55 ` Anthony PERARD
2015-06-26 16:44 ` Ian Jackson [this message]
2015-06-29 14:08 ` Anthony PERARD
2015-06-23 13:38 ` Ian Campbell
2015-06-24 12:40 ` Dario Faggioli
2015-06-24 13:39 ` Anthony PERARD
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=21901.33163.547929.321814@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jfehlig@suse.com \
--cc=xen-devel@lists.xensource.com \
/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.