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

[Xen-devel] [xen-unstable test] 33183: trouble: broken/fail/pass

flight 33183 xen-unstable real [real]

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-libvirt      3 host-install(3)         broken REGR. vs. 32877
 test-amd64-amd64-libvirt      3 host-install(3)         broken REGR. vs. 32877
 test-amd64-i386-libvirt       3 host-install(3)         broken REGR. vs. 32877
 test-amd64-i386-rhel6hvm-amd  3 host-install(3)         broken REGR. vs. 33112
 test-amd64-i386-rhel6hvm-intel  3 host-install(3)       broken REGR. vs. 33112
 test-amd64-i386-qemut-rhel6hvm-intel  3 host-install(3) broken REGR. vs. 33112
 test-amd64-i386-xl-qemuu-debianhvm-amd64 3 host-install(3) broken REGR. vs. 
 test-amd64-amd64-xl-winxpsp3  3 host-install(3)         broken REGR. vs. 33112
 test-amd64-i386-xl-qemuu-ovmf-amd64  3 host-install(3)  broken REGR. vs. 33112
 test-amd64-amd64-xl-qemuu-ovmf-amd64  3 host-install(3) broken REGR. vs. 33112
 test-amd64-i386-xl-win7-amd64  3 host-install(3)        broken REGR. vs. 33112
 test-amd64-i386-pair         4 host-install/dst_host(4) broken REGR. vs. 33112
 test-amd64-i386-pair         3 host-install/src_host(3) broken REGR. vs. 33112
 test-amd64-amd64-xl-qemut-winxpsp3  3 host-install(3)   broken REGR. vs. 33112
 test-amd64-amd64-xl-qemut-win7-amd64  3 host-install(3) broken REGR. vs. 33112
 test-amd64-amd64-xl-qemuu-winxpsp3  3 host-install(3)   broken REGR. vs. 33112

Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-xl-pcipt-intel  3 host-install(3)      broken REGR. vs. 33112
 test-amd64-amd64-xl-sedf      3 host-install(3)         broken REGR. vs. 33112
 test-amd64-i386-xl-multivcpu  3 host-install(3)              broken like 32646

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-xl          10 migrate-support-check        fail   never pass
 test-amd64-amd64-xl-pvh-amd   9 guest-start                  fail   never pass
 test-amd64-amd64-xl-pvh-intel  9 guest-start                  fail  never pass
 test-amd64-i386-xl-qemuu-win7-amd64 14 guest-stop              fail never pass
 test-amd64-i386-xl-qemut-winxpsp3 14 guest-stop                fail never pass
 test-amd64-i386-xl-qemuu-winxpsp3 14 guest-stop                fail never pass
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop         fail never pass
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-stop         fail never pass
 test-amd64-amd64-xl-win7-amd64 14 guest-stop                   fail never pass
 test-amd64-i386-xl-qemut-win7-amd64 14 guest-stop              fail never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 14 guest-stop               fail never pass
 test-amd64-i386-xl-winxpsp3  14 guest-stop                   fail   never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-stop             fail never pass

version targeted for testing:
 xen                  d3c151fd3a4365fc6107198bfc975807d40d157d
baseline version:
 xen                  36174af3fbeb1b662c0eadbfa193e77f68cc955b

