Re: linux-yocto virtualization requires virtio.scc from yocto-kernel-cache
On Fri, Jul 23, 2021 at 2:32 AM Diego Sueiro <diego.sueiro@...> wrote:
Yes .. precisely! I'll reply to both email here, so I'm mixing replies
to Diego and
We had a similar discussion in #meta-virt about a month ago, when some AGL
builds were running into a similar issue. The layout of the includes
for the fragment were intentional, as was the broad nature of the bbappend
Without those fragments, I end up debugging end users' subtle runtime errors for
any number of packages in meta-virt, so having issues pop up when the
fragments can't be found, while annoying, is a useful flag for potential issues.
I resisted making a copy of virtio.cfg available in meta-virt for exactly the
reason Diego is bringing up. Maintaining them in two places is not ideal, and
having them centralized is the goal.
To solve the short term issue as we were talking about in #meta-virt, I did
a couple of things:
A "hack": https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/?h=master-wip&id=40cae93f631e77286de7fa79101abee2f6c04618
But if you use that, you'll need to ensure via other means that you get the
right configuration enabled.
And something that I had wanted to do for a while, which is the actual
solution I'm heading towards.
see commits: https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/?h=master-test&id=44db8ee6ddf7c9eb1b5ffb22e9b83b3840997da9
I still haven't done extensive testing with a lot of different kernels, hence
why I haven't moved them to master yet.
But with those two commits, I can remove all of the fragments in the layer
and rely on the one true reference in the kernel-cache.
meta-virtualization used to allow this decoupling by configuring the virtio
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II