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

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

flight 97261 xen-unstable-smoke real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-libvirt     11 guest-start               fail REGR. vs. 96794
 test-amd64-amd64-xl-qemuu-debianhvm-i386 9 debian-hvm-install fail REGR. vs. 
 build-armhf                   5 xen-build                 fail REGR. vs. 96794

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-xl           1 build-check(1)               blocked  n/a

version targeted for testing:
 xen                  1fb0fe97a647549cc1bbe90f15b6cb2fcc3f79b6
baseline version:
 xen                  7da483b0236d8974cc97f81780dcf8e559a63175

Last test of basis    96794  2016-07-08 15:01:26 Z    4 days
Testing same since    97261  2016-07-13 11:00:54 Z    0 days    1 attempts

People who touched revisions under test:
  Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx>
  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
  Juergen Gross <jgross@xxxxxxxx>
  Julien Grall <julien.grall@xxxxxxx>
  Kevin Tian <kevin.tian@xxxxxxxxx>
  Stefano Stabellini <sstabellini@xxxxxxxxxx>
  Wei Liu <wei.liu2@xxxxxxxxxx>

 build-amd64                                                  pass    
 build-armhf                                                  fail    
 build-amd64-libvirt                                          pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 test-armhf-armhf-xl                                          blocked 
 test-amd64-amd64-xl-qemuu-debianhvm-i386                     fail    
 test-amd64-amd64-libvirt                                     fail    

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 1fb0fe97a647549cc1bbe90f15b6cb2fcc3f79b6
Author: Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx>
Date:   Sat Jul 9 07:12:07 2016 +0300

    x86/vmx_update_guest_cr: minor optimization
    Minor optimization @ vmx_update_guest_cr: checks if 
    was modified before actually calling vmx_update_cpu_exec_control(v).
    Signed-off-by: Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx>
    Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx>

commit 22ea8ad02e465e32cd40887c750b55c3a997a288
Author: Juergen Gross <jgross@xxxxxxxx>
Date:   Wed Jul 6 16:55:34 2016 +0200

    libxl: move DEFINE_DEVICE* macros to libxl_internal.h
    In order to be able to have all functions related to a device type in
    a single source file move the macros used to generate device type
    specific functions to libxl_internal.h. Rename the macros as they are
    no longer local to a source file. While at it hide device remove and
    device destroy in one macro as those are always used in pairs. Move
    usage of the macros to the appropriate source files.
    Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit 2c2c33f038c889acc9f73681c09320164516da47
Author: Juergen Gross <jgross@xxxxxxxx>
Date:   Wed Jul 6 16:55:33 2016 +0200

    libxl: refactor domcreate_attach_dtdev() to use device type framework
    Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit 26021d77dc14d441ff3b0094f2fafcc5d18aa599
Author: Juergen Gross <jgross@xxxxxxxx>
Date:   Wed Jul 6 16:55:32 2016 +0200

    libxl: refactor domcreate_attach_pci() to use device type framework
    Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit 74e857c6c7f9dc106fa7a7bbf49a9729f5841ad9
Author: Juergen Gross <jgross@xxxxxxxx>
Date:   Wed Jul 6 16:55:31 2016 +0200

    libxl: add framework for device types
    Instead of duplicate coding for each device type (vtpms, usbctrls, ...)
    especially on domain creation introduce a framework for that purpose.
    Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit 56bac262e097684b20f7753ceb6debe594e9725c
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Wed Jun 8 15:01:02 2016 +0100

    libxl: only issue cpu-add call to QEMU for not present CPU
    Calculate the final bitmap for CPUs to add to avoid having annoying
    error messages complaining those CPUs are already present. Example
    message is like (wrapped):
    libxl: error: libxl_qmp.c:287:qmp_handle_error_response: received an
    error message from QMP server: Unable to add CPU: 0, it already exists
    We can also properly handle error from QMP now.
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Reviewed-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit 01f3193e2e3b9b36bde027f909db496f7211c320
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Fri Jun 3 16:38:32 2016 +0100

    libxl: update vcpus bitmap in retrieved guest config
    ... because the available vcpu bitmap can change during domain life time
    due to cpu hotplug and unplug.
    For QEMU upstream, we interrogate QEMU for the number of vcpus. For
    others, we look directly into xenstore for information.
    Reported-by: Jan Beulich <jbeulich@xxxxxxxx>
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit 324bd8f5dce20d0a1dbbd9480f89673a18e1db53
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Tue Jun 7 10:03:39 2016 +0100

    libxl: introduce libxl__qmp_query_cpus
    It interrogates QEMU for CPUs and update the bitmap accordingly.
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Reviewed-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx>
    Reviewed-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit b173750d2bc2c9b57fda9750309824296bdea932
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Mon Jul 11 12:03:51 2016 +0100

    libxl: libxl_domain_need_memory shouldn't modify b_info
    This function is used to return the memory needed for a guest. It's not
    in a position to modify the b_info passed in (note the _setdefault
    Constify the passed in b_info, use a copy to do the calculation. Mark
    the change in API in libxl.h.
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit 11316d31d6844b17b12890f66fbe03d9069bd489
Author: Wei Liu <wei.liu2@xxxxxxxxxx>
Date:   Mon Jul 11 15:12:57 2016 +0100

    libxl: constify copy and length calculation functions
    These functions are not supposed to modify the passed in parameters.
    Reflect that in function declarations.
    Mark the change in APIs in libxl.h
    Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
    Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

commit e6c0a480eff5a650824a65cca91d3f1646a89f3b
Author: Julien Grall <julien.grall@xxxxxxx>
Date:   Tue Jun 28 17:34:31 2016 +0100

    xen/arm: io: Protect the handlers with a read-write lock
    Currently, accessing the I/O handlers does not require to take a lock
    because new handlers are always added at the end of the array. In a
    follow-up patch, this array will be sort to optimize the look up.
    Given that most of the time the I/O handlers will not be modify,
    using a spinlock will add contention when multiple vCPU are accessing
    the emulated MMIOs. So use a read-write lock to protected the handlers.
    Finally, take the opportunity to re-indent correctly domain_io_init.
    Signed-off-by: Julien Grall <julien.grall@xxxxxxx>
    Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>

commit fdf1c6140420df20ffcdca9a0d7cdd7369fde03a
Author: Julien Grall <julien.grall@xxxxxxx>
Date:   Tue Jun 28 16:51:54 2016 +0100

    xen/arm: gic-v3: No need to sort the Redistributor regions
    The sorting was required by the vGIC emulation until commit
    9b9d51e98edb8c5c731e2d06dfad3633053d88a4 "xen/arm: vgic-v3:
    Correctly retrieve the vCPU associated to a re-distributor".
    Furthermore, the code is buggy because both local variables 'l' and 'r'
    point to the same region.
    So drop the code which sort the Redistributors array.
    Reported-by: Shanker Donthineni <shankerd@xxxxxxxxxxxxxx>
    Signed-off-by: Julien Grall <julien.grall@xxxxxxx>
    Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>

commit 652a11ee2fa710c05df09b21cfeab6bad94e06cc
Author: Julien Grall <julien.grall@xxxxxxx>
Date:   Tue Jun 14 12:50:26 2016 +0100

    xen/arm: map_dev_mmio_region: The iomem permission check should be done on 
    The helper iomem_access_permitted expects MFNs in parameters and not
    GNFs. Thankfully only the hardware domain can call this function and
    it will always be with GFNS == MFNs for now.
    Also, fix the printf to use the MFN range and not the GFN one.
    Signed-off-by: Julien Grall <julien.grall@xxxxxxx>
    Reviewed-by: Shannon Zhao <shannon.zhao@xxxxxxxxxx>
    Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>
(qemu changes not included)

osstest-output mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.