Virtualization with Zephyr & Xen for Embedded Safety Systems
summary
Zephyr acts as a dom0 on Xen for Arm, boots on Renesas H3, starts a guest Linux via u-boot as per-domain bootloader, and demonstrates a thin dom0 architecture separating control from hardware domains. Upstream adds hypercall wrappers, enlightened page mapping, a paravirtual console and grant-table support; zenbus and console/daemon work remain pending. Known blockers include Apache/GPL licensing frictions, Zephyr static configuration assumptions that hinder runtime remapping, and slow review cycles for Xen-related patches.
AI-written summary · about
chapters (8)
- 0:00Introduction to virtualization
- 1:34Xen and dom0 architecture
- 3:20Xen dom0 with Zephyr
- 5:43Zephyr dom0 implementation
- 9:03Current development progress
- 13:12Development challenges
- 15:35Status and future goals
- 19:44Q&A and discussion
related talks
33mZephyr‑Based VIRTIO Backend on Xen: Toward Open Source Functional Safety
40mDom0less and Deterministic: Building Safer Automotive Systems With Xen
18mZVM: Zephyr-based Virtual Machine
41mSecuring Your Xen-Based Cloud
39mThe Hypervisor Hierarchy: Why Architecture Matters for Performance, Security, and Flexibility
27mZephyr and Trusted Execution Environments
41mUserspace in Zephyr: Overview and Practicality
27mvTZ: Virtualizing ARM TrustZone