Virtual Machine Migration Between Hypervisors
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current virtualization technologies, such as VMware and Xen, lack the ability to migrate virtual machines between different hypervisors, limiting workload balancing across systems with varying resource demands and utilization levels.
Innovation Solution
A method for migrating virtual machines by scanning and parsing metadata, generating a target metadata descriptor, and converting file system images between different hypervisor environments using a conversion engine with plug-in components that handle specific hypervisor conversions, allowing virtual machines to run on different hypervisors like VMware and Xen.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If virtualization technologies are designed to run exclusively on specific hardware boxes, then system stability and performance are improved, but adaptability and workload balancing between different hypervisors deteriorate
Solution Approach 1:
The patent introduces a conversion engine as an intermediary component that translates virtual machine images between different hypervisor formats. This mediator enables compatibility between VMware and Xen hypervisors without compromising the stability of either system, allowing virtual machines to migrate between different hypervisor environments while maintaining system reliability.
Solution Approach 2:
The conversion engine provides multi-functional capability by supporting conversion between multiple hypervisor formats (VMware and Xen). This universal approach allows a single system to handle different virtual machine formats, enhancing adaptability while maintaining the specialized functionality of each hypervisor.
2Adaptability or versatility
If virtual machine images are converted between different hypervisors, then adaptability and workload balancing are improved, but system complexity and conversion overhead increase
Solution Approach 1:
The conversion system is segmented into distinct modules: a conversion engine, format-specific plugins for VMware and Xen, and a metadata extraction component. This segmentation reduces overall system complexity by allowing each component to handle specific tasks independently, making the conversion process more manageable and maintainable.
Solution Approach 2:
The system performs preliminary analysis of the source virtual machine image to identify its format and extract necessary metadata before initiating the conversion process. This preliminary action prepares the conversion engine with the information needed to select appropriate conversion parameters, reducing complexity during the actual conversion execution.
3Productivity
If virtual machines are migrated between hypervisors, then workload balancing and resource utilization are improved, but migration time and operational complexity increase
Solution Approach 1:
The conversion engine creates a copy of the virtual machine image in the target hypervisor format while the source virtual machine continues to run. This copying approach allows migration to occur without interrupting service, reducing the effective migration time impact on productivity. The converted image can be activated once ready, enabling seamless workload balancing.
Data Source
AI summary
A method for migrating virtual machines between hypervisors is disclosed. Initially, metadata describing a virtual machine are automatically scanned and parsed. The structure of the metadata of a source virtual machine are automatically analyzed. Elements of this structure are mapped to corresponding entries of a target virtual machine. A target metadata descriptor to be used as part of the target virtual machine is generated. A predefined layout description of the data stored in a file system image of the source virtual machine read. A predefined layout description of the data to be stored in a file system image to be used at the target virtual machine is also read. The data are extracted from the source virtual machine. A template of a file system image for the target virtual system is generated. Storage space corresponding to the target virtual machine is allocated, and the extracted data are inserted into the allocated storage space.