linux/meta-virtualization.git/conf/layer.conf, branch master-next

layer.conf/qemu-system-native: Improve native DISTRO_FEATURE handling

2026-04-28T11:27:58+00:00

OE-Core needs to make some improvements to the way DISTRO_FEATURES is being built but this will break the way meta-virtualization is handling native propagation. Use DISTRO_FEATURES_FILTER_NATIVE which is designed for this. That then means updating the bbappend just to look at DISTRO_FEATURES and to look for both possible values. Signed-off-by: Richard Purdie Signed-off-by: Bruce Ashfield

layer: bump compatibility to wrynose

2026-03-18T03:28:17+00:00

Signed-off-by: Bruce Ashfield

container-dummy-provides: Update to match changes in oe-core

2026-03-14T15:16:57+00:00

OE-Core made changes to the way dummy providers work, update the container-dummy-provides to match them. It now needs a hint in layer.conf to make the core components aware of the presence of the dummy recipe. Signed-off-by: Richard Purdie Signed-off-by: Bruce Ashfield

container-registry: make IMAGE_FEATURES conditional on distro features

2026-03-11T23:34:27+00:00

Move the container-registry IMAGE_FEATURES[validitems] registration from layer.conf into meta-virt-container-cfg.bbclass where it can be gated on DISTRO_FEATURES. The validitems varflag is now only registered when vcontainer or virtualization is in DISTRO_FEATURES. layer.conf is parsed before distro features are known, so inline Python cannot be used there. The bbclass is loaded via USER_CLASSES (deferred parsing) and already handles container profile configuration. Signed-off-by: Bruce Ashfield

vcontainer: add sanity checks and auto-enable virtfs for QEMU

2026-02-09T03:34:12+00:00

Fix virtio-9p (virtfs) support for container-cross-install batch imports which provides ~50x speedup over base64-over-serial. The issue was that native recipes don't see target DISTRO_FEATURES, so qemu-system-native wasn't getting virtfs enabled. Fix by: - layer.conf: Propagate virtualization to DISTRO_FEATURES_NATIVE when vcontainer or virtualization is in target DISTRO_FEATURES - qemu-system-native: Check DISTRO_FEATURES_NATIVE for virtfs enable - container-cross-install: Prepend native sysroot to PATH so vrunner finds the QEMU with virtfs support Signed-off-by: Bruce Ashfield

container-registry: add local OCI registry infrastructure

2026-02-09T03:32:52+00:00

Add container registry support for Yocto container workflows: - container-registry.bbclass with helper functions - container-registry-index.bb generates helper script with baked paths - docker-registry-config.bb for Docker daemon on targets - container-oci-registry-config.bb for Podman/Skopeo/Buildah targets - IMAGE_FEATURES container-registry for easy target configuration Signed-off-by: Bruce Ashfield

cockpit-machines: add recipe

2026-01-06T19:32:39+00:00

`cockpit-machines` is a Cockpit plugin used to provide a web interface to manage virtual machines. Since Cockpit version 242, cockpit-machines has been moved to a dedicated repository. This package is dependent on cockpit package from meta-webserver layer. To test it, access the cockpit-machines UI on the tested target at `https://127.0.0.1:9090/machines`. Signed-off-by: Paul Le Guen de Kerneizon Signed-off-by: Bruce Ashfield

layer.conf: add kubernetes into NON_MULTILIB_RECIPES for x86-64

2025-11-06T04:19:33+00:00

Here is the setting in recipe kubernetes: COMPATIBLE_HOST = '(x86_64.*|arm.*|aarch64.*)-linux' x86 is not support, so add kubernetes into NON_MULTILIB_RECIPES for x86-64 to avoid extending lib32- variant Signed-off-by: Changqing Li Signed-off-by: Bruce Ashfield

runc: start removing 'opencontainers' reference

2025-07-07T15:42:27+00:00

We've only had one type of runc for a while, this is another step in the direction of moving to just 'runc' versus the old runc- variants Signed-off-by: Bruce Ashfield

layer: drop walnascar support

2025-07-07T15:42:27+00:00

Now that the unpackdir changes are in place, we switch our support to only whinlatter. Signed-off-by: Bruce Ashfield