Live Migration Page Tracking via Modification-After-Migration Bits
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current live migration techniques in virtualization environments are inefficient due to the transfer of all memory pages during migration, regardless of updates, leading to increased delay and performance degradation, as there is no existing method to track the state of migrated pages.
Innovation Solution
Introducing a modification-after-migration bit (MAM) in the hypervisor page table to track updated pages, allowing only modified pages to be transferred back during the back-migration process, thereby reducing memory page transfer time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all memory pages are transferred during live migration regardless of updates, then complete migration is ensured, but migration time and system performance are significantly increased
Solution Approach 1:
The system performs preliminary actions by setting modification-after-migration bits in the hypervisor page table before migration occurs. This allows the system to pre-identify which pages will be modified during migration, enabling selective transfer of only those pages afterward, thus reducing overall migration time while ensuring completeness.
Solution Approach 2:
The system implements feedback mechanisms by continuously monitoring and tracking memory page modifications through modification-after-migration bits in the hypervisor page table. This feedback allows the migration system to dynamically identify which pages require transfer, optimizing the migration process by transferring only necessary pages rather than all pages.
2Reliability
If all memory pages are transferred during back-migration, then data consistency is maintained, but transfer time and network bandwidth consumption increase
Solution Approach 1:
The system extracts only the necessary information (modification-after-migration bits) from the hypervisor page table to identify which pages require back-migration. By taking out only the modified pages rather than transferring all pages, the system maintains data consistency while significantly reducing back-migration transfer time and network bandwidth consumption.
Solution Approach 2:
Instead of performing excessive action by transferring all memory pages during back-migration, the system applies partial action by transferring only the subset of pages that were modified during the migration period. This is achieved through tracking modification-after-migration bits, ensuring data consistency is maintained for the pages that actually changed.
3Device complexity
If no tracking mechanism is implemented for migrated pages, then system complexity is reduced, but inefficiency and performance degradation occur
Solution Approach 1:
The system introduces an intermediary mechanism (modification-after-migration bits in the hypervisor page table) that tracks page modifications without significantly increasing overall system complexity. This intermediary allows efficient identification of pages requiring transfer, thereby improving migration efficiency and productivity while maintaining relatively simple system architecture.
Data Source
AI summary
Provided are embodiments of a method for performing live updates. The method includes determining a migration type for a live migration to be performed from a source server to a target server, and performing the live migration from the source server to the target server. The method also includes based on the migration type, maintaining pages to be migrated, tracking modifications in a hypervisor page table, and performing a back-migration based on the migration type. Also provided are embodiments for a system and computer program product for performing live updates.