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

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

flight 17971 xen-unstable real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-pvops             4 kernel-build     fail in 17970 REGR. vs. 17968

Tests which are failing intermittently (not blocking):
 test-amd64-i386-xend-qemut-winxpsp3  3 host-install(3)    broken pass in 17970

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop             fail never pass
 test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop               fail never pass
 test-amd64-i386-xend-winxpsp3 16 leak-check/check             fail  never pass
 test-amd64-i386-xl-win7-amd64 13 guest-stop                   fail  never pass
 test-amd64-amd64-xl-winxpsp3 13 guest-stop                   fail   never pass
 test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop              fail never pass
 test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop               fail never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop               fail never pass
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop         fail never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop             fail never pass
 test-amd64-amd64-xl-win7-amd64 13 guest-stop                   fail never pass
 test-amd64-amd64-xl-pcipt-intel  1 xen-build-check(1)     blocked in 17970 n/a
 test-amd64-amd64-xl-sedf      1 xen-build-check(1)        blocked in 17970 n/a
 test-amd64-amd64-xl           1 xen-build-check(1)        blocked in 17970 n/a
 test-amd64-amd64-xl-sedf-pin  1 xen-build-check(1)        blocked in 17970 n/a
 test-amd64-amd64-xl-qemut-win7-amd64 1 xen-build-check(1) blocked in 17970 n/a
 test-amd64-amd64-xl-qemuu-winxpsp3  1 xen-build-check(1)  blocked in 17970 n/a
 test-amd64-amd64-pv           1 xen-build-check(1)        blocked in 17970 n/a
 test-amd64-amd64-xl-winxpsp3  1 xen-build-check(1)        blocked in 17970 n/a
 test-amd64-amd64-xl-qemut-winxpsp3  1 xen-build-check(1)  blocked in 17970 n/a
 test-amd64-amd64-pair         1 xen-build-check(1)        blocked in 17970 n/a
 test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail in 17970 never 
 test-amd64-amd64-xl-qemuu-win7-amd64 1 xen-build-check(1) blocked in 17970 n/a
 test-amd64-amd64-xl-win7-amd64  1 xen-build-check(1)      blocked in 17970 n/a

version targeted for testing:
 xen                  5d43891bf4002b754cd90d83e91d9190e8c8b9d0
baseline version:
 xen                  afa65ddfd88184a894d9364bec587554c28c20e0

People who touched revisions under test:
  Christoph Egger <chegger@xxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Liu Jinsong <jinsong.liu@xxxxxxxxx>
  Tim Deegan <tim@xxxxxxx>

 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl                                          pass    
 test-amd64-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-win7-amd64                         fail    
 test-amd64-i386-xl-qemut-win7-amd64                          fail    
 test-amd64-amd64-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-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-i386-xl-multivcpu                                 pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-amd64-amd64-xl-sedf-pin                                 pass    
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           pass    
 test-amd64-amd64-xl-sedf                                     pass    
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     fail    
 test-amd64-i386-xl-winxpsp3-vcpus1                           fail    
 test-amd64-i386-xend-qemut-winxpsp3                          broken  
 test-amd64-amd64-xl-qemut-winxpsp3                           fail    
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail    
 test-amd64-i386-xend-winxpsp3                                fail    
 test-amd64-amd64-xl-winxpsp3                                 fail    

sg-report-flight on woking.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 5d43891bf4002b754cd90d83e91d9190e8c8b9d0
Author: Tim Deegan <tim@xxxxxxx>
Date:   Thu May 9 13:06:53 2013 +0100

    x86/hvm: avoid p2m lookups for vlapic accesses.
    The LAPIC base address is a known GFN, so we can skip looking up the
    p2m: we know it should be handled as emulated MMIO.  That helps
    performance in older Windows OSes, which make a _lot_ of TPR accesses.
    This will change the behaviour of any OS that maps other
    memory/devices at its LAPIC address; the new behaviour (the LAPIC
    mapping always wins) is closer to actual hardware behaviour.
    Signed-off-by: Tim Deegan <tim@xxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 71ba77fcf27149a6c75d7d4720f6566f7034ee55
Author: Liu Jinsong <jinsong.liu@xxxxxxxxx>
Date:   Thu May 16 10:34:42 2013 +0200

    x86/vMCE: remove is_vmce_ready check
    Remove is_vmce_ready() check since
    1. it's problematic and overkilled: it checks if virq bind to dom0 mcelog
    driver. That's not correct, since mcelog is just a dom0 driver used to log
    error info, irrelated to dom0 vmce injection. It's also overkilled, defaulty
    dom0 disabled mcelog driver, under such case this checking would resulting
    in system crash:
    (XEN) MCE: This error page is ownded by DOM 0
    (XEN) DOM0 not ready for vMCE
    (XEN) domain_crash called from mcaction.c:133
    (XEN) Domain 0 reported crashed by domain 32767 on cpu#31:
    (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
    (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
    2. it's redundant: hypervisor in fact has checked
    1). whether dom0 vmce ready or not (at inject_vmce()), via checking
        vmce trap callback, to make sure vmce injection OK;
    2). whether dom0 mcelog driver ready or not (at mce_softirq()), via
        virq binding, to make sure error log works;
    3. it's deprecated: for hvm, it checks whether guest vcpu has different
    virtual family/model with that of host pcpu --> that's deprecated, since
    vMCE has changed a lot, not bound to host MCE any more.
    Signed-off-by: Liu Jinsong <jinsong.liu@xxxxxxxxx>
    Acked-by: Christoph Egger <chegger@xxxxxxxxx>
(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®.