Thanks for posting a way of handling this. I've encountered the same unpredictable device enumeration and had been looking into whether switching the sdhci_iproc driver to PROBE_FORCE_SYNCHRONOUS

Reviewed-by: Christopher Clark <christopher.w.clark@...> Tested-by: Christopher Clark <christopher.w.clark@...> Agreed! Thanks, Luca! Christopher

FYI: Christopher is having a look at these updates. I just wanted to let everyone know that they haven't been missed. Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness

Adding kernel-modules did the trick, the docker daemon issued iptables command now works and supports --to-destination for dnat. Thank-you Bruce for taking the time to explain, I've learned a ton in

In the K3S recipe, we actually have finer grained RRECOMMENDS than the docker recipes (due to the way k3s was developed and integrated). In K3S, I'm currently tracking: RRECOMMENDS:${PN} = "\

I did "bitbake world" build with webOS OSE https://github.com/shr-project/build-webos/tree/honister with it's default DISTRO_FEATUREs and PNBLACKLIST, so not all of meta-virtualization was built, but

Yes, you're spot on! Running the script reviled the following. The issue I'm having now is finding the correct way of including the configs, I tried setting them in my myKernelConfigs.cfg and

In message: [meta-virtualization][hardknott][PATCH] openvswitch: Security fix for CVE-2021-36980 on 29/09/2021 Xu, Yanfei wrote: You are carrying local patches to your ovs recipe that don't match

I've been watching for these as well, but haven't gotten to doing my 'all' builds to trigger them. Out of curiosity, what level of coverage do you end up with on the meta-virt layers ? I'm just

In message: [meta-virtualization] [PATCH] kubernetes: update sed expression on 26/09/2021 kai wrote: Since this wasn't actually doing anything, we could likely drop it now. I remember adding it, and

It'll be the iptables and cgroups options that are causing issues. The standard layers and kernel are extensively tested with meta-virt, so there really shouldn't be something missing. You can also

Thanks for the reply Bruce __ Let me know if these details help? root@generic-arm64:~# uname -r 5.10.46-yocto-standard Only setting these two kernel configs at the

<stephibb=amazon.co.uk@...> wrote: It's your kernel configuration, coupled with the iptables modules available .. but most often, it is a missing kernel module. So without knowing

Hi Luca, Reviewed-by: Bertrand Marquis <bertrand.marquis@...> Cheers Bertrand IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If

Hi Luca, Reviewed-by: Bertrand Marquis <bertrand.marquis@...> Thanks a lot for that :-) Cheers Bertrand IMPORTANT NOTICE: The contents of this email and any attachments are confidential and

The mmc probing order has become unpredictable due to recent linux kernel changes, therefore devices like the raspberry pi that have two mmc interface most of the time can't boot from the hard-coded

Syntax conversion for bbappend linux-yocto_5.10 and linux-yocto-dev inside the raspberrypi dynamic layer. Signed-off-by: Luca Fancellu <luca.fancellu@...> ---

Hello all! The current meta-virtualisation docker is incompatible with the legacy v1.8.7 iptables. Docker version 20.10.3, build 41b3ea7e47