Closed mkilivan closed 4 years ago
Fixed by #731
Do you want to have virtio enabled on rpi?
When I've noticed this in webOS I've just removed virtio.cfg in: https://github.com/webosose/meta-webosose/commit/a8d9dff92610ad6e4fd8e40d6d5c89b15542c7cb#diff-6ccf8bc05c2664ecd3a7a651c585b947R12
and when I've asked Bruce about it in IRC, he said that it should be only an warning when KERNEL_DANGLING_FEATURES_WARN_ONLY is enabled:
23:42 < JaMa> zeddii: talking about meta-virt compatibility, is every linux-yocto kernel supposed to have cfg/virtio.scc in kernel-meta? 23:43 < JaMa> zeddii: it's included in http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/?id=21d8bcdb791a1ea766a3e7e7663c7b6d49bc861a but seems like new 5.4 linux-raspberrypi kernel doesn't have this and fails because of it 04:01 < zeddii> JaMa: yes. that's the design. We were talking about this on the list the other day. And it's why I added the ability to make those dangling features a warning. 04:02 < zeddii> (KERNEL_DANGLING_FEATURES_WARN_ONLY) 04:24 < zeddii> that of course doesn't mean things can't be changed, but the error being thrown is known
And from the #yocto on freenode on 2020-09-04 it looks like linux-imx has similar issue, maybe it should be improved somehow in meta-virtualization instead? @zeddii ?
On Tue, Oct 6, 2020 at 11:19 AM shr-project notifications@github.com wrote:
Do you want to have virtio enabled on rpi?
When I've noticed this in webOS I've just removed virtio.cfg in: webosose/meta-webosose@a8d9dff#diff-6ccf8bc05c2664ecd3a7a651c585b947R12 https://github.com/webosose/meta-webosose/commit/a8d9dff92610ad6e4fd8e40d6d5c89b15542c7cb#diff-6ccf8bc05c2664ecd3a7a651c585b947R12
and when I've asked Bruce about it in IRC, he said that it should be only an warning when KERNEL_DANGLING_FEATURES_WARN_ONLY is enabled:
23:42 < JaMa> zeddii: talking about meta-virt compatibility, is every linux-yocto kernel supposed to have cfg/virtio.scc in kernel-meta? 23:43 < JaMa> zeddii: it's included in http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/commit/?id=21d8bcdb791a1ea766a3e7e7663c7b6d49bc861a but seems like new 5.4 linux-raspberrypi kernel doesn't have this and fails because of it 04:01 < zeddii> JaMa: yes. that's the design. We were talking about this on the list the other day. And it's why I added the ability to make those dangling features a warning. 04:02 < zeddii> (KERNEL_DANGLING_FEATURES_WARN_ONLY) 04:24 < zeddii> that of course doesn't mean things can't be changed, but the error being thrown is known
And from the #yocto on freenode on 2020-09-04 it looks like linux-imx has similar issue, maybe it should be improved somehow in meta-virtualization instead? @zeddii https://github.com/zeddii ?
Clearly the default for this is causing meta-virt users some pain, and that's not what I want.
We are caught between asking for a generic kernel bbappend, so the fragments can be used, but it is also picking up kernel's that don't use the fragments.
One option is that I'll switch the default to a warning only, versus the current error.
I'll also see if there's a better way that I can detect if the main kernel meta data is being used, and only trigger the warning/error in that scenario.
Bottom line: I'll fix this so meta-rpi doesn't have to adjust (if it doesn't want to).
Bruce
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/agherzan/meta-raspberrypi/issues/730#issuecomment-704344719, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARSRK4HFI77LTTDDVJ4LETSJMYQBANCNFSM4RYBVYSQ .
--
Description Unable to build the linux-raspberrypi_5.4 branch with virtualization feature enabled.
Steps to reproduce the issue:
dunfell
branchDescribe the results you received: Build failed.
Describe the results you expected: Should build successfully.
Additional information you deem important (e.g. issue happens only occasionally): The issue happens every time.
Additional details (revisions used, host distro, etc.): Host : ubuntu 18.04