Xen: Open Source Hypervisor Designed for Clouds
summary
Xen claims production stability and wide deployment—Amazon, Rackspace and Verizon use it—and provides a type‑1 hypervisor with a Linux/BSD control domain that hosts drivers, plus optional driver domains (disaggregation) for performance and isolation. Toolstacks include xl, libvirt and XAPI/Zappy which offer live migration, snapshots and resource pools; Remus adds HA. Security uses FLASK-based policies. ARM support (v7/v8) runs the hypervisor in hypervisor mode with far fewer lines of code (~17k vs ~220k on x86).
AI-written summary · about
chapters (38)
- 0:00Intro
- 0:21Russell Pavlicek
- 2:12Zen Stack
- 3:46Old Things
- 5:45Cloud
- 9:37Cloud Virtualization
- 12:26Xen in the Cloud
- 13:33Security
- 15:11Scale
- 16:08Tool stacks
- 17:19Different solutions
- 18:11Zappy
- 19:22Multitenancy
- 20:28Pick what makes sense
- 21:13Orchestration choices
- 22:05Zen
- 22:27Zen Foundation
- 24:55Zen Features
- 26:21Hypervisor Architecture
- 29:32Xen Kernel
- 33:01Dis disaggregation
- 37:21Virtualization types
- 39:02Break brain bleed
- 41:08Configuration
- 43:30User Events
- 45:21De disaggregation
- 45:58Security advantages
- 46:44Red box
- 47:48Arm hypervisor
- 48:05Arm diagram
- 48:34Arm hypervisor mode
- 48:51Kernel space match
- 49:08Device tree
- 49:27Optimal mode
- 50:04Mirage OS
- 50:44Whats next
- 51:09Orchestrators
- 52:34Questions
