linux/meta-virtualization.git/recipes-kernel, branch master-nxt

python3-dtc: port to Python 3.10

2021-11-11T13:59:11+00:00

Signed-off-by: Ross Burton Signed-off-by: Bruce Ashfield

kernel: add 5.15 fragment enablement

2021-11-09T13:29:32+00:00

5.15 is tested as a kernel now, so we add the .inc to enable fragments. Signed-off-by: Bruce Ashfield

lopper: update to v1.0 and setuptools based project

2021-11-09T02:57:02+00:00

Switching to lopper 1.0 brings us a more standard setuptools based project for install and packaging. This update also fixes the experimental update to master-next, which was incomplete and broken. The only signficant user visible change with this update is that lopper.py is now 'lopper' and any calling recipes need to be updated accordingly. Signed-off-by: Bruce Ashfield

k3s: Add additional required kernel modules

2021-11-08T14:20:32+00:00

Adds the following kernel modules for k3s: * xt-physdev * xt-nflog * xt-limit * nfnetlink-log Without them, the k3s network-policy-controller reports failures in the log related to iptables-restore. Signed-off-by: Richard Neill Signed-off-by: Bruce Ashfield

linux-yocto_virtualization.inc: remove :append and += combination

2021-11-07T03:05:26+00:00

* fixes: KERNEL_FEATURES:append += is not a recommended operator combination, please replace it. Signed-off-by: Martin Jansa Signed-off-by: Bruce Ashfield

lopper: update to master-next

2021-11-03T13:48:00+00:00

Signed-off-by: Bruce Ashfield

global: convert github SRC_URIs to use https protocol

2021-11-02T13:57:03+00:00

github is removing git:// access, and fetches will start experiencing interruptions in service, and eventually will fail completely. bitbake will also begin to warn on github src_uri's that don't use https. So we convert the meta-virt instances to use protocol=https (done using the oe-core contrib conversion script) Signed-off-by: Bruce Ashfield

global: add explicit branch to all SRC_URIs

2021-11-02T13:57:03+00:00

As introduced in the oe-core post: https://lists.openembedded.org/g/openembedded-core/message/157623 SRC_URIs without an explicit branch will generate warnings, and eventually be an error. We run the provided conversion script to make sure that meta-virt is ready for the change. Signed-off-by: Bruce Ashfield

virtualization/config: allow conditional use of yocto-cfg-fragments

2021-10-14T22:29:05+00:00

To help enforce/guide consistent configuration and to avoid duplicating configuration fragments into the meta-virt layer, we leverage a native provider of the yocto-kernel-cache fragment repository. To allow support for kernels that support fragments, but don't have the yocto-kernel-cache in the kernel's SRC_URI, we create two conditional parts of the virtualization configuration. If virtualization is enabled in the distro features, the kernel version matches one of our supported ones, and the kernel inherits kernel-yocto, we add a depedency on the yocto-cfg-fragments-native recipe. That recipe will install the fragment collection to the kernel recipe's native sysroot. We can then check for the kernel-cache on the SRC_URI. If it is present, we use the feature at the standard location. If it is not present, we add the fragment from the native sysroot. While we could always use the native sysroot variant, we want to allow a kernel with a kernel-cache to be the first choice, and provide their own fragments. Signed-off-by: Bruce Ashfield

yocto-cfg-fragments: introduce native provider of configuration fragments

2021-10-14T02:45:55+00:00

To allow the use of the yocto configuration fragments in scenarios where a kernel inherits kernel-yocto or has a custom fragment implementation, but doesn't directly include the yocto-kernel-cache in the kernel SRC_URI, we introduce a native provider of the fragments. This fragment provider is independent of a kernel tree and when added as a dependency to a recipe, the fragments will be placed in: recipe-sysroot-native/kcfg/ These can then be referenced on the SRC_URI or in KERNEL_FEEATURES by using '../recipe-sysroot-native/kcfg' as the relative path to the .scc or .cfg file. In the future, this won't be required as kernel-yocto will always check the native sysroot for fragments, and fragments will always be referenced by relative path from the base of the kernel-cache. Signed-off-by: Bruce Ashfield