Virtualization
Description
Environment
Activity
I propose closing this issue and opening any specific issues that are found from now on.
The description of this issue has been modified to reflect a more generic activity which targets virtualization.
This activity is discussed in EG-VIRT.
Assigned to Virtualization Expert Group. The EG should consider either closing this project and create something more manageable in terms of a project backlog or creating sub tasks for the Epic.
Walt, All,
Is there a specific reason why in this SPEC only XEN is considered?
Although with different characteristics, I think other open source hypervisors, such as KVM, can be used for the same purpose. Therefore if this SPEC, as the name suggests, is intended to generically add the ability to run VMs in AGL, maybe there is a need to be a bit more generic in the SPEC description.
Details
Details
Assignee
Reporter
Labels
Components
Priority
MinorEpic Name
Virtualization can be used to provide HW isolation (memory, interrupts, etc) as well as to achieve Electronic Control Unit (ECU) functions portability and consolidation (e.g., soft ADAS + IVI + instrument cluster on the same platform). The recent availability of automotive platforms/SoCs with virtualization extensions, makes the use of virtualization in automotive possible. However, virtualization can be implemented through type-1/type-2 hypervisors, containers or resources partition solutions. All of them comes with different characteristics, strengths and shortcomings.
The objective of this issue is to provide one (or more) open source virtualization solution(s) for AGL, which provides the best trade off between performance, security, safety, and where needed certifiability, RT responsiveness and HW acceleration.
The activities to bring virtualization in AGL include:
Definition of Requirements, use cases and AGL specifications (in cooperation with AGL SAT)
Existing technology evaluation
Iterative Proof of concepts development, starting from basics
Testing