From: Dario Faggioli <dario.faggioli@citrix.com>
To: Julien Grall <julien.grall@citrix.com>
Cc: xen-devel@lists.xensource.com,
osstest service owner <osstest-admin@xenproject.org>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [xen-unstable test] 60076: regressions - FAIL
Date: Thu, 30 Jul 2015 09:48:53 +0200 [thread overview]
Message-ID: <1438242533.16912.34.camel@citrix.com> (raw)
In-Reply-To: <55B8E011.6070609@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 3667 bytes --]
On Wed, 2015-07-29 at 15:15 +0100, Julien Grall wrote:
> On 29/07/15 15:10, Julien Grall wrote:
> > osstest is waiting 40s to get the network ready in the guest. When the
> > test pass, the osstest is likely waiting ~20s to pass it. I took the
> > time between
> >
> > guest debian.guest.osstest 5a:36:0e:06:00:20 22 link/ip/tcp: waiting 40s...
> >
> > and the first
> >
> > executing ssh ... root@172.16.146.149 echo guest debian.guest.osstest: ok
> > guest debian.guest.osstest: ok
>
> > For instance see
> > http://logs.test-lab.xenproject.org/osstest/logs/59910/test-armhf-armhf-xl-multivcpu/14.ts-guest-start.log
>
> FWIW, there is also worth case where the waiting time very close to 40s
> (exactly 38s):
>
> http://logs.test-lab.xenproject.org/osstest/logs/59721/test-armhf-armhf-xl-multivcpu/14.ts-guest-start.log
>
Exactly my point, together with this:
http://logs.test-lab.xenproject.org/osstest/logs/60076/test-armhf-armhf-xl-multivcpu/arndale-metrocentre---var-log-xen-console-guest-debian.guest.osstest.log
It show two instances of full guest boot, which makes sense as it is the
second attempt that "fails".
Look at the second one and note:
- that it actually boots fine
- for some reason, we have:
[ 1.196443] udevd[69]: starting version 175
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin:
Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Running /scripts/local-premount ... done.
[ 20.741128] EXT4-fs (xvda2): mounting ext3 file system using the ext4 subsystem
[ 20.755723] EXT4-fs (xvda2): mounted filesystem with ordered data mode. Opts: (null)
... ... ... ...
[ 47.329342] EXT4-fs (xvda2): re-mounted. Opts: (null)
[....] Checking root file system...fsck from util-linux 2.20.1
/dev/xvda2: clean, 14689/262144 files, 124109/1048576 blocks
... ... ... ...
[ 47.803550] EXT4-fs (xvda2): re-mounted. Opts: errors=remount-ro
so it looks like it did take quite a bit to start. Yes, that's in
guest time, but stil...
In first instance, we have this:
[ 1.221159] udevd[69]: starting version 175
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[ 2.275805] EXT4-fs (xvda2): mounting ext3 file system using the ext4 subsystem
[ 2.300418] EXT4-fs (xvda2): mounted filesystem with ordered data mode. Opts: (null)
... ... ... ...
[ 5.958201] EXT4-fs (xvda2): re-mounted. Opts: (null)
[....] Checking root file system...fsck from util-linux 2.20.1
... ... ... ...
[ 6.424911] EXT4-fs (xvda2): re-mounted. Opts: errors=remount-ro
Then, no, I don't think I see why the pre-mount activities (I don't even
know what those are, although, I don't think it matters) already is ~10x
slower, and then the mounting and the fsck check ~6x...
The host is certainly overloaded, in terms of number of vcpus vs. number
of pcpus, but it's not that all those vcpus should be super busy at this
point... Perhaps, the host being practically UP matters (I don't think
I've actually ever run Xen on an UP system! :-P)
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-07-30 7:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 6:42 [xen-unstable test] 60076: regressions - FAIL osstest service owner
2015-07-29 9:05 ` Dario Faggioli
2015-07-29 14:10 ` Julien Grall
2015-07-29 14:15 ` Julien Grall
2015-07-29 18:18 ` Arndale secondary CPU boot issue Was " Julien Grall
2015-07-30 8:55 ` Ian Campbell
2015-07-30 10:54 ` Stefano Stabellini
2015-07-30 11:27 ` Ian Campbell
2015-07-30 11:27 ` David Vrabel
2015-07-30 11:36 ` Julien Grall
2015-07-30 10:38 ` Andrew Cooper
2015-07-30 7:48 ` Dario Faggioli [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=1438242533.16912.34.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=osstest-admin@xenproject.org \
--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.