meta-virtualization's linux-yocto_virtualization.inc includes cfg/virtio.scc in KERNEL_FEATURES, which is a dependency from yocto-kernel-cache.  However, we do not use yocto-kernel-cache with our custom linux-* recipe, so we're hitting a metadata error because of a missing virtio.scc.  It seems like the creation of linux-%.bbappend (in f2f36a8061c600b35b5f0ce1599d59f1d144a3aa) was intentional to match kernel recipes other than linux-yocto*, which we could benefit from, but the lack of yocto-kernel-cache is problematic with virtio.scc.

Can meta-virtualization provide virtio.scc like it does for the other kernel features to allow decoupling from yocto-kernel-cache?

meta-virtualization used to allow this decoupling by configuring the virtio feature without the yocto-kernel-cache in f1c03f390e95b63d5c2dfba9140d1b07c4d17acf, but that was restructured in 21d8bcdb791a1ea766a3e7e7663c7b6d49bc861a.  The dependency was not required unless you were using linux-yocto, but as of f2f36a8061c60 is now required for all linux-% recipes.  (We just now noticed because our linux recipe has recently been updated to match a kernel version supported by meta-virtualization.

Thanks,

Kyle