P2V Migration Dirty Data Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing P2V migration methods significantly disrupt program execution and user experience due to repeated interruptions during the migration process from a Physical Machine (PM) to a cloud platform, as they require multiple interruptions to ensure data consistency.

Innovation Solution

A method and apparatus for P2V migration that involves transmitting disk data from a PM to create and start a Virtual Machine (VM), acquiring and updating dirty data generated during transmission, and iteratively synchronizing data until the program can be seamlessly transferred to the VM, minimizing interruptions and optimizing user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If disk data is transmitted from PM to create and start VM, then P2V migration is achieved, but program execution is interrupted repeatedly affecting user experience

Engineering Contradiction:
Improvedata consistencyVSAvoidprogram execution continuity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies preliminary action by monitoring and recording dirty data (data changes) during the disk data transmission process from PM to VM. This allows the system to capture all modifications made during migration before the final switch, ensuring data consistency without requiring repeated interruptions. The dirty data is collected and transferred to the VM in advance, so when the program is finally switched from PM to VM, no additional interruptions are needed.

Inventive Principle:
Principle #10Preliminary action

2Manufacturing precision

If repeated interruptions are performed to ensure data consistency, then data accuracy is improved, but migration time and user experience deteriorate

Engineering Contradiction:
Improvedata accuracyVSAvoidmigration time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements continuity of useful action by performing dirty data monitoring and collection continuously during the entire disk data transmission process, rather than stopping the program multiple times. The monitoring operates in the background while the program continues to run on the PM, accumulating all data changes in real-time. This continuous approach ensures data accuracy is maintained while minimizing interruption time, as the final switch to VM can happen in a single operation with all necessary data already prepared.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If dirty data is monitored and transferred iteratively, then data synchronization is improved, but system complexity increases

Engineering Contradiction:
Improvedata synchronizationVSAvoidmigration process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies feedback by implementing a monitoring mechanism that continuously tracks dirty data changes during the migration process. The system receives feedback about which data blocks have been modified and automatically includes them in the transfer to the VM. This feedback loop ensures that the VM receives an accurate and complete set of data changes, improving data synchronization reliability. The feedback mechanism is implemented through file system monitoring and checksum verification, which automatically identify and track modifications without requiring complex manual intervention.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11886902B2Physical-to-virtual migration method and apparatus, and storage medium
Publication Date: 2024.01.30 XIAN ZHONGXING NEW SOFTWARE
  • US11886902B2 patent drawing
  • US11886902B2 patent drawing
  • US11886902B2 patent drawing

AI summary

Disclosed are a Physical to Virtual (P2V) migration method and apparatus, and a storage medium. The method includes that: disk data of a Physical Machine (PM) is transmitted to a server, wherein the disk data is used by the server to create and start a Virtual Machine (VM) based on the disk data of the PM; a first dirty data generated by running of a program on the PM in a transmission process of the disk data of the PM is acquired; the disk data for creating the VM is updated based on the acquired first dirty data; and based on the updated disk data for the VM, the VM is controlled to resume running the program based on a progress of the program.