[xen-unstable-smoke test] 64953: regressions - FAIL

[xen-unstable-smoke test] 64953: regressions - FAIL

[osstest service owner]

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

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-xl           6 xen-boot                  fail REGR. vs. 64861

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

version targeted for testing:
 xen                  c35eefded2992fc9b979f99190422527650872fd
baseline version:
 xen                  65288cf610ccf1aae423f65ac67ee5dbeff252a1

Last test of basis    64861  2015-11-19 16:00:58 Z    0 days
Testing same since    64953  2015-11-20 12:00:47 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Jan Beulich <jbeulich@suse.com>

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 c35eefded2992fc9b979f99190422527650872fd
Author: Jan Beulich <jbeulich@suse.com>
Date:   Fri Nov 20 12:38:33 2015 +0100

    x86/P2M: consolidate handling of types not requiring a valid MFN
    
    As noted regarding the mixture of checks in p2m_pt_set_entry(),
    introduce a new P2M type group allowing to be used everywhere we
    just care about accepting operations with either a valid MFN or a type
    permitting to be used without (valid) MFN.
    
    Note that p2m_mmio_dm is not included in P2M_NO_MFN_TYPES, as for the
    intended purpose that one ought to be treated similar to p2m_invalid
    (perhaps the two should ultimately get folded anyway).
    
    Note further that PoD superpages now get INVALID_MFN used when creating
    page table entries (was _mfn(0) before).
    
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Reviewed-by: George Dunlap <george.dunlap@citrix.com>

commit 513c203a0046232c55adf6d70ec1dbe54e8d157f
Author: Jan Beulich <jbeulich@suse.com>
Date:   Fri Nov 20 12:37:37 2015 +0100

    x86/PoD: tighten conditions for checking super page
    
    Since calling the function isn't cheap, try to avoid the call when we
    know up front it won't help; see the code comment for details on those
    conditions.
    
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Reviewed-by: George Dunlap <george.dunlap@citrix.com>
(qemu changes not included)