Why it exists
Consolidation puts infotainment, vehicle functions and safety supervision on one chip. They have very different criticality, update rates and suppliers — and must not disturb each other.
What it is
A type-1 hypervisor runs directly on the hardware and partitions CPU cores, memory and devices into virtual machines, each with its own OS (e.g. Android, Linux, QNX).
Guest operating systems run in separate VMs above a type-1 hypervisor that runs directly on the hardware.
How it ensures isolation
- Spatial: each VM sees only its memory; the SMMU restricts device DMA.
- Temporal: CPU time and sometimes cache and memory bandwidth are reserved per VM.
- Communication: VMs talk only through defined channels (shared memory, VirtIO).
Best practices
- Keep the hypervisor small; use a certified one for safety-relevant partitions.
- Run the highest-ASIL functions on the safety island, outside the hypervisor.
Common pitfalls
- Shared caches and memory bandwidth breaking timing isolation despite separate cores.