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

[Xen-devel] [xen-4.5-testing test] 57454: regressions - trouble: broken/fail/pass

flight 57454 xen-4.5-testing real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail REGR. vs. 

Tests which are failing intermittently (not blocking):
 test-armhf-armhf-xl-sedf-pin  3 host-install(3)           broken pass in 57410
 test-armhf-armhf-libvirt      3 host-install(3)           broken pass in 57410
 test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-localmigrate.2 fail in 57410 
pass in 57454
 test-amd64-i386-xl-qemuu-win7-amd64 12 guest-localmigrate fail in 57410 pass 
in 57454
 test-armhf-armhf-xl-cubietruck 14 guest-start.2             fail pass in 57410

Regressions which are regarded as allowable (not blocking):
 test-armhf-armhf-libvirt     11 guest-start           fail in 57410 like 56941
 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop              fail like 56898
 test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop              fail like 56941

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-xl-sedf-pin 12 migrate-support-check fail in 57410 never pass
 test-amd64-amd64-xl-pvh-intel 11 guest-start                  fail  never pass
 test-amd64-amd64-xl-pvh-amd  11 guest-start                  fail   never pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-arndale  12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt      12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-multivcpu 12 migrate-support-check        fail  never pass
 test-armhf-armhf-xl-cubietruck 12 migrate-support-check        fail never pass
 test-armhf-armhf-xl-credit2  12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-sedf     12 migrate-support-check        fail   never pass
 test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop             fail never pass
 test-armhf-armhf-xl          12 migrate-support-check        fail   never pass

version targeted for testing:
 xen                  9d5b2b01024d18b2135c1b0deebb8bfbf5dced5f
baseline version:
 xen                  ddfe333aef87e6c5f52b84c8beb3277be4663313

People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  David Scott <dave.scott@xxxxxxxxxx>
  Ian Campbell <ian.campbell@xxxxxxxxxx>
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
  Jim Fehlig <jfehlig@xxxxxxxx>
  Ross Lagerwall <ross.lagerwall@xxxxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>

 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-armhf-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 build-amd64-rumpuserxen                                      pass    
 build-i386-rumpuserxen                                       pass    
 test-amd64-amd64-xl                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-amd64-i386-xl                                           pass    
 test-amd64-amd64-xl-pvh-amd                                  fail    
 test-amd64-i386-qemut-rhel6hvm-amd                           pass    
 test-amd64-i386-qemuu-rhel6hvm-amd                           pass    
 test-amd64-amd64-xl-qemut-debianhvm-amd64                    pass    
 test-amd64-i386-xl-qemut-debianhvm-amd64                     pass    
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    pass    
 test-amd64-i386-xl-qemuu-debianhvm-amd64                     pass    
 test-amd64-i386-freebsd10-amd64                              pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    
 test-amd64-amd64-rumpuserxen-amd64                           pass    
 test-amd64-amd64-xl-qemut-win7-amd64                         fail    
 test-amd64-i386-xl-qemut-win7-amd64                          fail    
 test-amd64-amd64-xl-qemuu-win7-amd64                         fail    
 test-amd64-i386-xl-qemuu-win7-amd64                          fail    
 test-armhf-armhf-xl-arndale                                  pass    
 test-amd64-amd64-xl-credit2                                  pass    
 test-armhf-armhf-xl-credit2                                  pass    
 test-armhf-armhf-xl-cubietruck                               fail    
 test-amd64-i386-freebsd10-i386                               pass    
 test-amd64-i386-rumpuserxen-i386                             pass    
 test-amd64-amd64-xl-pvh-intel                                fail    
 test-amd64-i386-qemut-rhel6hvm-intel                         pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-amd64-libvirt                                     pass    
 test-armhf-armhf-libvirt                                     broken  
 test-amd64-i386-libvirt                                      pass    
 test-amd64-amd64-xl-multivcpu                                pass    
 test-armhf-armhf-xl-multivcpu                                pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-amd64-amd64-xl-sedf-pin                                 pass    
 test-armhf-armhf-xl-sedf-pin                                 broken  
 test-amd64-amd64-xl-sedf                                     pass    
 test-armhf-armhf-xl-sedf                                     pass    
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     pass    
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     pass    
 test-amd64-amd64-xl-qemut-winxpsp3                           pass    
 test-amd64-i386-xl-qemut-winxpsp3                            pass    
 test-amd64-amd64-xl-qemuu-winxpsp3                           pass    
 test-amd64-i386-xl-qemuu-winxpsp3                            pass    

sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at

Test harness code can be found at

broken-step test-armhf-armhf-xl-sedf-pin host-install(3)
broken-step test-armhf-armhf-libvirt host-install(3)

Not pushing.

commit 9d5b2b01024d18b2135c1b0deebb8bfbf5dced5f
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Mon Mar 2 15:04:37 2015 +0000

    tools/xenconsoled: Increase file descriptor limit
    XenServer's VM density testing uncovered a regression when moving from
    sysvinit to systemd where the file descriptor limit dropped from 4096 to
    1024. (XenServer had previously inserted a ulimit statement into its
    One solution is to use LimitNOFILE=4096 in xenconsoled.service to match the
    lost ulimit, but that is only a stopgap solution.
    As Xenconsoled genuinely needs a large number of file descriptors if a large
    number of domains are running, attempt to increase the limit.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    (cherry picked from commit 588df84c0d702e835e526ecef3af6c5444857558)

commit a984d860ee0612f30c1aebbdb94dba801eb7a6e6
Author: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx>
Date:   Tue Feb 24 08:05:50 2015 +0000

    tools/hotplug: systemd: Don't ever kill xenstored
    Don't kill xenstored as part of the usual service shutdown process to
    prevent hangs on shutdown where the kernel tries to unplug a VIF
    after xenstored has exited.
    In an ideal case with all guests cooperating, xendomains will have shut
    down all guests before xenstored is killed.
    However in the uncooperative case, malicious or crashed guests may still
    be running after xendomains has exited and this should not block the
    shutdown/reboot of dom0.
    Xenstored has no state to sync to disk, and never used to be killed in
    the sysvinit case; observe the warning in xencommons.  Our testing has
    shown regressions caused by the change in behaviour between sysvinit and
    systemd when it comes to killing xenstored.
    Signed-off-by: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    [ ijc -- added systemd to title ]
    (cherry picked from commit 96e0ee8386cf690c28c46a2c9f75cd2b03f646e1)

commit cfc4c43be14e60608ed0b8173365c737950afe41
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Fri Jan 30 14:11:14 2015 +0000

    ocaml/xenctrl: Fix stub_xc_readconsolering()
    The Ocaml stub to retrieve the hypervisor console ring had a few problems.
     * A single 32k buffer would truncate a large console ring.
     * The buffer was static and not under the protection of the Ocaml GC lock 
       could be clobbered by concurrent accesses.
     * Embedded NUL characters would cause caml_copy_string() (which is strlen()
       based) to truncate the buffer.
    The function is rewritten from scratch, using the same algorithm as the 
    stubs, but uses the protection of the Ocaml GC lock to maintain a static
    running total of the ring size, to avoid redundant realloc()ing in future
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    CC: Dave Scott <dave.scott@xxxxxxxxxxxxx>
    CC: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
    CC: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    CC: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: David Scott <dave.scott@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    (cherry picked from commit 1a010ca99e9b04c1cfbd0ee718aa22d5ebd530ab)

commit 032673c8836e28d9e291e0d02235001c41aedaab
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Wed Jan 28 17:55:32 2015 +0000

    ocaml/xenctrl: Make failwith_xc() thread safe
    The static error_str[] buffer is not thread-safe, and 1024 bytes is
    unreasonably large.  Reduce to 256 bytes (which is still much larger than 
    current use), and move it to being a stack variable.
    Also, propagate the Noreturn attribute from caml_raise_with_string().
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    CC: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
    CC: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
    CC: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    CC: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: David Scott <dave.scott@xxxxxxxxxx>
    (cherry picked from commit c8945d51613450c19e0898b1b3056c90f4929179)

commit c91ed889ea3c3781a94a30909f30c3aad56c97d5
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Tue Jan 27 20:38:11 2015 +0000

    ocaml/xenctrl: Check return values from hypercalls
    rather than blindly continuing and possibly using negative values.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    CC: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
    CC: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    CC: Wei Liu <wei.liu2@xxxxxxxxxx>
    CC: Dave Scott <dave.scott@xxxxxxxxxxxxx>
    Acked-by: David Scott <dave.scott@xxxxxxxxxx>
    (cherry picked from commit 3380f5b6270e6fa4b24313f8808e7625e4c5a6ba)

commit fa62913ea76b0129cd76ef06ce4cd5d946c25d13
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Thu Mar 5 16:28:04 2015 +0000

    libxl: Domain destroy: fork
    Call xc_domain_destroy in a subprocess.  That allows us to do so
    asynchronously, rather than blocking the whole process calling libxl.
    The changes in detail:
     * Provide an libxl__ev_child in libxl__domain_destroy_state, and
       initialise it in libxl__domain_destroy.  There is no possibility
       to `clean up' a libxl__ev_child, but there need to clean it up, as
       the control flow ensures that we only continue after the child has
     * Call libxl__ev_child_fork at the right point and put the call to
       xc_domain_destroy and associated logging in the child.  (The child
       opens a new xenctrl handle because we mustn't use the parent's.)
     * Consequently, the success return path from domain_destroy_domid_cb
       no longer calls dis->callback.  Instead it simply returns.
     * We plumb the errorno value through the child's exit status, if it
       fits.  This means we normally do the logging only in the parent.
     * Incidentally, we fix the bug that we were treating the return value
       from xc_domain_destroy as an errno value when in fact it is a
       return value from do_domctl (in this case, 0 or -1 setting errno).
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Reviewed-by: Jim Fehlig <jfehlig@xxxxxxxx>
    Tested-by: Jim Fehlig <jfehlig@xxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    (cherry picked from commit 188e9c541f698109a76cf334b925c77b6007aba1)

commit c9b13f32dcf414e7406ed8518a20ac0022d41aa4
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Tue Mar 17 09:30:58 2015 -0600

    libxl: Domain destroy: unlock userdata earlier
    Unlock the userdata before we actually call xc_domain_destroy.  This
    leaves open the possibility that other libxl callers will see the
    half-destroyed domain (with no devices, paused), but this is fine.
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    CC: Wei Liu <wei.liu2@xxxxxxxxxx>
    Reviewed-by: Jim Fehlig <jfehlig@xxxxxxxx>
    Tested-by: Jim Fehlig <jfehlig@xxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    (cherry picked from commit 1c91d6fba20c1517d78076d412d33cb41f501be5)

commit 0b19348f3cd176e4badb173dd0054c49346a6ce1
Author: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date:   Tue Mar 17 09:30:57 2015 -0600

    libxl: In domain death search, start search at first domid we want
    From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    When domain_death_xswatch_callback needed a further call to
    xc_domain_getinfolist it would restart it with the last domain it
    found rather than the first one it wants.
    If it only wants one it will also only ask for one domain.  The result
    would then be that it gets the previous domain again (ie, the previous
    one to the one it wants), which still doesn't reveal the answer to the
    question, and it would therefore loop again.
    It's completely unclear to me why I thought it was a good idea to
    start the xc_domain_getinfolist with the last domain previously found
    rather than the first one left un-confirmed.  The code has been that
    way since it was introduced.
    Instead, start each xc_domain_getinfolist at the next domain whose
    status we need to check.
    We also need to move the test for !evg into the loop, we now need evg
    to compute the arguments to getinfolist.
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reported-by: Jim Fehlig <jfehlig@xxxxxxxx>
    Reviewed-by: Jim Fehlig <jfehlig@xxxxxxxx>
    Tested-by: Jim Fehlig <jfehlig@xxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    (cherry picked from commit 4783c99aab866f470bd59368cfbf5ad5f677b0ec)

commit 771f857e03fa47a1434f6e468efcc24752aac991
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Wed May 27 16:55:39 2015 +0100

    QEMU_TAG update
(qemu changes not included)

Xen-devel mailing list



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