Difference between revisions of "Hyperlaunch"

From Xen
m
(Tag: Undo)
m
 
(One intermediate revision by the same user not shown)
Line 17: Line 17:
 
=== Implementation ===
 
=== Implementation ===
   
  +
* [https://lists.xenproject.org/archives/html/xen-devel/2024-08/msg01434.html Version 4 patch series: Boot modules for Hyperlaunch] contains the fourth version of changes proposed to the Xen Hypervisor towards integrating Hyperlaunch. This v4 series is initial integration work rather than a full Hyperlaunch feature implementation -- see the [https://lists.xenproject.org/archives/html/xen-devel/2022-07/msg00345.html earlier Version 1 series] for a posted full implementation of the Hyperlaunch feature.
 
* [https://lists.xenproject.org/archives/html/xen-devel/2023-06/msg01870.html Slides and notes from Design Session at Xen Summit 2023]
 
* [https://lists.xenproject.org/archives/html/xen-devel/2023-06/msg01870.html Slides and notes from Design Session at Xen Summit 2023]
 
* [https://lists.xenproject.org/archives/html/xen-devel/2022-07/msg00345.html Version 1 patch series] posted to [https://lists.xenproject.org/archives/html/xen-devel/ xen-devel mailing list] in July 2022
 
* [https://lists.xenproject.org/archives/html/xen-devel/2022-07/msg00345.html Version 1 patch series] posted to [https://lists.xenproject.org/archives/html/xen-devel/ xen-devel mailing list] in July 2022

Latest revision as of 20:53, 12 September 2024

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.

Implementation


DomB mode of dom0less


Related work

Earlier design document revisions