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

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

flight 128593 xen-unstable-smoke real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-debianhvm-i386 10 debian-hvm-install fail REGR. vs. 

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

version targeted for testing:
 xen                  162fc8295f31240dc3670190a91e9bbc03b0d7be
baseline version:
 xen                  85b00385827e4e061b2ff38b549c03d0f1e66b6a

Last test of basis   128513  2018-10-08 18:01:11 Z    1 days
Failing since        128527  2018-10-09 15:00:42 Z    1 days   12 attempts
Testing same since   128593  2018-10-10 14:00:42 Z    0 days    1 attempts

People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
  George Dunlap <george.dunlap@xxxxxxxxxx>
  Ian Jackson <ian.jackson@xxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Nicolas Poirot <nicolas.poirot@xxxxxxxxx>
  Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
  Roger Pau Monné <roger.pau@xxxxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>

 build-arm64-xsm                                              pass    
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-arm64-arm64-xl-xsm                                      pass    
 test-amd64-amd64-xl-qemuu-debianhvm-i386                     fail    
 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

Explanation of these reports, and of osstest in general, is at

Test harness code can be found at

Not pushing.

commit 162fc8295f31240dc3670190a91e9bbc03b0d7be
Author: George Dunlap <george.dunlap@xxxxxxxxxx>
Date:   Wed Oct 10 12:36:25 2018 +0100

    libxl: Restore scheduling parameters after migrate in best-effort fashion
    Commit 3b4adba ("tools/libxl: include scheduler parameters in the
    output of xl list -l") added scheduling parameters to the set of
    information collected by libxl_retrieve_domain_configuration(), in
    order to report that information in `xl list -l`.
    Unfortunately, libxl_retrieve_domain_configuration() is also called by
    the migration / save code, and the results passed to the restore /
    receive code.  This meant scheduler parameters were inadvertently
    added to the migration stream, without proper consideration for how to
    handle corner cases.  The result was that if migrating from a host
    running one scheduler to a host running a different scheduler, the
    migration would fail with an error like the following:
    libxl: error: libxl_sched.c:232:sched_credit_domain_set: Domain 1:Getting 
domain sched credit: Invalid argument
    libxl: error: libxl_create.c:1275:domcreate_rebuild_done: Domain 1:cannot 
(re-)build domain: -3
    Luckily there's a fairly straightforward way to set parameters in a
    "best-effort" fashion.  libxl provides a single struct containing the
    parameters of all schedulers, as well as a parameter specifying which
    scheduler.  Parameters not used by a given scheduler are ignored.
    Additionally, the struct contains a parameter to specify the
    scheduler.  If you specify a specific scheduler,
    libxl_domain_sched_params_set() will fail if there's a different
    scheduler.  However, if you pass LIBXL_SCHEDULER_UNKNOWN, it will use
    the value of the current scheduler for that domain.
    In domcreate_stream_done(), before calling libxl__build_post(), set
    the scheduler to LIBXL_SCHEDULER_UNKNOWN.  This will propagate
    scheduler parameters from the previous instantiation on a best-effort
    Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 5e00f02763f66dbbf0c86eee333c798fa8565a19
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Tue Oct 9 19:58:12 2018 +0100

    iommu: fix arm build after e9be34be5
    The function iommu_share_p2m_table is used by both ARM and x86 but
    hap_enabled macro is x86 only. Put the ASSERT under CONFIG_X86.
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>

commit cd395b1d69a773556d2af206b4ecbf56b33057ea
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Oct 9 16:27:59 2018 +0200

    x86: put_page_from_l2e() should honor _PAGE_RW
    56fff3e5e9 ("x86: nuke PV superpage option and code") has introduced a
    (luckily latent only) bug here, in that it didn't make reference
    dropping dependent on whether the page was mapped writable. The only
    current source of large page mappings for PV domains is the Dom0
    builder, which only produces writeable ones.
    Take the opportunity and also convert to bool both put_data_page()'s
    respective parameter and the argument put_page_from_l3e() passes.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit e9be34be5f9a1a6ecbf05ba9502cd705ae441476
Author: Roger Pau Monné <roger.pau@xxxxxxxxxx>
Date:   Tue Oct 9 16:27:13 2018 +0200

    x86/vtd: fix iommu_share_p2m_table
    Commit 2916951c1 "mm / iommu: include need_iommu() test in
    iommu_use_hap_pt()" changed the check in iommu_share_p2m_table to use
    need_iommu(d) (as part of iommu_use_hap_pt) instead of iommu_enabled,
    which broke the check because at the point in domain construction
    where iommu_share_p2m_table is called need_iommu(d) will always return
    Fix this by reverting to the previous logic.
    While there turn the hap_enabled check into an ASSERT, since the only
    caller of iommu_share_p2m_table already performs the hap_enabled check
    before calling the function.
    Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
    Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 5e04bf333b954fcfd86eda3d258dc69bcf0586a3
Author: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Date:   Tue Oct 9 16:26:54 2018 +0200

    flask: sort io{port,mem}con entries
    These entries are not always sorted by checkpolicy, so sort them during
    policy load (as is already done for later ocontext additions).
    Reported-by: Nicolas Poirot <nicolas.poirot@xxxxxxxxx>
    Signed-off-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
    Tested-by: Nicolas Poirot <nicolas.poirot@xxxxxxxxx>
    Reviewed-by: Nicolas Poirot <nicolas.poirot@xxxxxxxxx>

commit 27225bbb6d148f6d373a4a89b0dc3f3f5bf4d193
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Oct 9 16:25:35 2018 +0200

    x86/HVM: move vendor independent CPU save/restore logic to shared code
    A few pieces of the handling here are (no longer?) vendor specific, and
    hence there's no point in replicating the code. Zero the full structure
    before calling the save hook, eliminating the need for the hook
    functions to zero individual fields.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx
    Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>

commit 5866b00ce05a7a7c39a0d5eb7f9de4149c5efe8b
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Tue Oct 9 15:06:25 2018 +0100

    tools/libxenstat: Fix SONAME following c/s 57077cc42
    The unstable ABI version is 4.12, not 4.11
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
(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®.