The Road to Safety Certification: How the Xen Project is Making Progress within the Auto Industry
summary
Project aims to make Xen usable in automotive and avionics by getting a safety-certified base rather than a fork, focusing on a dom0-less Xen reference and a ~47,000 lines of code minimal ARM configuration to keep certification tractable. Process changes include split open/closed development, traceability stored in-tree, CI integration for validation, and tooling experiments like Doorstop for requirements. Early reference implementations (embedded, automotive, NASA-backed) exist and feasibility estimates put DAL A work at a few to ten man‑years given expertise.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:17Why Virtualisation
- 2:47History of Xen
- 4:16Embedded Use Cases
- 8:39What does this mean for a project
- 10:29Off of safety certification
- 12:07Two sets of problems
- 15:00Key point
- 16:40The ecosystem
- 18:23What does this mean
- 19:45Initial Safety Certification Scope
- 21:48How are we starting to break order problems
- 23:12Building common understanding
- 24:42Split development model
- 28:44Examples
- 29:28The VModel
- 30:45Open Source Projects
- 31:34Retrofitting
- 32:28Process discipline
- 33:26Traceability
- 33:59Documentation Tools
- 35:44Validation
- 36:50Misra
- 37:34The Experiment
- 37:59Community Scalability
- 38:59Getting to a credible plan
- 39:59User Stories
related talks
45mSafety Certifying an Open Source Project: The Example of Xen
40mThe Xen Safety Concept, a Major Milestone Toward Certification
50mXen Project's Progress Toward Safety Certification
46mSafety-Certifying Open Source Software: The Case of the Xen Hypervisor
40mDom0less and Deterministic: Building Safer Automotive Systems With Xen
40mBOF: Open Source Projects in Safety Critical Applications
35mOpen Sesame! Why Functional Safety is the Master Key to Open the Door for Linux into Automotive
38mZephyr: Learnings From Working on Safety Certification in the Open