Difference between revisions of "Hyperlaunch"

From Xen
(Add link to the posted notes for the Hyperlaunch Design Session at Xen Summit 2021)
(Added link to the System Device Tree specification document)
Line 33: Line 33:
 
* Platform Security Summit 2018 [https://www.platformsecuritysummit.com/2018/videos/ videos]
 
* Platform Security Summit 2018 [https://www.platformsecuritysummit.com/2018/videos/ videos]
 
* Platform Security Summit 2019 [https://www.platformsecuritysummit.com/2019/videos/ videos]
 
* Platform Security Summit 2019 [https://www.platformsecuritysummit.com/2019/videos/ videos]
  +
* [https://github.com/devicetree-org/lopper/blob/3f9f22964bd785949b55fc5d0167c261a1d79c5e/specification/specification.md System Device Tree specification], 16th March 2021
   
 
== Earlier design document revisions ==
 
== Earlier design document revisions ==

Revision as of 18:30, 11 June 2021

Hyperlaunch is a new, flexible system for launching the Xen hypervisor and virtual machines.

The design enables seamless transition for existing systems that require a dom0, and provides a new general capability to build and launch alternative configurations of virtual machines, including support for static partitioning and accelerated start of VMs during host boot, while adhering to the principles of least privilege. It incorporates the existing dom0less functionality, extended to fold in the new developments from the DomB project, with support for both x86 and Arm platform architectures, building upon and replacing the earlier 'late hardware domain' feature for disaggregation of dom0.

Hyperlaunch is designed to be flexible and reusable across multiple use cases, and our aim is to ensure that it is capable, widely exercised, comprehensively tested, and well understood by the Xen community.


DomB mode of dom0less


Related work

Earlier design document revisions