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
Next revision Both sides next revision
eg-virt [2019/04/23 14:38]
m.paolino Main page update, hypervisor requirements added
eg-virt [2019/06/26 14:51]
m.paolino updates after discussion during eg-virt meeting
Line 52: Line 52:
 The discussions of this EG will be done through the public AGL mailing list.  The discussions of this EG will be done through the public AGL mailing list. 
  
-====== Hypervisor requirements ======+====== Hypervisor ​and eCockpit ​requirements ======
  
-Virtualization in the AGL Requirements:​ Eric Shufro, Satpreet Singh (Panasonic)+Virtualization in the AGL Requirements:​ Eric Shufro, Satpreet Singh (Panasonic), LaurentC, Mark Silberger (VW)
  
 1. Vision 1. Vision
- +    * Have an opensource ​project supporting a e-cockpit ​out of the box solution. 
- a. Have an opensoruce ​project supporting a ecockpit ​out of the box solution. +    * Support IVI (android/​AGL),​ cluster (AGL), Telematics (Connectivity), safe RTOS (AutoSAR, RTOS)
- b. Support IVI (android/​AGL),​ cluster (AGL), safe RTOS (AutoSAR, RTOS)+
  
 2. Hypervisor 2. Hypervisor
- +    * ability to virtualize GPU, IOs, networking, CPU and run different virtual machines. 
- a. ability to virtualize GPU, IOs, networking, CPU and run different virtual machines. +    * Support memory separation for each guest 
- b. Support memory separation for each guest +    * Support physical suspend to RAM. 
- c. Support physical suspend to RAM. +    * Inter VM communication (Shared memory, network, character) 
- d. Inter VM communication (Shared memory, network, character) +    * Meet ASIL Safety requirements 
- e. 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 3. System Behavior
- +    * Power management of vehicle micro and main micro 
- a. Power management of vehicle micro and main micro +    * Co-ordinate startup and shutdown of all VMs. 
- b. Co-ordinate startup and shutdown of all VMs. +    * Support early boot using suspend to ram or suspend to disk or other techniques 
- c. 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 4. Goals
- +    * Create standard interfaces for inter VM communication. 
- a. Create standard interfaces for inter VM communication. +    * Create vehicle power moding strategy and interfaces to VM. 
- b. Create vehicle power moding strategy and interfaces to VM. +    * Create a system block architecture with recommended separation of concerns. 
- c. Create a system block architecture with recommended separation of concerns. +    * Standard way of sharing hardware (Virtio) ​is very important for fast prototyping and portability 
- d. Standard way of sharing hardware (Virtio) +    * Standard way of software update including peripheral devices and delta update.
- e. Standard way of software update including peripheral devices and delta update. +
- +
- +
- +
- +
-====== Known efforts for automotive virtualization ====== +
- +
-Currently available hardware platforms enable the implementation of different types of virtualization. This section gathers a list of example efforts in the direction of AGL virtualization. If you are working on a similar project and you want the AGL community to be aware of it, add  the related information here below. +
- +
-  * 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 +
-  * Description - company+
  
  
 +5. HW target
 +    * The new raspberry Pi can be a nice target
eg-virt.txt · Last modified: 2023/04/19 20:46 by megankn