Hi Christopher,I have dropped setting install directory, because it seemed for me to be redundant, but I missed the case, when user customize exec_prefix or nonarch_libdir, so I will apply your

Thanks, Khem. Kamil: Is there any reason that you chose to drop specifying the install directory via the flags passed to EXTRA_OECONF? ie. An alternative would be: rather than remove the

ok, it does look like there's a fix that should be made here, thanks. It took a bit of following to see what's involved, so: There are two recipes in meta-openembedded that do use ${nonarch_libdir}

Add the more recent Xen-related recipes to the list. Signed-off-by: Christopher Clark <christopher.w.clark@...> --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git

Xen's networking for guests is typically configured using bridges and the standalone ifupdown package, which contains a more capable version of the tool than busybox, is needed to configure them,

prelink is no longer default enabled and has been recommended to be disabled since OE-core f9719cc1. Signed-off-by: Christopher Clark <christopher.w.clark@...> ---

Hi Kamil, Reviewed-by: Bertrand Marquis <bertrand.marquis@...> But an empty commit message is not something that I like (more for next time, no need to change this patch). Cheers Bertrand

Hi Kamil, Reviewed-by: Bertrand Marquis <bertrand.marquis@...> Cheers Bertrand

Hi Kamil, Reviewed-by: Bertrand Marquis <bertrand.marquis@...> Cheers Bertrand

Xen build may fail for arm machines that have enabled extra flags, that can be enabled only for specific architecture version, e.g. armv8-2a. Signed-off-by: Kamil Dziezyk <kamil.dziezyk@...> ---

Signed-off-by: Kamil Dziezyk <kamil.dziezyk@...> --- recipes-bsp/grub/grub-efi_%.bbappend | 1 + recipes-bsp/grub/grub-efi_xen.inc | 1 + 2 files changed, 2 insertions(+) create mode 100644

This patch changes the location of xen.conf file, that contains list of kernel modules to be loaded during system boot, to "${nonarch_libdir}". This is done by removing '--with-systemd-modules-load='

Hi Martin, Bruce Apologies for taking a long time to reply to the work on the uxen tools and thanks to both of you for your patches. Ack, and I agree, I would like to get this fixed upstream to retire

<s.mueller-klieser@...> wrote: Good enough for me! I've pushed -next to hardknott. Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the

true, I did not follow, sorry I just put hardknott-next in the build and it looks good. That is all I needed. Thanks a lot for the quick reply and the quick fix! Have a good weekend! Cheers,

Since we already have these changes in master, this is fundamentally a cherrypick / backport request. There are a couple of larger/group patches for the protocol and branch changes, but there's an

Upstream renamed master to main and github will remove the git protocol. Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@...> ---

In message: [meta-virtualization] [PATCH] qemu-package-split.inc: Correct a typo on 01/12/2021 Peter Kjellerstedt wrote: I had noticed this myself, and swear that I fixed it .. but I can't find any

all 13 are merged to hardknott. Bruce In message: [meta-virtualization][hardknott][PATCH 01/13] uxen: update guest tools to 4.1.8 on 01/12/2021 Martin Jansa wrote:

5/5 are now merged to honister. Thanks! Bruce In message: [meta-virtualization][honister][PATCH 1/5] uxen-guest-tools: fix build against kernels 5.4+ on 01/12/2021 Martin Jansa wrote: