Multi-target Post-copy Guest Migration Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current guest migration strategies in virtualized environments face challenges such as prolonged downtime, significant network load, and latency due to the inefficiencies of pre-copy and post-copy migration methods, especially when migrating across multiple hosts, leading to potential timeouts and execution errors.

Innovation Solution

The implementation of a multi-target post-copy guest migration system, where each host that previously hosted a guest registers in a multicast group, allowing for efficient page fault handling by flagging page states and reducing network overhead, enabling the guest to request missing memory pages directly from the host that has the copy, thereby minimizing latency and processing overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional pre-copy or post-copy migration methods are used, then guest migration can be performed, but prolonged downtime and significant network load occur

Engineering Contradiction:
Improvemigration speedVSAvoiddowntime
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by having source hosts proactively push memory pages to potential destination hosts before migration is actually needed. This pre-positioning of data eliminates the need for lengthy pre-copy phases and reduces downtime significantly, as the destination host already has the required pages when migration is initiated.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a migration orchestrator as an intermediary component that coordinates the migration process across multiple hosts. This orchestrator manages the complex interactions between source hosts, destination hosts, and the guest VM, enabling efficient multi-target migration while reducing network load through intelligent routing and coordination.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If memory pages are migrated through multiple intermediary hosts, then migration can occur across different hosts, but latency and network overhead increase

Engineering Contradiction:
Improvemigration flexibilityVSAvoidlatency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system segments the migration process into independent parallel operations where multiple destination hosts can simultaneously receive memory pages from source hosts. This segmentation allows the migration to proceed in parallel rather than sequentially through intermediaries, significantly reducing latency while maintaining the ability to migrate across multiple hosts.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from a linear chain-of-custody migration approach to a multi-dimensional parallel migration architecture. Instead of pages passing sequentially through intermediary hosts, the system enables direct parallel transfers from source to multiple destinations simultaneously, adding a temporal dimension to the migration process that reduces overall latency.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Reliability

If all memory pages are migrated before guest execution, then data consistency is maintained, but migration time increases significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidmigration duration
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The system performs preliminary migration of critical memory pages to destination hosts before the guest VM needs to execute on those hosts. This pre-positioning ensures data consistency is maintained for pages that are migrated, while pages that are not yet migrated are handled through page fault mechanisms, thereby reducing overall migration duration without sacrificing reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of requiring all memory pages to be fully migrated and verified before guest execution, the system performs partial migration of essential pages and allows the guest to start executing. Missing pages are fetched on-demand through page faults, which reduces migration duration significantly while maintaining data consistency for the pages that are migrated.

Inventive Principle:
Principle #16Partial or excessive action

4Productivity

If intermediary hosts are used in the migration chain, then migration can proceed through available hosts, but network overhead and processing complexity increase

Engineering Contradiction:
Improvemigration throughputVSAvoidmigration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the coordination complexity from the individual host migration processes and centralizes it in a migration orchestrator. This extraction allows source hosts and destination hosts to engage in simpler, more direct memory page transfers, reducing the complexity burden on each host while maintaining high migration throughput through centralized coordination.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10552080B2Multi-target post-copy guest migration
Publication Date: 2020.02.04 RED HAT INC
  • US10552080B2 patent drawing
  • US10552080B2 patent drawing
  • US10552080B2 patent drawing

AI summary

Multi-target post-copy guest migration is disclosed. For example, first, second, and third host nodes are associated with respective first, second, and third memories and respective first, second, and third isolated guest managers. An isolated guest, previously migrated from the first host node, executes on the second host node with a first memory page in the first memory and second and third memory pages in the second memory. The isolated guest is requested to migrate to the third host node. The isolated guest executes on the third host node after the third memory page is migrated. The isolated guest requests the first memory page. The third memory is determined to lack the first memory page, and in response, the first and second isolated guest managers are notified that the first memory page is required by the third host resulting in the first memory page being sent to the third host.