Xen and the Art of Hypervisor Maintenance
summary
XenServer musters engineering, testing and partner coordination to turn the Xen hypervisor into an enterprise product: a 1,728U lab with 14 km of cable, 1,373 devices and 210 network elements runs 800–3,000 test runs a day and an automated harness called Xen RT that has executed 4 million jobs lifetime and ~250,000 jobs per year. Continuous release pipelines, live patching and VM migration minimize downtime; integration branch holds 7 integration, 30 bugfix and 39 feature patches, while XenServer 8 tracks Xen 4.17 with 87 backports and 8.2 CU1 carries 352 backports. Hardware certification and vendor drivers complete the stack.
AI-written summary · about
chapters (16)
- 0:00Introduction and story
- 1:03Behind the scenes of XenServer
- 3:10Customer priorities and security
- 8:04Our massive testing lab
- 11:10Xen RT test automation
- 12:15Open telemetry and tracing
- 13:36Regression testing and metrics
- 13:58Continuous release pipeline
- 15:22External factors for success
- 16:06XenServer and Xen Project history
- 17:13Patch queue and backports
- 18:58Security features and contributions
- 19:19Hardware compatibility list
- 21:45Guest support and updates
- 22:06Key takeaways for developers
- 23:11Q&A session
related talks
26mXen, XenServer, and XAPI: What's the Difference?
17mBuilding the Rackspace Open Cloud with XenServer and OpenStack
46mSafety-Certifying Open Source Software: The Case of the Xen Hypervisor
30mXenserver-core: What it is, how it is built and how to get involved
40mXen Project Development Update
45mSafety Certifying an Open Source Project: The Example of Xen
33mDelivering continuous deployment of xen-api at cloud scale
44mThe Road to Safety Certification: How the Xen Project is Making Progress within the Auto Industry