People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Ian Campbell <ian.campbell@xxxxxxxxxx>
  Ian Campbell <ijc@xxxxxxxxxxxxxx>
  Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
  Ian Jackson <iwj@xxxxxxxxxxxxxxxxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Julien Grall <julien.grall@xxxxxxxxxx>
  Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  Mihai DonÈ?u <mdontu@xxxxxxxxxxxxxxx>
  Robert Hu <robert.hu@xxxxxxxxx>
  RÄ?zvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
  Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>
  Yang Hongyang <yanghy@xxxxxxxxxxxxxx>

 build-amd64                                                  pass
 build-armhf                                                  pass
 build-i386                                                   pass
 build-amd64-libvirt                                          pass
 build-armhf-libvirt                                          pass
 build-i386-libvirt                                           pass
 build-amd64-oldkern                                          pass
 build-i386-oldkern                                           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-rhel6hvm-amd                                 broken
 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                     broken
 test-amd64-i386-freebsd10-amd64                              pass
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         broken
 test-amd64-i386-xl-qemuu-ovmf-amd64                          broken
 test-amd64-amd64-rumpuserxen-amd64                           pass
 test-amd64-amd64-xl-qemut-win7-amd64                         broken
 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-amd64-amd64-xl-win7-amd64                               fail
 test-amd64-i386-xl-win7-amd64                                broken
 test-amd64-i386-xl-credit2                                   pass
 test-amd64-i386-freebsd10-i386                               pass
 test-amd64-i386-rumpuserxen-i386                             pass
 test-amd64-amd64-xl-pcipt-intel                              broken
 test-amd64-amd64-xl-pvh-intel                                fail
 test-amd64-i386-rhel6hvm-intel                               broken
 test-amd64-i386-qemut-rhel6hvm-intel                         broken
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass
 test-amd64-amd64-libvirt                                     broken
 test-armhf-armhf-libvirt                                     broken
 test-amd64-i386-libvirt                                      broken
 test-amd64-i386-xl-multivcpu                                 broken
 test-amd64-amd64-pair                                        pass
 test-amd64-i386-pair                                         broken
 test-amd64-amd64-xl-sedf-pin                                 pass
 test-amd64-amd64-xl-sedf                                     broken
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     fail
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     fail
 test-amd64-i386-xl-winxpsp3-vcpus1                           fail
 test-amd64-amd64-xl-qemut-winxpsp3                           broken
 test-amd64-i386-xl-qemut-winxpsp3                            fail
 test-amd64-amd64-xl-qemuu-winxpsp3                           broken
 test-amd64-i386-xl-qemuu-winxpsp3                            fail
 test-amd64-amd64-xl-winxpsp3                                 broken
 test-amd64-i386-xl-winxpsp3                                  fail

sg-report-flight on osstest.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images

Logs, config files, etc. are available at

Test harness code can be found at

broken-step test-armhf-armhf-libvirt host-install(3)
broken-step test-amd64-amd64-libvirt host-install(3)
broken-step test-amd64-amd64-xl-pcipt-intel host-install(3)
broken-step test-amd64-i386-libvirt host-install(3)
broken-step test-amd64-i386-rhel6hvm-amd host-install(3)
broken-step test-amd64-amd64-xl-sedf host-install(3)
broken-step test-amd64-i386-xl-multivcpu host-install(3)
broken-step test-amd64-i386-rhel6hvm-intel host-install(3)
broken-step test-amd64-i386-qemut-rhel6hvm-intel host-install(3)
broken-step test-amd64-i386-xl-qemuu-debianhvm-amd64 host-install(3)
broken-step test-amd64-amd64-xl-winxpsp3 host-install(3)
broken-step test-amd64-i386-xl-qemuu-ovmf-amd64 host-install(3)
broken-step test-amd64-amd64-xl-qemuu-ovmf-amd64 host-install(3)
broken-step test-amd64-i386-xl-win7-amd64 host-install(3)
broken-step test-amd64-i386-pair host-install/dst_host(4)
broken-step test-amd64-i386-pair host-install/src_host(3)
broken-step test-amd64-amd64-xl-qemut-winxpsp3 host-install(3)
broken-step test-amd64-amd64-xl-qemut-win7-amd64 host-install(3)
broken-step test-amd64-amd64-xl-qemuu-winxpsp3 host-install(3)

Not pushing.

