...
Minute takers according to this page
F2F September 24
1. Introduction
Automotive requirements lead to particular choices and needs from the underlying software stack. Existing standards for device drivers in virtualization need to be augmented because they are often not focused on automotive or even embedded, systems. Much of the progression comes from the IT/server consolidation and in the Linux world, some come from virtualization of workstation/desktop systems.
A collection of virtual device driver APIs constitute the defined interface between virtual machines and the virtualization layer, i.e. the hypervisor or virtualization "host system". Together they make up a definition of a virtual platform.
This has a number of advantages:
- Device drivers (for paravirtualization) for the kernel (Linux in particular), don't need to be maintained uniquely for different hypervisors
- Simplify moving hypervisor guests between different hypervisor environments
- Support guest and host interoperability:
- .... Programming against a specification simplifies developing local/custom variants of systems (e.g. Infotainment systems tailored for a certain geographical market)
- .... Simplify moving legacy systems to a virtual environment
- Some potential for shared implementation across guest operating systems
- Some potential for shared implementation across hypervisors with different license models
- Industry shared requirements and potential for shared test-suites
- A common vocabulary and understanding to reduce complexity of virtualization.
- Similarly, guests VMs can be engineered to match the specification.
In comparison, the OCI initiative for containers serves a similar purpose. There are many compatible container runtimes standardized "hypervisor runtime environments" that allow a standards compliant virtual (guest) machine to run with less integration efforts.
Parked questions
- What could a common test suite look like?
-
...
September 17, 2019
Participants:
...