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

k3s-host: set virtual-runc as container runtime

2026-04-06T23:49:24+00:00

The k3s-host container profile had VIRTUAL-RUNTIME_container_runtime set to empty, which meant no OCI runtime (runc or crun) was installed. containerd's RDEPENDS uses this variable to pull in the runtime, so k3s pods failed with "runc: executable file not found in $PATH". Set to virtual-runc which is what k3s expects. The k3s-node profile inherits from k3s-host so it gets the fix too. Signed-off-by: Bruce Ashfield

vruntime, vrunner, conftest: fix multiconfig and batch import issues

2026-04-06T23:48:37+00:00

vruntime.conf: - Reset all VIRTUAL-RUNTIME_container_* variables to prevent CONTAINER_PROFILE selections from leaking into vruntime multiconfigs (e.g., podman profile pulling netavark into vruntime builds) - Disable ptest for glib-2.0 — its -ptest RDEPENDS chain (python3-dbusmock -> python3-pygobject -> cairo -> fontconfig) pulls the entire graphics stack which is masked in vruntime - OE-core commit 159148f4de2 replaced DISTRO_FEATURES_BACKFILL_CONSIDERED with DISTRO_FEATURES_OPTED_OUT. The old variable no longer has any effect, which meant ptest, gobject-introspection-data, wayland, and other features were no longer being blocked in vruntime builds. This caused glib-2.0's ptest RDEPENDS to pull in the cairo → fontconfig → freetype graphics stack, which is masked by the vruntime BBMASK. - Set PREFERRED_PROVIDER_virtual/runc with strong assignment to ensure the unified runc recipe is used vrunner.sh: - Fix batch import exit code handling: wrap import chain in subshell and make the images listing best-effort. The previous '&& podman images' caused false failures when podman images couldn't initialize its network backend. Using 'exit' was also wrong as the command runs inside PID 1 init's eval — exit kills init causing kernel panic. vpdmn-rootfs-image.bb: - Switch from netavark to CNI networking — netavark's dependency chain (nmap -> libpcap -> bluez5 -> python3-pygobject -> cairo) cannot be built under the vruntime BBMASK environment - Add nsswitch.conf override (files-only backend) to prevent libnss_systemd segfaults — the vruntime VM uses busybox init with no systemd running, but libnss_systemd.so is pulled in as a dependency and segfaults on NSS resolution vdkr-rootfs-image.bb: - Document skopeo requirement for batch import conftest.py: - Add --k3s-timeout option and k3s/multinode markers for upcoming K3s test suite Signed-off-by: Bruce Ashfield

conf/distro: add build profile configuration fragments

2026-04-05T02:09:58+00:00

Add includable configuration fragments that replace manual DISTRO_FEATURES, CONTAINER_PROFILE, and related settings in local.conf. Fragments are organized as a base + composable deltas: - meta-virt-host.conf: base for all virtualization work (virtualization, systemd, seccomp, vmsep, vcontainer, BBMULTICONFIG) - container-host-{docker,podman,containerd,k3s,k3s-node}.conf: container engine profiles setting CONTAINER_PROFILE and profile-specific DISTRO_FEATURES - xen-host.conf: Xen hypervisor support (xen, vxn distro features, xen-image-minimal packages) - meta-virt-dev.conf: QEMU development settings (IMAGE_FSTYPES, QB_MEM, debug image features) - container-registry.conf: local dev registry defaults (insecure localhost:5000) Profiles are pure deltas and do not auto-include the base to avoid BitBake duplicate inclusion warnings. Users include meta-virt-host.conf first, then add profile fragments. The BUILD_PROFILE variable enables single-line profile switching. Usage in local.conf: require conf/distro/include/meta-virt-host.conf BUILD_PROFILE ?= "podman" require conf/distro/include/container-host-${BUILD_PROFILE}.conf Tested with podman, docker, and xen builds. Signed-off-by: Bruce Ashfield

libibverbs: remove obsolete recipe

2026-03-24T03:15:41+00:00

libibverbs has been superseded by rdma-core in OE-core since 2017. The only consumer was ceph, which builds with -DWITH_RDMA=OFF making the dependency unnecessary. Remove the recipe and its vruntime bbmask entry. 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: use FEATURE_PACKAGES for IMAGE_FEATURES validation

2026-03-12T19:18:50+00:00

Move FEATURE_PACKAGES_container-registry from container-image-host.bb to meta-virt-container.inc so it is available to all image recipes. image.bbclass check_image_features() auto-discovers FEATURE_PACKAGES_* variables as valid image features (line 72), so defining the variable globally is sufficient — no IMAGE_FEATURES[validitems] needed. This avoids the signature pollution that IMAGE_FEATURES[validitems] causes when set globally, while allowing container-registry to be used as an IMAGE_FEATURES value in any image recipe. 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

conf/vruntime: exclude backfill distro features

2026-03-03T18:11:12+00:00

Block backfill features not needed by container runtime environments. OE-core's DISTRO_FEATURES_BACKFILL auto-appends these to DISTRO_FEATURES unless explicitly listed here. Without this, gobject-introspection-data enables python3-pygobject (which DEPENDS on cairo), and wayland enables pygobject's cairo PACKAGECONFIG — both are masked in vruntime builds. We are using: ISTRO_FEATURES_BACKFILL_CONSIDERED = "pulseaudio gobject-introspection-data opengl ptest multiarch wayland vulkan" Signed-off-by: Bruce Ashfield

linux-yocto: add vxn distro feature and Xen PV kernel config

2026-02-26T01:05:01+00:00

Add 'vxn' to DISTRO_FEATURES in vruntime.conf to enable Xen PV guest kernel configuration. When set, linux-yocto_virtualization.inc includes vxn.cfg which enables Xen PVH frontend drivers and the 9p Xen transport (NET_9P_XEN). The base 9p stack comes from the existing vcontainer feature via cfg/container.scc. Signed-off-by: Bruce Ashfield