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

[Xen-devel] [xen-4.2-testing test] 26458: regressions - FAIL

flight 26458 xen-4.2-testing real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-pv           11 guest-saverestore         fail REGR. vs. 26319
 test-amd64-amd64-pv          11 guest-saverestore         fail REGR. vs. 26319
 test-amd64-amd64-pair  17 guest-migrate/src_host/dst_host fail REGR. vs. 26319

Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-xl-sedf     11 guest-saverestore         fail REGR. vs. 26319

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-rumpuserxen-amd64  1 build-check(1)               blocked n/a
 test-i386-i386-rumpuserxen-i386  1 build-check(1)               blocked  n/a
 test-amd64-i386-rumpuserxen-i386  1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt       9 guest-start                  fail   never pass
 test-i386-i386-libvirt        9 guest-start                  fail   never pass
 test-amd64-amd64-xl-qemuu-ovmf-amd64  7 debian-hvm-install     fail never pass
 build-amd64-rumpuserxen       5 rumpuserxen-build            fail   never pass
 test-amd64-i386-xl-qemuu-ovmf-amd64  7 debian-hvm-install      fail never pass
 test-amd64-amd64-libvirt      9 guest-start                  fail   never pass
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-amd64-amd64-xl-qemuu-debianhvm-amd64  9 guest-saverestore fail never pass
 test-amd64-amd64-xl-win7-amd64 14 guest-stop                   fail never pass
 test-amd64-i386-xl-qemuu-win7-amd64 14 guest-stop              fail never pass
 test-amd64-i386-xend-winxpsp3 17 leak-check/check             fail  never pass
 test-amd64-amd64-xl-qemut-winxpsp3 14 guest-stop               fail never pass
 test-amd64-i386-xend-qemut-winxpsp3 17 leak-check/check        fail never pass
 test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop             fail never pass
 test-amd64-i386-xl-win7-amd64 14 guest-stop                   fail  never pass
 test-amd64-i386-xl-qemut-win7-amd64 14 guest-stop              fail never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-stop             fail never pass
 test-i386-i386-xl-qemut-winxpsp3 14 guest-stop                 fail never pass
 test-amd64-amd64-xl-winxpsp3 14 guest-stop                   fail   never pass
 test-amd64-amd64-xl-qemuu-winxpsp3 14 guest-stop               fail never pass
 test-i386-i386-xl-winxpsp3   14 guest-stop                   fail   never pass
 test-i386-i386-xl-qemuu-winxpsp3 14 guest-stop                 fail never pass
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-stop         fail never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 14 guest-stop               fail never pass
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop         fail never pass
 build-i386-rumpuserxen        5 rumpuserxen-build            fail   never pass

version targeted for testing:
 xen                  0a7c4ea20c444a22e05a5483ce317dbefe940ba3
baseline version:
 xen                  148de920337454ba8db5fdf3725c8d1e35f007cf

People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
  Don Dugger <donald.d.dugger@xxxxxxxxx>
  George Dunlap <george.dunlap@xxxxxxxxxxxxx>
  Ian Campbell <ian.campbell@xxxxxxxxxx>
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
  Julien Grall <julien.grall@xxxxxxxxxx>
  Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  Tim Deegan <tim@xxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>
  Xiantao Zhang <xiantao.zhang@xxxxxxxxx>
  Yang Zhang <yang.z.zhang@xxxxxxxxx>

 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 build-amd64-rumpuserxen                                      fail    
 build-i386-rumpuserxen                                       fail    
 test-amd64-amd64-xl                                          pass    
 test-amd64-i386-xl                                           pass    
 test-i386-i386-xl                                            pass    
 test-amd64-i386-rhel6hvm-amd                                 pass    
 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                    fail    
 test-amd64-i386-xl-qemuu-debianhvm-amd64                     pass    
 test-amd64-i386-qemuu-freebsd10-amd64                        pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         fail    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          fail    
 test-amd64-amd64-rumpuserxen-amd64                           blocked 
 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-amd64-amd64-xl-win7-amd64                               fail    
 test-amd64-i386-xl-win7-amd64                                fail    
 test-amd64-i386-xl-credit2                                   pass    
 test-amd64-i386-qemuu-freebsd10-i386                         pass    
 test-amd64-i386-rumpuserxen-i386                             blocked 
 test-i386-i386-rumpuserxen-i386                              blocked 
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-i386-rhel6hvm-intel                               pass    
 test-amd64-i386-qemut-rhel6hvm-intel                         pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-amd64-libvirt                                     fail    
 test-amd64-i386-libvirt                                      fail    
 test-i386-i386-libvirt                                       fail    
 test-amd64-i386-xl-multivcpu                                 pass    
 test-amd64-amd64-pair                                        fail    
 test-amd64-i386-pair                                         pass    
 test-i386-i386-pair                                          pass    
 test-amd64-amd64-xl-sedf-pin                                 pass    
 test-amd64-amd64-pv                                          fail    
 test-amd64-i386-pv                                           fail    
 test-i386-i386-pv                                            pass    
 test-amd64-amd64-xl-sedf                                     fail    
 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-i386-xend-qemut-winxpsp3                          fail    
 test-amd64-amd64-xl-qemut-winxpsp3                           fail    
 test-i386-i386-xl-qemut-winxpsp3                             fail    
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail    
 test-i386-i386-xl-qemuu-winxpsp3                             fail    
 test-amd64-i386-xend-winxpsp3                                fail    
 test-amd64-amd64-xl-winxpsp3                                 fail    
 test-i386-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