commit d3c151fd3a4365fc6107198bfc975807d40d157d
Author: Mihai DonÈ?u <mdontu@xxxxxxxxxxxxxxx>
Date:   Tue Jan 6 12:49:52 2015 +0000

    x86/HVM: prevent use-after-free when destroying a domain

    hvm_domain_relinquish_resources() can free certain domain resources
    which can still be accessed, e.g. by HVMOP_set_param, while the domain
    is being cleaned up.

    This is CVE-2015-0361 / XSA-116.

    Signed-off-by: Mihai DonÈ?u <mdontu@xxxxxxxxxxxxxxx>
    Tested-by: RÄ?zvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 8233ca53adf008da54c01d55d3309c4b0999ddb5
Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date:   Fri Nov 28 16:53:09 2014 +0000

    reset PCI devices on force removal even when QEMU returns error

    On do_pci_remove when QEMU returns error, we just bail out early without
    resetting the device. On domain shutdown we are racing with QEMU exiting
    and most often QEMU closes the QMP connection before executing the
    requested command.

    In these cases if force=1, it makes sense to go ahead with rest of the
    PCI device removal, that includes resetting the device and calling
    xc_deassign_device. Otherwise we risk not resetting the device properly
    on domain shutdown.

    Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

commit 876367befa26b12bfdecd6697faa7b8102e4b287
Author: Julien Grall <julien.grall@xxxxxxxxxx>
Date:   Wed Dec 17 15:40:15 2014 +0000

    xen/arm: Initialize the domain vgic lock

    The domain vgic lock is used uninitialized.

    Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

commit 1ec4e3336d413cc489813669e58c47e9156e03d8
Author: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date:   Mon Aug 4 10:58:25 2014 +0100

    tools: libxl: link libxlu against libxl.

    It uses libxl_defbool_set and must therefore be linked against the
    right library.

    Spotted by dpkg-shlibdeps and pointed out by Bastian Blank:

    dpkg-shlibdeps: warning: symbol libxl_defbool_set used by 
debian/libxen-4.4/usr/lib/libxlutil-4.4.so found in none of the libraries

    This required switching the make rule from $^ to an explicit
    LIBXLU_OBJS since the former now includes libxenlight.so.

    Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Cc: Bastian Blank <waldi@xxxxxxxxxx>

commit dea3ff6ed2af2fe3ab084733d3e71daf4dcfb8a0
Author: Ian Campbell <ijc@xxxxxxxxxxxxxx>
Date:   Sun Dec 21 11:18:53 2014 +0000

    xen: arm: correct off-by-one error in consider_modules

    By iterating up to <= mi->nr_mods we are running off the end of the boot
    modules, but more importantly it causes us to then skip the first FDT 
    region, meaning we might clobber it.

    Signed-off-by: Ian Campbell <ijc@xxxxxxxxxxxxxx>
    Reviewed-by: Julien Grall <julien.grall@xxxxxxxxxx>

commit 54eb18cd63ed7243f1ab497e35807bf6f4a436ec
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Mon Jan 5 14:19:58 2015 +0000

    tools/libxl: Use of init()/dispose() to avoid leaking 

    libxl_dominfo contains a ssid_label pointer which will have memory allocated
    for it in libxl_domain_info() if the hypervisor has CONFIG_XSM compiled.
    However, the lack of appropriate use of libxl_dominfo_{init,dispose}() will
    cause the label string to be leaked, even in success cases.

    This was discovered by XenServers Coverity scanning, and are issues not
    identified by upstream Coverity Scan.

    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: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

commit 7ca2558c048c7d5d2a6d401e58181a06a00f9eeb
Author: Ian Jackson <iwj@xxxxxxxxxxxxxxxxxxxxxxxx>
Date:   Fri Nov 14 14:41:38 2014 +0000

    libxl: Fix if{} nesting in do_pci_remove

    do_pci_remove contained this:

        if (type == LIBXL_DOMAIN_TYPE_HVM) {
        } else if (type != LIBXL_DOMAIN_TYPE_PV)

    This is bizarre, and not correct.  The effect is that HVM guests end
    up running both the proper code and that intended for PV guests.  This
    causes (amongst other things) trouble when PCI devices are
    hot-unplugged from HVM guests.

    This bug was introduced in abfb006f "tools/libxl: explicitly grant
    access to needed I/O-memory ranges".

    This is clear candidate for Xen 4.5, being a bugfix to an important

    Reported-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
    Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    Tested-by: Robert Hu <robert.hu@xxxxxxxxx>
    Rlease-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    CC: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
    CC: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>

