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

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

flight 20085 xen-unstable real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-xl-credit2   10 guest-saverestore         fail REGR. vs. 20083

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-armhf-armhf-xl           3 host-install(3)              broken never pass
 test-amd64-i386-xend-winxpsp3 16 leak-check/check             fail  never pass
 test-amd64-amd64-xl-qemuu-winxpsp3 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-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-win7-amd64 13 guest-stop                   fail  never pass
 test-amd64-amd64-xl-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-i386-xend-qemut-winxpsp3 16 leak-check/check        fail never pass
 test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop             fail never pass

version targeted for testing:
 xen                  8e0da8c07f4f80e14314977a11f738bd74a5b62b
baseline version:
 xen                  1e143e2ae8be3ba86c2e931a1ee8d91efca08f89

People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
  Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Jun Nakajima <jun.nakajima@xxxxxxxxx>
  Keir Fraser <keir@xxxxxxx>
  Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  Yang Zhang <yang.z.zhang@xxxxxxxxx>

 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl                                          pass    
 test-armhf-armhf-xl                                          broken  
 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                                   fail    
 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                          fail    
 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 8e0da8c07f4f80e14314977a11f738bd74a5b62b
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Fri Oct 4 12:58:20 2013 +0200

    x86: Improve information from domain_crash_synchronous
    As it currently stands, the string "domain_crash_sync called from entry.S" 
    not helpful at identifying why the domain was crashed, and a debug build of
    Xen doesn't help the matter
    This patch improves the information printed, by pointing to where the crash
    decision was made.
    Specific improvements include:
     * Moving the ascii string "domain_crash_sync called from entry.S\n" away 
       some semi-hot code cache lines.
     * Moving the printk into C code (especially as this_cpu() is miserable to 
       in assembly code)
     * Undo the previous confusing situation of having the
       domain_crash_synchronous() as a macro in C code, yet a global symbol in
       assembly code.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>

commit fe06795e82922f8d8c8910da545ef1215cbb1b8c
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Fri Oct 4 12:57:43 2013 +0200

    x86/traps: Record last extable faulting address
    ... so the following patch can identify the location of faults leading to a
    decision to crash a domain.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>

commit ef912fbf2eadfa34e61210430117b6c2a4f7c567
Author: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date:   Fri Oct 4 12:54:38 2013 +0200

    x86: allow HVM guests to make console_io hypercall
    The console_io hypercall is provided for PV guests and for HVM
    guests it is done via the 0xe9 port. However the PV hypercall
    is more efficient as it takes a string rather than one character
    per write.
    Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>

commit d4fede3b1248c034901c0e3e901d7400d8dbbed1
Author: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Date:   Fri Oct 4 12:52:56 2013 +0200

    xsm: clean up unneeded current references
    Some XSM hooks in dummy.h used current->domain when this was also passed
    as a parameter; use the parameter in these cases. There are two hooks
    where this does not apply and which are not immediately obvious:
    xsm_set_target's parameters are the device model and HVM domains, and
    xsm_mem_sharing_op's first parameter is the source of the shared page,
    not the domain making the hypercall.
    Reported-by: Jan Beulich <jbeulich@xxxxxxxx>
    Signed-off-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>

commit 65ba631bcb62c79eb33ebfde8a0471fd012c37a8
Author: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Date:   Fri Oct 4 12:51:44 2013 +0200

    xsm: forbid PV guest console reads
    The CONSOLEIO_read operation was incorrectly allowed to PV guests if the
    hypervisor was compiled in debug mode (with VERBOSE defined).
    Reported-by: Jan Beulich <jbeulich@xxxxxxxx>
    Signed-off-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>

commit 11b85dbd0ab068bad3beadda3aee2298205a3c01
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Fri Oct 4 12:32:25 2013 +0200

    x86: make hvm_cpuid() tolerate NULL pointers
    Now that other HVM code started making more extensive use of
    hvm_cpuid(), let's not force every caller to declare dummy variables
    for output not cared about.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
    Acked-by: Jun Nakajima <jun.nakajima@xxxxxxxxx>