Not pushing.

commit 0a7c4ea20c444a22e05a5483ce317dbefe940ba3
Author: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Date:   Fri May 23 15:42:16 2014 +0200

    move domain to cpupool0 before destroying it
    Currently when a domain is destroyed it is removed from the domain_list
    before all of it's resources, including the cpupool membership, are freed.
    This can lead to a situation where the domain is still member of a cpupool
    without for_each_domain_in_cpupool() (or even for_each_domain()) being
    able to find it any more. This in turn can result in rejection of removing
    the last cpu from a cpupool, because there seems to be still a domain in
    the cpupool, even if it can't be found by scanning through all domains.
    This situation can be avoided by moving the domain to be destroyed to
    cpupool0 first and then remove it from this cpupool BEFORE deleting it from
    the domain_list. As cpupool0 is always active and a domain without any 
    membership is implicitly regarded as belonging to cpupool0, this poses no
    Signed-off-by: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
    master commit: bac6334b51d9bcfe57ecf4a4cb5288348fcf044a
    master date: 2014-05-20 15:55:42 +0200

commit 269b6538fadb56161c39b398118a0682d25a7071
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Fri May 23 15:41:34 2014 +0200

    VT-d: extend error report masking workaround to newer chipsets
    Add two more PCI IDs to the set that has been taken care of with a
    different workaround long before XSA-59, and (for constency with the
    newer workarounds) log a message here too.
    Also move the function wide comment to the cases it applies to; this
    should really have been done by d061d200 ("VT-d: suppress UR signaling
    for server chipsets").
    This is CVE-2013-3495 / XSA-59.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Xiantao Zhang <xiantao.zhang@xxxxxxxxx>
    Acked-by: Yang Zhang <yang.z.zhang@xxxxxxxxx>
    master commit: 04734664eb20c3bf239e473af182bb7ab901d779
    master date: 2014-05-20 15:54:01 +0200

commit 917614a82e7c0eeb14acc035ad20aa65c5ca85e7
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Fri May 23 15:40:47 2014 +0200

    VT-d: apply quirks at device setup time rather than only at boot
    Accessing extended config space may not be possible at boot time, e.g.
    when the memory space used by MMCFG is reserved only via ACPI tables,
    but not in the E820/UEFI memory maps (which we need Dom0 to tell us
    about). Consequently the change here still leaves the issue unaddressed
    for systems where the extended config space remains inaccessible (due
    to firmware bugs, i.e. not properly reserving the address space of
    those regions).
    With the respective messages now potentially getting logged more than
    once, we ought to consider whether we should issue them only if we in
    fact were required to do any masking (i.e. if the relevant mask bits
    weren't already set).
    This is CVE-2013-3495 / XSA-59.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Xiantao Zhang <xiantao.zhang@xxxxxxxxx>
    Acked-by: Yang Zhang <yang.z.zhang@xxxxxxxxx>
    master commit: 5786718fbaafbe47d72cc1512cd93de79b8fc2fa
    master date: 2014-05-20 15:53:20 +0200

commit b9aea2a228b614fdb3aa9e143bf329ef71352b4d
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Fri May 23 15:35:45 2014 +0200

    VT-d: suppress UR signaling for desktop chipsets
    Unsupported Requests can be signaled for malformed writes to the MSI
    address region, e.g. due to buggy or malicious DMA set up to that
    region. These should normally result in IOMMU faults, but don't on
    the desktop chipsets dealt with here.
    This is CVE-2013-3495 / XSA-59.
    Note that in the backported version the clearing of the fixmap entry
    is commented out - it's not strictly needed, as we don't re-use the
    fixmap slot (and if we did it would still caue no problems), but causes
    a problem in map_pages_to_xen(), which wants to flush the cache for the
    page in question, but that works only when the page is still mapped.
    Fixing this will need to be a separate patch (coming through -unstable)
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Don Dugger <donald.d.dugger@xxxxxxxxx>
    Acked-by: Tim Deegan <tim@xxxxxxx>
    Acked-by: Xiantao Zhang <xiantao.zhang@xxxxxxxxx>
    master commit: d6cb14b34ffc2a830022d059f1aa22bf19dcf55f
    master date: 2014-04-25 12:12:38 +0200

commit fffcc45a1d6dd4488f69fa6ba5915857e3f17326
Author: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
Date:   Fri May 23 15:33:44 2014 +0200

    x86: use native RDTSC(P) execution when guest and host frequencies are the 
    We should be able to continue using native RDTSC(P) execution on
    HVM/PVH guests after migration if host and guest frequencies are
    equal (this includes the case when the frequencies are made equal
    by TSC scaling feature).
    This also allows us to revert main part of commit 4aab59a3 (svm: Do not
    intercept RDTSC(P) when TSC scaling is supported by hardware) which
    was wrong: while RDTSC intercepts were disabled domain's vtsc could
    still be set, leading to inconsistent view of guest's TSC.
    Signed-off-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>
    master commit: 82713ec8d2b65d17f13e46a131e38bfe5baf8bd6
    master date: 2014-04-22 12:07:37 +0200

commit 7b9e905dd254b17924ede8edf87cf716b3227f31
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Sat May 10 02:18:33 2014 +0100

    tools/pygrub: Fix error handling if no valid partitions are found
    If no partitions at all are found, pygrub never creates the name 'fs',
    resulting in a NameError indicating the lack of fs, rather than a
    RuntimeError explaining that no partitions were found.
    Set fs to None right at the start, and use the pythonic idiom "if fs is 
    to protect against otherwise valid values for fs which compare equal to
    Reported-by: Sven Köhler <sven.koehler@xxxxxxxxx>
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    CC: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
    (cherry picked from commit d75215805ce6ed20b3807955fab6a7f7a3368bee)
    (cherry picked from commit 5ee75ef147f83457fa28d4d4374efcf066581e26)
    (cherry picked from commit 11b2541f458a3d09c63980e669c166cf6e96980a)

commit a4ef5ac91710e1a40afbe0e4782e1473e6cd6405
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Wed Apr 9 14:29:13 2014 +0100

    libxl_json: remove extra "break"
    ... otherwise JSON array elements are not freed and memory is leaked.
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    (cherry picked from commit 3eb54a2fdbc216b39dc2c0a86f11a32d4c838269)
    (cherry picked from commit d6eff6fcc05f7167e5b2232d3bc60047fffb8fc4)
    (cherry picked from commit a14bb4db517ca076ad7d785be52d4bd7a6df6de9)

commit 90c2f8c3029a02813db4b416f6e1aeb2c0266cac
Author: Julien Grall <julien.grall@xxxxxxxxxx>
Date:   Fri Apr 4 11:13:32 2014 +0200

    tmem: remove dumb check in do_tmem_destroy_pool
    do_tmem_destroy_pool is checking if pools == NULL. But, pools is a fixed
    Clang 3.5 will fail to compile xen/common/tmem.c with the following error:
    tmem.c:1848:18: error: comparison of array 'client->pools' equal to a null
    pointer is always false [-Werror,-Wtautological-pointer-compare]
        if ( client->pools == NULL )
    Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx>
    Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
    (cherry picked from commit ac0f56a2fa407e0704fade12630a5a960dedce87)
    (cherry picked from commit 6ce0c3fca9bd1c0d45908452d6e5e9f7bf22f7b7)
    (cherry picked from commit 804d9af208c5c95156140b1c62cf8857ba250b03)

commit 7336d9b50476e6a0447e9bec42b344e017876e71
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Wed May 21 16:33:57 2014 +0200

    Revert "VT-d: suppress UR signaling for desktop chipsets"
    This reverts commit a910070d4289fdf71c3ca35886192a602a3724d5 -
    the use of ioremap()/iounmap() is only valid from 4.3 onwards.
(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®.