User Tools

Site Tools


eg-virt

Software Defined Vehicle Expert Group

This page is in the process of being deprecated. All content has been moved to Confluence and the info on this page will be deleted by June 1, 2024.

Information about the SDV EG can be found on Confluence. This wiki page is no longer maintained.

The AGL Software Defined Vehicle (SDV) Expert Group (SDV-EG) (formerly known as Virtualization and Containers Expert Group (EG-VIRT)) is responsible to design and implement virtualization solutions for AGL. This expert group has been created from a BoF held in the Munich AMM 2016 meeting (slides available here).

Containers, Hypervisors (both based on Virtualization Extensions and TrustZone) and any other virtualization solution for x86/ARM are considered to be of interest for this Expert Group. Mainline AGL support the KVM hypervisor on the Renesas RCar M3 platform).

The SDV-VIRT expert group has been focused on defining the Virtualization platform architecture of AGL since 2018. The result of the work of the EG-VIRT group in this direction is this white paper.

In 2020 the Expert Group began to focus on making VirtIO available for AGL and various open source hypervisors.

In Feb 2023 the Containers and Mesh EG was merged into Virtualization EG and the new group was renamed the Software Defined Vehicle Expert Group. The legacy Container and Mesh Confluence page can be found here.

For more information about the technical objectives, members involved and target events see the specific section below.

Meetings

Regular meetings are scheduled on biweekly on Wednesdays. The upcoming schedule can be found on the project calendar.

Join Zoom Meeting https://zoom.us/j/855006400?pwd=OER2bGVaVm91VjhKYm83Rk1hZTg2dz09

Meeting ID: 855 006 400 Passcode: 772184

Meetings Agenda and Report

Meetings agenda and report can be found on Confluence

Group Members

This group is open to people interested in the AGL virtualization architecture definition and implementation. If you are interested in joining the development efforts or the discussion, put your name here.

  • Jerry Zhao - Panasonic - Expert Group Lead
  • Francesco Salamida - AWS
  • Nenad Ilic - AWS
  • Michele Paolino - Virtual Open Systems - m.paolino@virtualopensystems.com
  • Matt Spencer - ARM
  • Laurent Cremmer -Carmeq
  • Mark Silberberger - Carmeq
  • Joel Catala - Tuxera
  • Eva Rio - Tuxera
  • Francois Ozog - Linaro
  • Leonardo Garcia - Linaro
  • Mikhail Golubev- Open Synergy
  • Mikhail Zaytsev - MERA
  • Leonid Lazerev - MERA
  • Kenji Hosokawa - ADIT
  • Vijayendra Mohan Agrawal (Vijay) - Wipro
  • Kishore Kanala - Wipro
  • Sachin Gole - FEV
  • Nedeljko Miljevic - AVL
  • Paul Mundt - HARMAN

The discussions of this EG are done through the public AGL mailing list.

Hypervisor and eCockpit requirements

Virtualization in the AGL Requirements: Eric Shufro, Satpreet Singh (Panasonic), LaurentC, Mark Silberger (VW)

1. Vision

  • Have an opensource project supporting a e-cockpit out of the box solution.
  • Support IVI (android/AGL), cluster (AGL), Telematics (Connectivity), safe RTOS (AutoSAR, RTOS)

2. Hypervisor

  • ability to virtualize GPU, IOs, networking, CPU and run different virtual machines.
  • Support memory separation for each guest
  • Support physical suspend to RAM.
  • Inter VM communication (Shared memory, network, character)
  • Meet ASIL Safety requirements
  • OPTEE should be available for all the guests
  • Boot time overhead introduced by the hypervisor should be much less than 25%

3. System Behavior

  • Power management of vehicle micro and main micro
  • Co-ordinate startup and shutdown of all VMs.
  • Support early boot using suspend to ram or suspend to disk or other techniques
  • Interprocessor communication (bootmicro and mainmicro for different systems (IVI, cluster) including safety considerations.

4. Goals

  • Create standard interfaces for inter VM communication.
  • Create vehicle power moding strategy and interfaces to VM.
  • Create a system block architecture with recommended separation of concerns.
  • Standard way of sharing hardware (Virtio) is very important for fast prototyping and portability
  • Standard way of software update including peripheral devices and delta update.

5. HW target

  • AGL Reference Hardware
  • Renesas RCar H3 Starter Kit
  • QEMU
  • new raspberry Pi
eg-virt.txt · Last modified: 2024/05/16 15:42 by wminer