commit c6f92aed0e209df823d2cb5780dbb1ea12fc6d4a
Author: Yang Zhang <yang.z.zhang@xxxxxxxxx>
Date:   Fri Oct 4 12:30:09 2013 +0200

    Nested VMX: fix IA32_VMX_CR4_FIXED1 msr emulation
    Currently, it use hardcode value for IA32_VMX_CR4_FIXED1. This is wrong.
    We should check guest's cpuid to know which bits are writeable in CR4 by 
    and allow the guest to set the corresponding bit only when guest has the 
    Signed-off-by: Yang Zhang <yang.z.zhang@xxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Jun Nakajima <jun.nakajima@xxxxxxxxx>

commit 1332d0e907fd5b6075241d36257f8faef5ec97a7
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Fri Oct 4 12:29:08 2013 +0200

    VMX: clean up capability checks
    VMCS size validation on APs should check against BP's size.
    No need for a separate cpu_has_vmx_ins_outs_instr_info variable
    Use proper symbolics.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Jun Nakajima <jun.nakajima@xxxxxxxxx>

commit 190b667ac20e8175758f4a3a0f13c4d990e6af7e
Author: Yang Zhang <yang.z.zhang@xxxxxxxxx>
Date:   Fri Oct 4 12:28:14 2013 +0200

    Nested VMX: check VMX capability before read VMX related MSRs
    VMX MSRs only available when the CPU support the VMX feature. In addition,
    VMX_TRUE* MSRs only available when bit 55 of VMX_BASIC MSR is set.
    Signed-off-by: Yang Zhang <yang.z.zhang@xxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Jun Nakajima <jun.nakajima@xxxxxxxxx>

commit 7cfb0053629c4dd1a6f01dc43cca7c0c25b8b7bf
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Fri Oct 4 12:24:34 2013 +0200

    x86/percpu: Force INVALID_PERCPU_AREA into the non-canonical address region
    This causes accidental uses of per_cpu() on a pcpu with an 
    to result in a #GF for attempting to access the middle of the non-canonical
    virtual address region.
    This is preferable to the current behaviour, where incorrect use of 
    will result in an effective NULL structure dereference which has security
    implication in the context of PV guests.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>

commit 0aa27ce3351f7eb09d13e863a1d5f303086aa32a
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Fri Oct 4 12:23:23 2013 +0200

    x86/idle: Fix get_cpu_idle_time()'s interaction with offline pcpus
    Checking for "idle_vcpu[cpu] != NULL" is insufficient protection against
    offline pcpus.  From a hypercall, vcpu_runstate_get() will determine "v !=
    current", and try to take the vcpu_schedule_lock().  This will try to look 
    per_cpu(schedule_data, v->processor) and promptly suffer a NULL structure
    deference as v->processors' __per_cpu_offset is INVALID_PERCPU_AREA.
    One example might look like this:
    Xen call trace:
       [<ffff82c4c0126ddb>] vcpu_runstate_get+0x50/0x113
       [<ffff82c4c0126ec6>] get_cpu_idle_time+0x28/0x2e
       [<ffff82c4c012b5cb>] do_sysctl+0x3db/0xeb8
       [<ffff82c4c023280d>] compat_hypercall+0xbd/0x116
    Pagetable walk from 0000000000000040:
     L4[0x000] = 0000000186df8027 0000000000028207
     L3[0x000] = 0000000188e36027 00000000000261c9
     L2[0x000] = 0000000000000000 ffffffffffffffff
    Panic on CPU 11:
    get_cpu_idle_time() has been updated to correctly deal with offline pcpus
    itself by returning 0, in the same way as it would if it was missing the
    idle_vcpu[] pointer.
    In doing so, XENPF_getidletime needed updating to correctly retain its
    described behaviour of clearing bits in the cpumap for offline pcpus.
    As this crash can only be triggered with toolstack hypercalls, it is not a
    security issue and just a simple bug.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
(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®.