[Openembedded-architecture] Upstreaming Jailhouse recipe

[Rich Persaud]

On Aug 2, 2019, at 21:48, Bruce Ashfield <bruce.ashfield at gmail.com> wrote:
> 
> 
> 
>> On Fri, Aug 2, 2019 at 9:24 PM Denys Dmytriyenko <denis at denix.org> wrote:
>> Hi,
>> 
>> We got Jailhouse working on several TI platforms and had different versions 
>> of the recipe used internally for couple years before recently adding it to 
>> meta-ti.
>> 
>> Jailhouse is a Linux-based partitioning hypervisor - more details can be found 
>> on its GitHub project page: https://github.com/siemens/jailhouse
>> 
>> I was hoping to get it upstreamed and wondered which layer would be the best 
>> home for it - openembedded-core, meta-virtualization or meta-openembedded?

Since this question is asking whether virtualization can find a home in oe-core or meta-oe:  what would be needed to elevate the "status" of meta-virtualization, relative to the other two layers mentioned above?  Automated test cases, more contributors, more hypervisors, test hardware, humans to analyze test failures, more users, formal support statement, release engineering, ...?

For security and safety certification, a smaller TCB (hardware, firmware, bootloader, hypervisor, (uni)kernel) is desirable.  Firmware is becoming more open (see https://OSFC.io) and could benefit from OE toolchains, e.g. Linux has been used in BIOS and unikernel.  We are getting closer to open FPGA toolchains (Yosys, Migen), which means a potential role for OE build integrity in software-defined hardware, including RISC-V cores.

With the heterogeneity of post-Moore hardware within a single "device", there will be increasing need for reproducible composition of multiple OE images within a single deployable system, at build-time and/or run-time. While the "LinuxCon" brand has been retired, CNCF (containers) and AWS drew 8,000 and 40,000 attendees respectively, to their 2018 events.

At present, virtualization and container teams contribute to meta-virt.  How can we build on the foundations of bitbake and meta-virt, to make OE more attractive to these growing markets?


>> What would be everyone's preference? If there's enough interest, I can get 
>> it cleaned up a bit to remove our specifics and submit to the corresponding 
>> mailing list. Thanks.
> 
> I've had requests for it in meta-virtualization in the past, but just never had enough cycles to complete the work.
> 
> Unless there's a compelling reason to not put it in meta-virt, it would fit nicely in with KVM and Xen as the hypervisor components there.
> 
> Bruce

Agreed.  It would be good to understand how oe-core or meta-oe might be perceived as better homes for Jailhouse than meta-virt, so we can improve meta-virt to address contributor requirements.

Rich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-architecture/attachments/20190809/f4153e8a/attachment.html>