commit 6b511af68618a86d5a2258e649042a3f0b8ace52
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Mon Jan 5 14:31:00 2015 +0000

    libxl: Initialise CTX->xce in domain suspend, as needed

    When excuting xl migrate/Remus, the following error can occur:
      [root@master xen]# xl migrate 5 slaver
      migration target: Ready to receive domain.
      Saving to migration stream new xl format (info 0x1/0x0/1225)
      Loading new save file <incoming migration stream> (new xl fmt info 
       Savefile contains xl domain config in JSON format
      Parsing config from <saved>
      Segmentation fault (core dumped)

    This is because CTX->xce is used without been initialized.
    The bug was introduced by commit 2ffeb5d7f5d8
        libxl: events: Deregister evtchn fd when not needed
    which removed the initialization of xce from libxl__ctx_alloc.

    In this patch we initialise the CTX->xce before using it.  Also, we
    adjust the doc comment for libxl__ev_evtchn_* to mention the need to
    do so.

    Signed-off-by: Yang Hongyang <yanghy@xxxxxxxxxxxxxx>
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
    Cc: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 4d9ba7b2188083a09d1b1a1bda7054cc3eb77f67
Author: Jan Beulich <JBeulich@xxxxxxxx>
Date:   Mon Dec 15 09:16:09 2014 +0000

    x86/AMD-ucode: correct multiple container handling

    Avoid emitting an error message referring to an incorrect or corrupt
    container file just because no entry was found for the running CPU.

    Additionally switch the order of data validation and consumption in
    cpu_request_microcode()'s first loop, and also check the types of
    skipped blocks in container_fast_forward().

    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@xxxxxxx>
    Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
    Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>

commit 6fb3a07bc0ad656b5f76eb9fc961bcd1d3cace58
Author: Jan Beulich <JBeulich@xxxxxxxx>
Date:   Fri Dec 12 10:24:13 2014 +0000

    domctl: fix IRQ permission granting/revocation

    Commit 545607eb3c ("x86: fix various issues with handling guest IRQs")
    wasn't really consistent in one respect: The granting of access to an
    IRQ shouldn't assume the pIRQ->IRQ translation to be the same in both
    domains. In fact it is wrong to assume that a translation is already/
    still in place at the time access is being granted/revoked.

    What is wanted is to translate the incoming pIRQ to an IRQ for
    the invoking domain (as the pIRQ is the only notion the invoking
    domain has of the IRQ), and grant the subject domain access to
    the resulting IRQ.

    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reported-by: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
    Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>

commit 21c9fce8efbf407dc5d6bcc78bf65a1402623db9
Author: Jan Beulich <JBeulich@xxxxxxxx>
Date:   Thu Dec 11 10:47:21 2014 +0000

    x86: don't deliver NMI to PVH Dom0

    ... for the time being: The mechanism used depends on the domain's use
    of the IRET hypercall - which PVH is not using.  HVM code (which PVH
    uses) will deliver an NMI if it sees v->nmi_pending however that
    temporary affinity adjustment gets undone in the HYPERVISOR_iret
    handler, yet PVH can't call that hypercall.

    Also drop two bogus code lines spotted while going through the involved
    code paths: Addresses of per-CPU variables can't possibly be NULL, and
    the setting of st->vcpu in send_guest_trap()'s MCE case is redundant
    with an earlier cmpxchgptr().

    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
    Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
(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®.