User Tools

Site Tools


eg-virt

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
eg-virt [2018/02/09 12:52]
m.paolino [Group Members]
eg-virt [2023/04/19 20:46] (current)
megankn
Line 1: Line 1:
-====== ​Virtualization ​Expert Group ======+====== ​Software Defined Vehicle ​Expert Group ======
  
-The AGL Virtualization 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 [[http://​events.linuxfoundation.org/​sites/​events/​files/​slides/​vosys_AGLAMM16_2016_9_7_public.pdf|here]]).+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 [[http://​events.linuxfoundation.org/​sites/​events/​files/​slides/​vosys_AGLAMM16_2016_9_7_public.pdf|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). 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).
  
-Today the EG-VIRT expert group is focused on defining the Virtualization platform architecture of AGL. The result of the work of the EG-VIRT group in this direction is this [[https://docs.google.com/document/d/1HpYzClh0nDEocsUHb17X0DxiehsAbCgyWE-P2Wk_RNU/edit?​usp=sharing|white paper]].+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 [[https://www.automotivelinux.org/wp-content/uploads/sites/4/​2018/​06/​agl_software_defined_car_jun18.pdf|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 [[https://​confluence.automotivelinux.org/​x/​JQCsAg | here]]. 
  
  
Line 13: Line 17:
 ====== Meetings ====== ====== Meetings ======
  
-The first EG-VIRT community meeting has been held on January 27th 2017, at 2PM CET.  
  
-Regular meetings are scheduled on Friday 2PM CEST (bi-weekly)To join the discussion, please use the following link:+Regular meetings are scheduled on biweekly on WednesdaysThe upcoming schedule can be found on the [[https://​lists.automotivelinux.org/​g/​agl-dev-community/​calendar | project calendar]].  
 + 
 + 
 + 
 +Join Zoom Meeting 
 +https://​zoom.us/​j/​855006400?​pwd=OER2bGVaVm91VjhKYm83Rk1hZTg2dz09 
 + 
 +Meeting ID: 855 006 400 
 +Passcode772184 
  
-https://​global.gotomeeting.com/​join/​728365005 
  
  
 ===== Meetings Agenda and Report ===== ===== Meetings Agenda and Report =====
  
-Meetings agenda and report can be found at the following wiki page: +Meetings agenda and report can be found on [[https://confluence.automotivelinux.org/​display/​VE/​Meeting+Notes | Confluence]] 
-[[eg-virt-meetings|https://wiki.automotivelinux.org/​eg-virt-meetings]]+
  
  
Line 30: Line 41:
 ====== Group Members ====== ====== Group Members ======
  
-This group is open to people interested in the AGL virtualization architecture and implementation. If you are interested in joining the development efforts or the discussion, put your name here.+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   * Michele Paolino - Virtual Open Systems - m.paolino@virtualopensystems.com
-  * Joel Hoffmann ​Renesas Electronics ​Joel.Hoffmann@renesas.com +  * Matt Spencer ​ARM 
-  * Hariharan A Sasken Technologies ​hariharan.a@sasken.com +  * Laurent Cremmer ​-Carmeq 
-  * Yuichi Kusakabe ​Fujitsu TEN - yuichi.kusakabe@jp.fujitsu.com +  * Mark Silberberger ​Carmeq 
-  * Denys Balatsko - Global Logic denys.balatsko@globallogic.com +  * Joel Catala ​Tuxera 
-  * Christoffer Dall - Linaro - christoffer.dall@linaro.org +  * Eva Rio Tuxera 
-  * Soo-yeon Kang DrimAES ​sykang@drimaes.com +  * Francois Ozog Linaro 
-  * Daniel Bernal ​Arm Inc. daniel.bernal@arm.com +  * Leonardo Garcia ​- Linaro 
-  * Tiejun Chen VMware - tiejunc@vmware.com +  * Mikhail GolubevOpen Synergy ​ 
-  * Name Company - email +  * 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
  
-The discussions of this EG will be done through the public AGL mailing list. +====== Hypervisor and eCockpit requirements ======
  
-====== ALS2017 virtualization related presentations ======+Virtualization in the AGL Requirements:​ Eric Shufro, Satpreet Singh (Panasonic),​ LaurentC, Mark Silberger (VW)
  
-This section lists the EG-VIRT and virtualization related presentation to be held in Tokyo for ALS2017: +1. Vision 
-  [[https://​als2017.sched.com/​event/​AF0V/​how-to-introduce-virtualization-in-agl-objectives-plans-and-targets-for-agl-eg-virt-michele-paolino-virtual-open-systems|How to Introduce Virtualization in AGL? ObjectivesPlans and Targets for AGL EG-VIRT]] - Michele Paolinoslides available here: [[http://​events.linuxfoundation.org/​sites/​events/​files/​slides/​vosys_EG-VIRT_ALS17_2017_6_1_public_0.pdf]] +    * Have an opensource project supporting a e-cockpit out of the box solution. 
-  * [[https://​als2017.sched.com/​event/​AF0M/​an-opensource-low-level-hypervisor-for-agl-dominig-ar-foll-intel-open-source|An OpenSource Low Level Hypervisor for AGL]] - Dominig ar Foll+    * Support IVI (android/AGL)cluster (AGL)Telematics (Connectivity),​ safe RTOS (AutoSAR, RTOS)
  
-====== Known efforts ​for automotive virtualization ======+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%
  
-Currently available hardware platforms enable the implementation of different types of virtualizationThis section gathers a list of example efforts in the direction ​of AGL virtualizationIf you are working on a similar project and you want the AGL community ​to be aware of itadd  the related information here below.+3System 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 (IVIcluster) including safety considerations.
  
-  ​ALS 2016 PoC: AGL, FreeRTOS ​and Ubuntu running on the RCar H3 ([[http://​www.virtualopensystems.com/​en/​solutions/​demos/​vosysmonitor-als2016|link]]- Virtual Open Systems +4. Goals 
-  Description - company+    ​* 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 (Virtiois 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.1518180723.txt.gz · Last modified: 2018/02/09 12:52 by m.paolino