linux/meta-virtualization.git/recipes-extended/xen/xen-hypervisor.inc, branch hardknott

xen: extend SYSROOT_DIRS to include installed binaries

2020-11-03T21:28:25+00:00

If a recipe DEPENDS on xen we should include its binaries in the sysroot. The do_install task also ships files to /boot and /usr/lib64. Hence, extend SYSROOT_DIRS to include these paths. Signed-off-by: Diego Sueiro Signed-off-by: Bruce Ashfield

xen: run do_deploy after do_compile and do_populate_sysroot

2020-11-03T21:28:24+00:00

When having rm_work and bitbake needs to re-run do_deploy, we need to ensure that the ${B} is re-generated, otherwise the deploy-xen will be empty. Signed-off-by: Diego Sueiro Signed-off-by: Bruce Ashfield

xen: Fix menuconfig and add support for config fragments and diffconfig

2020-08-27T20:28:58+00:00

This patch introduces the following changes: 1. When building in OE environment the linker path needs to be passed when buildind the Kconfig tool in order to get the menuconfig task properly working. 2. By inheriting cml1.bbclass we can drop some environment variables settings in xen-hypervisor.inc for the menuconfig task, and also be able to search for config fragmens and use the diffconfig task. Also, there is no need to have a custom do_menuconfig task anymore. Change-Id: I8d61ec76d92de7d1613b79edf55b4868fe712334 Signed-off-by: Diego Sueiro Signed-off-by: Bruce Ashfield

xen-hypervisor: Check for the right image in uncompressed deploy

2020-04-27T01:48:28+00:00

The deploy for the uncompressed image was checking if a .gz file exists, it should instead check for a straight xen file. Signed-off-by: Corey Minyard Signed-off-by: Jeremy A. Puhlman Signed-off-by: Bruce Ashfield

xen, xen-tools: updates to the deploy task

2020-02-27T21:59:23+00:00

Amend addtask for deploy in both recipes: add deploy before do_build to ensure that it completes before the build step stamp is written. Suggested-by: Bertrand Marquis Add comments explaining the scheduling of the deploy task to both the hypervisor and tools recipes. In the hypervisor build, change deploy to obtain files from ${B} rather than ${D}, since it allows a bbappend to modify boot binary file destinations in do_install without breaking do_deploy. To ensure that a deployed hypervisor has matching tools in any image being built, add a dependency to make sure that the tools have built and been staged first: do_deploy[depends] += "xen-tools:do_populate_sysroot" Also add a dependency to ensure that anything that the tools recipe deploys, such as a XSM policy file, has been deployed first: do_deploy[depends] += "xen-tools:do_deploy" Schedule deploy tasks after populate_sysroot to ensure that deployed binaries match those staged for inclusion in the image rootfs. Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen, xen-tools: separate COMPATIBLE_HOST for hypervisor and tools

2020-02-27T21:59:23+00:00

The tools have broader platform compatibility than the hypervisor. Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen, xen-tools: update recipes for python3

2020-02-27T21:59:23+00:00

Adds patches for packaged scripts to enable deployment with python3 where they have been ported to python 3 upstream. setuptools3 inherits distutils3 which modifies ${B}, so cd ${S} is needed in the do_configure, do_compile and do_install steps. Remove python 2 dependency from the Xen recipes by adding a new separate recipe, xen-python2, for packaging the remaining optional scripts which are yet to be ported to python 3. Package naming in the separate recipe is chosen to support transition back into the xen-tools recipe if the scripts are ported later. Use RSUGGESTS to support inclusion of the xen-python2 scripts in images that include python 2. Drop the remus package python dependency since the script was removed in 2014: commit 5b66f84e37a45038f9e5dae7a5768a5525d1e6ba Add python3 RDEPENDS needed to run xenmon. Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen: separate recipes for hypervisor and tools; switch to git as source

2020-02-27T21:59:23+00:00

This change changes the names of many packages produced: the xen-tools recipe now builds packages previous built by the xen recipe, so the package prefix changes from "xen-" to "xen-tools-". A temporary bbappend is provided for qemu to ease the transition. Multiple motivations for recipe separation: - improves efficiency of incremental build and development - supports building the hypervisor and tools with different toolchains and for different architectures Switch to using a git recipe on the Xen stable branch: - enables easier tracking of critical XSA security updates applied upstream by just advancing SRCREV along the branch Revision has been set to the tip of the stable-4.12 branch, which has the one XSA-312 patch applied on top of RELEASE-4.12.2. The recipe refactor externalizes the block tap components, to enable optional building of blktap in a separate recipe outside xen-tools, needed by OpenXT. xenstored is made a virtual package to support switching between alternative implementations (several exist). Update xen-image-minimal to install the xen-tools package, which replaces what was previously xen-base. Determine the flask policy filename, which is Xen-version specific, using the same method as the Xen build system. qemu: update PACKAGECONFIG[xen] for xen package renaming: allows builds to continue correctly in the meantime while openembedded core and poky are updated. OpenXT ticket reference: OXT-1694 Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield