|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-unstable-smoke test] 155778: regressions - FAIL
flight 155778 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/155778/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-arm64-arm64-xl-xsm 8 xen-boot fail REGR. vs. 155584 Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 15 migrate-support-check fail never pass test-armhf-armhf-xl 15 migrate-support-check fail never pass test-armhf-armhf-xl 16 saverestore-support-check fail never pass version targeted for testing: xen a95f31376ba4ae911536c647e1a583d144ccab73 baseline version: xen 25849c8b16f2a5b7fcd0a823e80a5f1b590291f9 Last test of basis 155584 2020-10-09 02:01:25 Z 4 days Failing since 155612 2020-10-09 18:01:22 Z 3 days 29 attempts Testing same since 155778 2020-10-13 14:01:27 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Jason Andryuk <jandryuk@xxxxxxxxx> Juergen Gross <jgross@xxxxxxxx> Nick Rosbrook <rosbrookn@xxxxxxxxxxxx> Nick Rosbrook <rosbrookn@xxxxxxxxx> Roger Pau Monné <roger.pau@xxxxxxxxxx> Trammell Hudson <hudson@xxxxxxxx> Wei Liu <wl@xxxxxxx> jobs: build-arm64-xsm pass build-amd64 pass build-armhf pass build-amd64-libvirt pass test-armhf-armhf-xl pass test-arm64-arm64-xl-xsm fail test-amd64-amd64-xl-qemuu-debianhvm-amd64 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 a95f31376ba4ae911536c647e1a583d144ccab73 Author: Nick Rosbrook <rosbrookn@xxxxxxxxx> Date: Sun Oct 11 19:31:25 2020 -0400 golang/xenlight: standardize generated code comment There is a standard format for generated Go code header comments, as set by [1]. Modify gengotypes.py to follow this standard, and use the additional // source: <IDL file basename> convention used by protoc-gen-go. This change is motivated by the fact that since 41aea82de2, the comment would include the absolute path to libxl_types.idl, therefore creating unintended diffs when generating code across different machines. This approach fixes that problem. [1] https://github.com/golang/go/issues/13560 Signed-off-by: Nick Rosbrook <rosbrookn@xxxxxxxxxxxx> Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxx> commit c60f9e4360ec857bb0164387378e12ae8e66e189 Author: Nick Rosbrook <rosbrookn@xxxxxxxxx> Date: Sun Oct 11 19:31:24 2020 -0400 golang/xenlight: do not hard code libxl dir in gengotypes.py Currently, in order to 'import idl' in gengotypes.py, we derive the path of the libxl source directory from the XEN_ROOT environment variable, and append that to sys.path so python can see idl.py. Since the the recent move of libxl to tools/libs/light, this hard coding breaks the build. Instead, check for the environment variable LIBXL_SRC_DIR, but move this check to a try-except block (with empty except). This simply makes the real error more visible, and does not strictly require that LIBXL_SRC_DIR is used. Finally, update the Makefile to set LIBXL_SRC_DIR rather than XEN_ROOT when calling gengotypes.py. Signed-off-by: Nick Rosbrook <rosbrookn@xxxxxxxxxxxx> Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxx> commit 534b3d09958fdc4df64872c2ab19feb4b1eebc5a Author: Juergen Gross <jgross@xxxxxxxx> Date: Sun Oct 11 14:24:01 2020 +0200 tools/libs/store: add disclaimer to header file regarding ignored options Add a disclaimer to the libxenstore header file that all of the open flags (socket only connection, read only connection) are ignored. Signed-off-by: Juergen Gross <jgross@xxxxxxxx> Acked-by: Wei Liu <wl@xxxxxxx> commit 1b810a9d5a39230e76073b1a753cd2c34ded65fc Author: Jason Andryuk <jandryuk@xxxxxxxxx> Date: Thu Oct 1 19:53:37 2020 -0400 libxl: only query VNC when enabled QEMU without VNC support (configure --disable-vnc) will return an error when VNC is queried over QMP since it does not recognize the QMP command. This will cause libxl to fail starting the domain even if VNC is not enabled. Therefore only query QEMU for VNC support when using VNC, so a VNC-less QEMU will function in this configuration. 'goto out' jumps to the call to device_model_postconfig_done(), the final callback after the chain of vnc queries. This bypasses all the QMP VNC queries. Signed-off-by: Jason Andryuk <jandryuk@xxxxxxxxx> Acked-by: Wei Liu <wl@xxxxxxx> commit 8a62dee9ceff3056c7e0bd9632bac39bee2a51b3 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Oct 2 12:30:34 2020 +0200 x86/vLAPIC: don't leak regs page from vlapic_init() upon error Fixes: 8a981e0bf25e ("Make map_domain_page_global fail") Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 8a71d50ed40bfa78c37722dc11995ac2563662c3 Author: Trammell Hudson <hudson@xxxxxxxx> Date: Fri Oct 2 07:18:21 2020 -0400 efi: Enable booting unified hypervisor/kernel/initrd images This patch adds support for bundling the xen.efi hypervisor, the xen.cfg configuration file, the Linux kernel and initrd, as well as the XSM, and architectural specific files into a single "unified" EFI executable. This allows an administrator to update the components independently without requiring rebuilding xen, as well as to replace the components in an existing image. The resulting EFI executable can be invoked directly from the UEFI Boot Manager, removing the need to use a separate loader like grub as well as removing dependencies on local filesystem access. And since it is a single file, it can be signed and validated by UEFI Secure Boot without requring the shim protocol. It is inspired by systemd-boot's unified kernel technique and borrows the function to locate PE sections from systemd's LGPL'ed code. During EFI boot, Xen looks at its own loaded image to locate the PE sections for the Xen configuration (`.config`), dom0 kernel (`.kernel`), dom0 initrd (`.ramdisk`), and XSM config (`.xsm`), which are included after building xen.efi using objcopy to add named sections for each input file. For x86, the CPU ucode can be included in a section named `.ucode`, which is loaded in the efi_arch_cfg_file_late() stage of the boot process. On ARM systems the Device Tree can be included in a section named `.dtb`, which is loaded during the efi_arch_cfg_file_early() stage of the boot process. Note that the system will fall back to loading files from disk if the named sections do not exist. This allows distributions to continue with the status quo if they want a signed kernel + config, while still allowing a user provided initrd (which is how the shim protocol currently works as well). This patch also adds constness to the section parameter of efi_arch_cfg_file_early() and efi_arch_cfg_file_late(), changes pe_find_section() to use a const CHAR16 section name, and adds pe_name_compare() to match section names. Signed-off-by: Trammell Hudson <hudson@xxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> [Fix ARM build by including pe.init.o] Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 4dced5df761e36fa2561f6f0f6563b3580d95e7f Author: Trammell Hudson <hudson@xxxxxxxx> Date: Fri Oct 2 07:18:20 2020 -0400 efi/boot.c: add handle_file_info() Add a separate function to display the address ranges used by the files and call `efi_arch_handle_module()` on the modules. Signed-off-by: Trammell Hudson <hudson@xxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> commit 04be2c3a067899a3860fc2c7bc7a1599502ed1c5 Author: Trammell Hudson <hudson@xxxxxxxx> Date: Fri Oct 2 07:18:19 2020 -0400 efi/boot.c: add file.need_to_free The config file, kernel, initrd, etc should only be freed if they are allocated with the UEFI allocator. On x86 the ucode, and on ARM the dtb, are also marked as need_to_free when allocated or expanded. This also fixes a memory leak in ARM fdt_increase_size() if there is an error in building the new device tree. Signed-off-by: Trammell Hudson <hudson@xxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit afef39241b66df7d5fd66b07dc13350370a4991a Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Apr 1 15:51:08 2020 +0100 x86/ucode: Trivial further cleanup * Drop unused include in private.h. * Used explicit width integers for Intel header fields. * Adjust comment to better describe the extended header. * Drop unnecessary __packed attribute for AMD header. * Fix types and style. No functional change. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> commit 8d255609930bed04c6436974bd895be9a405d0c1 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri Oct 2 12:20:44 2020 +0100 x86/hvm: Correct error message in check_segment() The error message is wrong (given AMD's older interpretation of what a NUL segment should contain, attribute wise), and actively unhelpful because you only get it in response to a hypercall where the one piece of information you cannot provide is the segment selector. Fix the message to talk about segment attributes, rather than the selector. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> (qemu changes not included)
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |