Organizing of the Domain-interaction Hypervisor project, with inititial focus on the full-day AMM Workshop.
Next Meeting
Tuesday, April 10, 10:00 AM CET
Agenda:
- Workshop agenda topics assignment (continuation), review of topics schedule
- Webex Link
Meeting password: hvws
AMM Workshop Schedule (Topic name & Responsible & Timeslot)
- Workshop introduction and intention 9:00-9:05 5mn
- presented by: Gunnar (GENIVI), Sang-Bum (Perseus)
- History of HVs 20mn presentation 9:05-9:25
- Introduction to XEN project – 9.20-->
- by: Lars Kurth (Xen project)
- Market Overview 20mn presentation 9:40-10:00 (->9.50-10.15)
- presented by:Franz Walkembach (SysGo)
- includes an intro to certification
- HV design and implementation 10mn + 15mn presentation + discussion 10:20-10:45
- Introduced by: Ralph (Open Synergy)
>>>> short break 15mn 10:45-11:00 CET
- Requirements gathering 10mn intro + 10mn discussion 11:00-11:20
- HV vendors asking OEMs/adopters/customers/etc to clarify technical requirements
- Introduced by: Matti (Open Synergy)
- Virtualization for Multi-core, SoC peripheral hardware and special- purpose CPUs 10mn intro + 10mn discussion 11:20-11:40
- Introduced by:Artem (EPAM)
- Audio system design with HVs 10mn intro + 10mn discussion 11:40-12:00
- Introduced by: Artem (EPAM)
- Standardization of hypervisor APIs (virtio and friends) 10mn intro + 10mn discussion 12:00-12:20
- Introduced by: Matti (Open Synergy) (virtio intro + what's needed?) + ?
- *morning wrapup* 12:20-12:30
- Agree on outcome, actions, topics for future project, etc.
>>>> lunch break 12:30-14:00
- Graphics/GPU Sharing (in relation to GSHA project) 10mn intro + 15mn discussion 14:30-14:55
- Introduced by: looking for volunteer to introduce the topic
- Artem? Alex? (EPAM)
- (Cyber-)Security enhancements based on virtualization 10mn intro + 20mn discussion
14:55-15:2515:30 - 15:45 Break
- Health/Debugging/Analysis/Logging (in relation to SHDA project) 5mn intro + 10mn discussion
15:55-16:15- Introduced by: Gunnar Andersson (GENIVI)
- *afternoon wrapup* 16:15-16:30
- Agree on outcome, actions, topics for future project, etc.
BACKUP TOPICS
- Terms / Nomenclature?
- Hypervisor project organization (post-AMM)
- How can reliability & safety be quantified?
- System design to optimize Boot Time,
- Boot requirements, e.g. secure boot, integrity check,
- System design and working with HVs from users/system integrator's perspective.
- Defining next steps + Hypervisor Project.
- 14:00-14:20 Performance comparison between open source software based hypervisors on ARM SoC 10mn intro + 10mn discussion
Topic Introduction
- Informative and teaching everyone to a similar level of understanding
- Technical neutral information, no sales pitch
- Try to open questions for discussion
- Define what is the remaining problem
- Technology needs improvement?
- Uncertainties?
- Information/documentation/lacking understanding?
- ....
- Suggestion:
- Final slide could be a list of questions (to the workshop participants)
AMM Workshop Agenda (Topic name & Responsible)
This is a workshop session spanning several hours. We expect significant participation from all attendees. Each topic should have a short introduction (maximum 10 minutes) followed by interactive discussion. Individual topics should be introduced by a variety of Hypervisor vendors and other experts, such as OpenSynergy and Perseus.
Discussion topics will include:
- Workshop introduction and intention
- Introduced by: Gunnar (GENIVI), Sang-Bum (Perseus)
- History of HVs
- Introduction to XEN project
- by: Lars (Xen) (TBC by Sang-bum)
- Market Overview
- by:Franz Walkembach (SysGo)
- includes an intro to certification
- Requirements gathering
- HV vendors asking OEMs/adopters/customers/etc to clarify technical requirements
- Introduced by: Matti (Open Synergy)
- Performance comparison between open source software based hypervisors on ARM SoC
- HV design and implementation
- Virtualization for Multi-core, SoC peripheral hardware and special-purpose CPUs
- Introduced by:Artem (EPAM) + input on Samsung roadmap (Sang bum)
- Standardization of hypervisor APIs (virtio and friends)
- Introduced by: Open Synergy (virtio intro + what's needed?) + ?
- How can reliability & safety be quantified?
- Introduced by:
- - how to invite experts? TUV/similar?
- Audio system design with HVs
- Introduced by: Artem (EPAM)
- Discussing GENIVI AudioManager extensions
- Graphics/GPU Sharing (in relation to GSHA project)
- possibly show-and-tell multiple vendors?
- Introduced by: - reaching out to Renesas ?
- Health/Debugging/Analysis/Logging (in relation to SHDA project)
- Introduced by:
- (Cyber-)Security enhancements based on virtualization
- System design and working with HVs from users/system integrator's perspective.
- Introduced by:
- ? tier-1 or OEM leading discussion?
- Hardware integration. Communication issues between vendors?
AMM Workshop Agenda Topics (brainstorm and more details)
- Requirements gathering
- Requests from HV vendors for OEMs/adopters/customers/etc to clarify technical requirements,
e.g. on particular driver, performance, reliability, safety. - Central device driver management?
- ^^ Lead/intro by Sang-Bum
- i.e. HV+BSP supporting hardware register access arbitration.
- ...?
- Even possible without this? What would be design patterns to use if the HV is not giving the hardware virtualization you need.
- BSPs available vs. needed
- Unikernel support
- e.g. tested/demonstrated
- any special matching needed between HV and unikernel (para-virtualization) – likely not...
- (Maybe in particular, how is reliability & safety quantified?)
Boils down to: Several safety related parts brought together - how to design (and evaluate) the total system. - Footprint
- Memory usage
- # Lines of code (auditing/reliability/trust...)
- Training / informative materials?
- Vendor-independent
- From users/system integrator's perspective.
- What can be done today, what can't be done today
- Consequences of para virt or hardware support for virtualization, and related BSP design
- Connection between "management/sales" slides and the very detailed HV documentation. Knowledge required in the gap here.
- Cross-domain architectures, examples, recommendations
- (repeated from above) Boils down to: Several safety related parts brought together - how to design (and evaluate) the total system.
- (repeated from above) Consequences of para virt or hardware support for virtualization, and related BSP design
- Is design even possible without virtualized hardware? Design patterns to coordinate access if the HV is not giving the hardware virtualization you need?
- 12 factors for service-oriented platforms.
- Required technology demonstrations
- Market/Technology survey
- Requirements survey - Questionnaire (to OEMs)
- Results could be statistics/anonymized if needed.
- Start work on this questions list.
- Feature evaluation
- Compare features
- Separate BSPs - paravirt or hardware virt support?
- ... or simply list "what types of features can a Hypervisor have"
- Comparing types of HV / key characteristics?
- Graphics/GPU Sharing (in relation to GSHA project)
- What things are hardware dependent?
- How to share graphics buffers?
- Health/Debugging/Analysis/Logging (in relation to SHDA project
- Audio...
- Past approaches are known and can be discussed (Sang-Bum)
- e.g. paravirt devices
- audio mixing in operating system can handle it instead of paravirtualized drivers
- Complete architecture idea, e.g. with GENIVI AudioManager
- One hardware run Cluster
- How to minimize impact on the development process when using HVs
- Glossary/terms - does everyone have the same understanding of terms?
Related introduction from OpenSynergy at