The Hypervisor Project follows after two successful workshops at the last two GENIVI All-Member-Meetings and investigates the wide scope of open- source and commercial hypervisor technologies, and addresses challenges in their use. Through collaboration between all vendors, experts and adopters of virtualization technology we can lower the barriers to successful product development. The project drives requirements, standardization for Hypervisor APIs, and other types of investigations to facilitate ECU consolidation, price reduction, and management of mixed-criticality in systems for improved security and functional safety.
You can look below for detailed backlog and topics, but to summarize there are two primary work streams currently in development:
Virtual Device API standardization, leading to the definition of the Automotive standard Virtual Platform
(this builds on existing standards like VIRTIO naturally)
Next Meeting
Agenda:
Currently we use the general genivi-projects mailing list. Start the subject line using: [HVWS]
Please contribute/improve the Wiki. Improve text, add relate info, links, references! To edit the Wiki, log in or request an account.
Any process question? - you can contact the current project lead, currently: Gunnar Andersson
Common I/O devices for hypervisor guests with standardized features and interface, such that device drivers (and thereby systems) are more portable.
Advantages:
*virtio supported by BSD, Windows, Fuchsia, and others
Extending this: Standardizing a contract/standard between guest and hypervisor. Compare the OCI initiatives for containers. Container runtimes → can we have standardized "hypervisor runtime environment" that allows a standards compliant virtual (guest) machine to run.
Compare: Linux Device Tree – ability to discover and configure devices.
Samsung Resarch - Automotive Virtualization, presented at Xen Summit 2018.
( ^^ includes links to many topic presentations by the participants)