On Wed, 11 Dec 2019 at 13:58, Adrian Bunk <[email protected]> wrote: > >... > > Creating containers, whilst easier than it ever used to be, does > > usually require elevated permissions and can cause problems with things > > like qemu acceleration and networking. If you've already dealt with > > that, fine but some setups wouldn't have. > >... > > Status quo is that qemu might be broken when the host has a more recent > libdrm than the Yocto release to be built. > > Like the qemu virgl issues with warrior on Fedora 30. >
I wouldn't say that qemu is broken when virgl isn't working. Virgl support is entirely optional, and you have to explicitly request it by passing an option to runqemu. It's also not working on some very old distros like centos 7, but rather than take them off the supported distro list, we simply skip the automated test there, as there is no hope to make it work. Ideas on how to better decouple virgl support from the host GL stack including libdrm (without drastically increasing build times) are welcome. Alex
_______________________________________________ Openembedded-architecture mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
