Purpose and Rationale

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 three primary work streams currently in development:

  1. Virtual Device API standardization, leading to the definition of the Automotive standard Virtual Platform
    (this naturally builds on existing standards like VIRTIO)

  2. Multi-OS system design on Multi-Core SoCs (with/without virtualisation)
  3. Investigate and recommend electrical/software architecture for automotive use-cases, when deployed using virtual-machine technologies. 

Next Meeting

(green star) Monday, Aug 31, 10:00 AM CE(S)T


General backlog

Meeting Minutes (← use link)

Events / F2F

2019 GENIVI Tech Summit in November (completed)

F2F Meeting (completed)

Backlog (Topic List)

(red star) Review / check consensus on USB chapter of specification + other minor edits (Artem to come back with new info)

Original sub-topics (Possible focus areas)

Mailing list & Contribution

  1. Discussion should use the general genivi-projects mailing list(warning) Start the subject line using: [HVWS]
  2. The Wiki is an open public collaboration area.  Please contribute/improve it as needed.  Improve text, add relate info, links, references! 
    To edit the Wiki, log in or request an account.
  3. Any other process question? - you can contact the acting project lead:  Gunnar Andersson

Done / skipped / no longer on backlog

Project Pages summary

Topic Introduction:
Virtual Device standardization, a.k.a. Automotive Virtual Platform definition

Define common I/O devices for hypervisor guests with standardized features and interface, such that device drivers (and as a consequences systems, virtual-machines) become more portable.


*virtio also 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.

The work is documented here

Other resources and Links

  Related publications and input


Bangalore Technical Summit Agenda (2018 October) (← use link)

Munich AMM Workshop Agenda (2018 April) (← use link)

  ((green star) ^^ includes links to many topic presentations by the participants)