VM Live Migration Device State Signature Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current live migration techniques for virtual machines with assigned devices are inefficient, leading to significant downtime due to the need to recreate device profiles and handle varying hardware and firmware versions between source and destination hosts, often resulting in resource wastage or system crashes.
Innovation Solution
A method that involves saving a device state signature before migration and determining its match or mismatch at the destination, allowing for efficient loading or reinitialization of the device state to ensure system functionality, thereby reducing downtime and overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If device state is saved and transferred during live migration, then migration speed is improved, but device compatibility issues arise when hardware configurations differ between source and destination hosts
Solution Approach 1:
The patent performs preliminary actions by saving the device state signature before migration occurs. This allows the destination host to pre-assess compatibility by comparing the saved signature with its hardware configuration, enabling proactive handling of compatibility issues rather than reactive troubleshooting after migration
Solution Approach 2:
The device state signature acts as an intermediary element between the source and destination device states. Instead of directly transferring complex device state data that may cause compatibility conflicts, the patent uses the signature as a lightweight mediator that enables compatibility verification and informed decision-making about state transfer
2Reliability
If device state is recreated during migration, then hardware compatibility is ensured, but significant downtime occurs
Solution Approach 1:
The patent applies partial action by selectively transferring only the device state signature rather than the complete device state. This partial transfer enables compatibility verification without the overhead of full state recreation, reducing downtime while maintaining sufficient information for compatibility assessment
Solution Approach 2:
Instead of recreating the entire device state which is time-consuming, the patent uses a simplified copy - the device state signature - that captures essential compatibility information. This copying approach maintains hardware compatibility verification capability while dramatically reducing the time required compared to full state recreation
3Reliability
If complete device state is transferred during migration, then device functionality is preserved, but resource overhead increases
Solution Approach 1:
The patent extracts only the essential compatibility information (device state signature) from the complete device state. This extraction separates the critical functionality-preserving elements from the redundant data, enabling migration with minimal resource overhead while maintaining device functionality
Solution Approach 2:
By performing preliminary extraction of the device state signature before migration, the patent avoids the resource-intensive process of transferring and processing complete device states. This preliminary action reduces computational and memory resources required during the actual migration operation
Data Source
AI summary
A migration system includes a memory, a physical processor in communication with the memory, a first device, a second device, a first hypervisor at a source location, a second hypervisor at a destination location, a first virtual machine, and a second virtual machine. The first virtual machine includes a guest OS executing on the first hypervisor and a guest driver and the second virtual machine includes the guest OS executing on the second hypervisor and the guest driver. The first and second hypervisors send a request to save a device state to the guest driver in the guest OS executing on the first hypervisor and send a migration notification to the guest OS executing on the second hypervisor. The guest driver saves a state signature in the memory. The guest driver determines a status of the state signature as one of matching the second device and mismatching the second device.