[Xen-devel] [xen-unstable-smoke test] 126846: trouble: broken/pass

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

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-xl             <job status>                 broken
 test-armhf-armhf-xl           4 host-install(4)        broken REGR. vs. 126779

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

version targeted for testing:
 xen                  6ffa33b370f58ed937806105921f66c83aed45e0
baseline version:
 xen                  36e29dd9e580cb0f847f5ac1e72afdb5febe3e99

Last test of basis   126779  2018-08-27 14:01:04 Z    0 days
Testing same since   126846  2018-08-28 10:00:47 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Jan Beulich <jbeulich@xxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>

jobs:
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          broken  
 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

broken-job test-armhf-armhf-xl broken
broken-step test-armhf-armhf-xl host-install(4)

Not pushing.

------------------------------------------------------------
commit 6ffa33b370f58ed937806105921f66c83aed45e0
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Sun Aug 26 13:19:41 2018 +0100

    xen/pt: io.c contains HVM only code
    
    We also need to make it x86 only because ARM will define CONFIG_HVM at
    some point.
    
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 6c851a9e5a535d38a15c0b1c4acf07dc7e1284e0
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Sun Aug 26 13:19:40 2018 +0100

    x86/vpmu: put HVM only code under CONFIG_HVM
    
    Change u32 to uint32_t while at it.
    
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 0199416a2ce1fd84c964d06627f2209ac04afaa2
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Sun Aug 26 13:19:38 2018 +0100

    x86: provide stub for memory_type_changed
    
    Jan indicated that for PV guests the memory type is not changed, for
    HVM guests memory_type_changed is needed for EPT's effective memory
    type calculation.  This means memory_type_changed is HVM only.
    
    Provide a stub to minimise code churn.
    
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 3212e3464f336e0fd1270a88f65028833180709e
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Sun Aug 26 13:19:37 2018 +0100

    x86/hvm: provide hvm_hap_supported
    
    And replace direct accesses in non-HVM subsystems to
    hvm_funcs.hap_supported with the new function, to avoid accessing an
    internal data structure of another subsystem directly.
    
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>

commit a0a6b2421ffcd917d35c2879b6df6c1bfe63f6ca
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Sun Aug 26 13:19:36 2018 +0100

    x86: enclose hvm_op and dm_op in CONFIG_HVM in relevant tables
    
    PV guest (Dom0) needs to able to use these two hypercalls in order to
    serve HVM guests. But if xen doesn't support HVM at all there is no
    point in exposing them to PV guests.
    
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
(qemu changes not included)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel