-
Notifications
You must be signed in to change notification settings - Fork 116
Change the way we boot the VMM #112
Copy link
Copy link
Open
Labels
MonitorsMonitors and their executionMonitors and their executiondesignInvolves design/architectureInvolves design/architectureenhancementNew feature or requestNew feature or requestfeatureIssues created from the urunc teamIssues created from the urunc team
Metadata
Metadata
Assignees
Labels
MonitorsMonitors and their executionMonitors and their executiondesignInvolves design/architectureInvolves design/architectureenhancementNew feature or requestNew feature or requestfeatureIssues created from the urunc teamIssues created from the urunc team
Type
Projects
Status
Todo
Most modern VMMs are able to execute either over a command line execution or over listening for commands over a socket. Firecracker is a good example of such design, where the VMM process starts and listens on a socket for commands. Sending commands over the socket, we can load the guest kernel in a Firecracker VM, set up network and block interfaces, along with eventually starting the guest. Qemu can work in a similar way with Qemu monitor .
We can leverage this design to save some time on starting up a guest. In more details, the VMM process can start and set up the execution environment for the guest in parallel with the initialization steps of urunc. Subsequently, urunc will simply send the command to start the guest when everything is ready.