[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [xen-unstable test] 60076: regressions - FAIL



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@xxxxxxxxxxxxxx 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: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.