...
Virtual Device API standardization, leading to the definition of the Automotive standard Virtual Platform
(this builds on existing standards like VIRTIO naturally)- Investigate and recommend electrical/software architecture for automotive use-cases, when deployed using virtual-machine technologies.
Next Meeting
Tuesday, January
...
22, 10:00 AM CET
Agenda (preliminary)
- API standardization / virtual platform definition
- Backlog refinement
- Zoom Meeting details:
- Registration link (if you do it before, it saves time)
- Join link
- Meeting password: hvws
Most Active Topics
- Definition of Automotive Virtual Platform (a.k.a. API standardization for Hypervisors in automotive environment, with starting point in VIRTIO)
Backlog (Topic List)
- Deep-dive Memory Buffer sharing (GPU) - invite Eugen Friedrich
- Update Milestones, deliverables, and workplan.
- (started) Concrete use-case, needs input again) Use-cases, architectures and requirements workstream
- Some was added to the AGL publication on virtualization after our most recent review. Re-review, to identify useful/reusable parts. Links at the bottom.
Original sub-topics (Possible focus areas)
- APIs for security: Mandatory Access Control features (in virtualization environments, that is)
- VM management tool
- Instrumentation & tools
- Safety compliance: ISO26262
- Security compliance: Common Criteria, EAL
- System design to optimize Boot Time,
- Boot requirements, e.g. secure boot, integrity check,
- Agree on Terms / Nomenclature
Mailing list & Contribution
Currently we use the general 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 acting project lead, currently: Gunnar Andersson
Sub-topics, with possible dedicated meetings (for prioritization)
- API for security: Mandatory Access Control features (in virtualization)
- VM management tool
- Instrumentation & tools
- Safety compliance: ISO26262
- Security compliance: Common Criteria, EAL
...
Skipped / no longer on backlog
Reactions to Samsung presentation
- Reference implementation: Should be based on which hypervisor(s)?
- → Answer: All are welcome. The companies that do the development will in practice affect the choice(s).
Meeting Minutes (← use link)
Project Pages
...
summary
Children Display
Topic Introduction:
Virtual Device standardization, a.k.a. Automotive Virtual Platform definition
Common Define common I/O devices for hypervisor guests with standardized features and interface, such that device drivers (and thereby systems) are as a consequences systems, virtual-machines) become more portable.
Advantages:
- Device drivers (for paravirtualization) for the (Linux*) kernel don't need to be maintained uniquely for different hypervisors
- Ability to move hypervisor guests between different hypervisor environments
- Definite potential for shared experience and getting the right functionality into the APIs.
- Heterogeneous cross-system testing will strengthen specs and implementation.
- Some potential potential for shared device driver driver implementation across hypervisors across hypervisors (dependent on licenses - open-source, closed-source)
*virtio also supported by BSD, Windows, Fuchsia, and others
...
Samsung Resarch - Automotive Virtualization, presented at Xen Summit 2018.
- VIRTIO v1.0 specification, (and newer git master?) – first start for our investigation into the definition of an Automotive-Wide virtualization platform
- The AGL software defined connected car architecture (a.k.a "AGL virtualization paper")
- PDF (snapshot May 2018) ^^^ NOTE that is an older snapshot of a living paper, (Google Docs edit location).
- Paper analysis/summary written by Nikola Velinov with intro paragraph by Gunnar Andersson – based on May 2018 snapshot.
- UPDATE:→ Study this latest published version (June 2018) from AGL publication page
- PDF (snapshot May 2018)
...