From: Christopher Clark <christopher.clark@...> The Xen hypervisor built for Arm 64-bit targets can be launched with runqemu by providing a Device Tree binary and configuration for Qemu, which

From: Christopher Clark <christopher.clark@...> This device tree tooling is being added as a prequisite for enabling qemuboot to run Xen system images with device trees generated for

This series introduces tools and class structure in the layer for enabling testing Xen system images with Qemu, booting with a device tree that describes the target system. A device tree is required

The SECURITY_FLAGS are already passed into the tools build in HOST_CC_ARCH so this separate case override is not needed. Signed-off-by: Christopher Clark <christopher.w.clark@...> ---

Newer XTF revision works around GCC 11.1 issue 99578 and supplying the correct linker to use fixes the build. Signed-off-by: Christopher Clark <christopher.w.clark@...> Reviewed-by: Bertrand

Ensure that the Xen build system variables EXTRA_CFLAGS_XEN_CORE and EXTRA_CFLAGS_XEN_TOOLS are passed into the compile steps. Update the hypervisor compilation to avoid passing in most compile

Apply patches for the tools and hypervisor to Xen 4.15 and the git recipe and uprev Xen 4.14 to latest stable revision. Retire the previous -Wno-vla-parameter workaround. Signed-off-by: Christopher

Pull in updates from upstream Xen and XTF for GCC 11 and fix passing compiler flags for the Xen hypervisor, tools and test framework. Changes since v1: - for Xen 4.14, drop the previous cherry-picked

For simplicity - compile code in Arm mode without interwork. We could choose Thumb mode as default instead - but a dirty experiment shows that with 90Kb PIEs Thumb code doesn't save even one page.

This warning always exists. I think it is caused by not enabling pie on ARM platform. # For simplicity - compile code in Arm mode without interwork. # We could choose Thumb mode as default instead -

On Wed, Jul 7, 2021 at 3:43 PM Bruce Ashfield via lists.yoctoproject.org <bruce.ashfield=gmail.com@...> wrote: We should also document why this QA warning is safe to skip/ignore

Were these warnings always there ? or has it been something introduced by recent uprevs of crui ? Bruce In message: [meta-virtualization] [PATCH] criu: skip QA checks textrel on 07/07/2021 zangrc

merged. Bruce In message: [meta-virtualization][PATCH] skopeo: fix native skopeo failed if no libdevmapper.so.1.02 on host on 05/07/2021 hongxu wrote:

merged. Bruce In message: [meta-virtualization][PATCH] Revert "nagios-nsca: blacklist recipe due to unsupported libmcrypt" on 05/07/2021 hongxu wrote:

WARNING: criu-3.14+gitAUTOINC+e49ce513c8-r0 do_package_qa: QA Issue: criu: ELF binary /usr/sbin/criu has relocations in .text [textrel] Signed-off-by: Zang Ruochen <zangrc.fnst@...> ---

Oh, yes, I see, thanks Martin very much for your pointing out! Thanks,

<christopher.w.clark@...> wrote: I assume you'll send all three patches in the v2. If you'd like me to apply any of the others before the v2, just let me know. Bruce -- - Thou shalt not

If host does not install libdevmapper.so.1.02, run native skopeo failed: ... $ tmp-glibc/sysroots/x86_64/usr/sbin/skopeo -h |tmp-glibc/sysroots/x86_64/usr/sbin/skopeo.real: error while loading shared

Yes, I see it in:https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/?id=950b24b2d5fe454c9d3a9eab5691753067e4b7d0

Thanks Bruce! BTW is this change merged? Thanks,