[Xen-devel] [xen-unstable-smoke test] 95241: regressions - FAIL

[osstest service owner <osstest-admin@xxxxxxxxxxxxxx>]

flight 95241 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95241/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-xl          15 guest-start/debian.repeat fail REGR. vs. 95239

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          13 saverestore-support-check    fail   never pass

version targeted for testing:
 xen                  df7f3ce32b99b02884e594435e5ca63acec5d7a3
baseline version:
 xen                  268ead59ce10967cf7490353d743ebc1bb7a9a4c

Last test of basis    95239  2016-06-03 14:02:16 Z    0 days
Testing same since    95241  2016-06-03 16:02:27 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
  Luwei Kang <luwei.kang@xxxxxxxxx>

jobs:
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          fail    
 test-amd64-amd64-xl-qemuu-debianhvm-i386                     pass    
 test-amd64-amd64-libvirt                                     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
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit df7f3ce32b99b02884e594435e5ca63acec5d7a3
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Fri Jun 3 16:21:46 2016 +0100

    docs: Feature Levelling feature document
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
    Release-acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit c52319642bb9069436d4aec75361049f5fac63ed
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Thu Jun 2 12:08:42 2016 +0100

    x86/cpuid: Calculate a guests xfeature_mask from its featureset
    
    libxc current performs the xstate calculation for guests, and provides the
    information to Xen to be used when satisfying CPUID traps.  (There is 
further
    work planned to improve this arrangement, but the worst a buggy toolstack 
can
    do is make junk appear in the cpuid leaves for the guest.)
    
    dom0 however has no policy constructed for it, and certain fields filter
    straight through from hardware.
    
    Linux queries CPUID.7[0].{EAX/EDX} alone to choose a setting for %xcr0, 
which
    is a valid action to take, but features such as MPX and PKRU are not 
supported
    for PV guests.  As a result, Linux, using leaked hardware information, fails
    to set %xcr0 on newer Skylake hardware with PKRU support, and crashes.
    
    As an interim solution, dynamically calculate the correct xfeature_mask and
    xstate_size to report to the guest for CPUID.7[0] queries.  This ensures 
that
    domains don't see leaked hardware values, even when no cpuid policy is
    provided.
    
    Similarly, CPUID.7[1]{ECX/EDX} represents the applicable settings for 
MSR_XSS.
    As Xen doesn't yet support any XSS states in guests, unconditionally zero
    them.
    
    Reported-by: Luwei Kang <luwei.kang@xxxxxxxxx>
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Tested-by: Luwei Kang <luwei.kang@xxxxxxxxx>
    Release-acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
(qemu changes not included)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel