JPWO2021211241A5

JPWO2021211241A5 -

Info

Publication number: JPWO2021211241A5
Application number: JP2022554566A
Authority: JP
Publication date: 2024-02-14

Claims

A calculation system,
one or more processors;
when executed by the one or more processors;
executing a first hypervisor that creates one or more guest partitions;
creating a service partition,
initializing a second hypervisor in the service partition using a static system state of the first hypervisor ;
synchronizing at least a portion of the runtime state of the first hypervisor with the second hypervisor, wherein at least a portion of the runtime state of the first hypervisor is synchronized with the second hypervisor; What to do is
intercepting requests for system invariants from the first hypervisor on shared memory;
issuing a reverse hypercall to the second hypervisor to transmit the system invariants to the second hypervisor via the shared memory;
and devirtualizing the second hypervisor from the service partition to replace the first hypervisor. one or more computer readable media having instructions stored thereon;
computing systems, including;

12. Initializing the second hypervisor in the service partition further comprises granting read-only unique access to a particular portion of the one or more computer-readable media of the computing system. The calculation system according to item 1.

The runtime state includes: (1) one or more second level memory page tables that map guest physical memory of the guest partition to host physical memory of the computing system; (2) one or more page frame number databases; or (3) the computing system according to claim 1, comprising at least one of a list of physical devices to be added to a guest partition and an assignment of the list of physical devices.

at least one of the one or more guest partitions includes a privileged parent partition;
the privileged parent partition runs a host operating system or virtualization service module;
the host operating system or the virtualization service module includes an orchestrator configured to coordinate the initialization and synchronization of the second hypervisor;
the first hypervisor enables the orchestrator to intercept certain requests from the second hypervisor to the first hypervisor;
The computing system according to claim 1.

When the orchestrator intercepts a request from the second hypervisor to the first hypervisor, the orchestrator issues a reverse hypercall to the second hypervisor to communicate a portion of the memory page. 5. The computing system of claim 4, shared with the second hypervisor for purposes.

the initial setting of the second hypervisor;
generating a loader block for the second hypervisor by the first hypervisor, the loader block being a logical construct describing at least a portion of the static system state for initialization; including, generating,
obtaining one or more system invariants of the computing system by the orchestrator;
4. Sharing the one or more system invariants with the second hypervisor; and initializing the second hypervisor based on the one or more system invariants. 5. The calculation system described in 5.

7. The computing system of claim 6, wherein the one or more system invariants include one or more features supported by one or more hardware resources of the computing system.

8. The orchestrator obtains the one or more features from at least one of (1) by a hypercall from the first hypervisor or (2) directly from a hardware resource. calculation system.

9. The computing system of claim 8, wherein the orchestrator obtains at least one of the features through a binary interface that discovers or queries hardware capabilities.

Synchronizing the runtime state of the first hypervisor comprises:
collecting runtime state of the first hypervisor by the orchestrator;
sharing the runtime state with the second hypervisor on a reverse hypercall by the orchestrator; and
causing the second hypervisor to replicate the runtime state;
The computing system according to claim 6, comprising:

Collecting the runtime state includes:
receiving, by the first hypervisor, a hypercall invoked by a guest partition;
servicing the hypercall by the first hypervisor; and
recording by the orchestrator the hypercall and a log of actions that occurred during the servicing of the hypercall by the first hypervisor;
and sharing the runtime state includes:
feeding, by the orchestrator, the hypercall to the second hypervisor; and
feeding, by the orchestrator, a log of the actions to the second hypervisor;
The computing system according to claim 10, comprising:

Replicating the runtime state includes:
receiving a reverse hypercall from the orchestrator in the second hypervisor;
switching the context of the guest partition that invoked the reverse hypercall;
processing, at the second hypervisor, a reverse hypercall to reconstruct necessary software state or dormant hardware state; and
informing the orchestrator of completion of the reverse hypercall;
The computing system according to claim 10, comprising:

the parent partition contains the host operating system and virtualization service module;
the virtualization service module is configured to provide virtualization services to at least one other guest partition;
The computing system is further configured to hot restart the virtualization service module without restarting the host operating system.
The calculation system according to claim 3.

Devirtualizing the second hypervisor comprises:
transferring control of physical hardware of the computing system from the first hypervisor to the second hypervisor;
freezing each of the one or more guest partitions;
communicating a final state of the first hypervisor to the second hypervisor;
switching each guest partition to the second hypervisor; and
Unzip each of the guest partitions,
The computing system according to claim 1, comprising:

The computing system of claim 1, wherein the computing system is further configured to hot restart at least one of the one or more guest partitions.

A method for hot restart of a hypervisor of a host implemented by a computing system, the method comprising:
executing a first hypervisor that creates one or more guest partitions;
creating a service partition,
initializing a second hypervisor in the service partition using a static system state of the first hypervisor;
synchronizing at least a portion of the runtime state of the first hypervisor with the second hypervisor, wherein at least a portion of the runtime state of the first hypervisor is synchronized with the second hypervisor; What to do is
intercepting requests for system invariants from the first hypervisor on shared memory;
issuing a reverse hypercall to the second hypervisor to transmit the system invariants to the second hypervisor via the shared memory;
including, synchronizing, and
devirtualizing the second hypervisor from the service partition to replace the first hypervisor;
including methods.

The runtime state includes: (1) one or more second level memory page tables that map guest physical memory of the guest partition to host physical memory of the computing system; (2) one or more page frame number databases; 17. The method of claim 16, comprising at least one of: or (3) a list of physical devices to be added to a guest partition and an assignment of the list of physical devices.

at least one of the one or more guest partitions includes a privileged parent partition;
the privileged parent partition runs a host operating system or virtualization service module;
the host operating system or the virtualization service module includes an orchestrator configured to coordinate the initialization and synchronization of the second hypervisor;
17. The method according to claim 16.

A computer program comprising computer-executable instructions, the computer-executable instructions, when executed by one or more processors of a computing system, comprising:
executing a first hypervisor that creates one or more guest partitions;
creating a service partition,
initializing a second hypervisor in the service partition using a static system state of the first hypervisor;
synchronizing at least a portion of the runtime state of the first hypervisor with the second hypervisor, wherein at least a portion of the runtime state of the first hypervisor is synchronized with the second hypervisor; What to do is
intercepting requests for system invariants from the first hypervisor on shared memory;
issuing a reverse hypercall to the second hypervisor to transmit the system invariants to the second hypervisor via the shared memory;
including, synchronizing, and
devirtualizing the second hypervisor from the service partition to replace the first hypervisor;
A computer program configured to cause the computing system to perform.

Devirtualizing the second hypervisor comprises:
transferring control of physical hardware of the computing system from the first hypervisor to the second hypervisor;
freezing each of the one or more guest partitions;
communicating a final state of the first hypervisor to the second hypervisor;
switching each guest partition to the second hypervisor; and
Unzip each of the guest partitions,
17. The method of claim 16, comprising: