Virtual Machine Conversion for Cross-Hypervisor Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current virtualization technologies lack cross-compatibility, leading to inefficiencies in data centers where computing needs mismatch available resources, resulting in unused spare computing resources being wasted.
Innovation Solution
A system and method that utilizes a virtual desktop infrastructure (VDI) to convert virtual machines from one type to another, enabling compatibility with different hypervisors, allowing for the execution of remote sessions using a second VM image file that is compatible with the destination hypervisor, thereby supporting multiple types of virtualization platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If virtual machines are created using a specific hypervisor's virtual template, then the VM can be executed on that hypervisor, but the VM cannot be executed on other hypervisors due to incompatibility
Solution Approach 1:
The patent introduces a virtualization management server as an intermediary component that mediates between virtual templates and destination hypervisors. This server receives conversion requests, identifies compatibility issues, and automatically converts virtual templates into formats compatible with different hypervisors, thereby resolving the incompatibility problem without requiring direct intervention from users.
Solution Approach 2:
The patent changes the format parameters of virtual machine images and configuration files during conversion. By modifying file formats, configuration structures, and virtual hardware specifications to match the destination hypervisor's requirements, the system enables cross-hypervisor compatibility while maintaining the core virtual machine functionality.
2Productivity
If computing resources are allocated to a specific virtualization platform, then the platform can execute its native virtual machines, but spare computing resources cannot be utilized by other virtualization platforms
Solution Approach 1:
The patent enables computing resources to serve multiple virtualization platforms through the conversion capability. A single physical server can host virtual machines for different hypervisors by converting templates as needed, making the computing resources universal and adaptable to various virtualization platforms rather than being dedicated to a single platform.
Solution Approach 2:
The system performs preliminary conversion of virtual templates to compatible formats before execution on the destination hypervisor. By pre-converting templates and preparing compatibility layers in advance, the system ensures that spare computing resources can be quickly allocated to different virtualization platforms without delay.
3Adaptability or versatility
If virtual machine templates are converted between different hypervisor formats, then cross-compatibility is achieved, but conversion time and processing overhead increase
Solution Approach 1:
The patent performs conversion operations in advance before the virtual machine needs to be executed on the destination hypervisor. By converting templates proactively and storing them in advance, the system minimizes conversion time during actual deployment and avoids delays during critical execution phases.
Solution Approach 2:
The system prepares conversion buffers and intermediate formats in advance to cushion against conversion delays. By maintaining pre-converted template versions and using intermediate representation formats, the system reduces the time required for actual conversion operations when needed.
Data Source
AI summary
Disclosed are systems and methods for executing a remote session in a virtualized environment. The described technique may be used when handling a request to launch a remote session using a specified virtual template. A virtual machine (VM) type associated with the virtual template and that indicates hypervisor compatibility of the virtual template may be determined. A destination hypervisor is selected for executing the remote session. If VM type is not compatible for execution on the destination hypervisor, a converted, native VM image file is generated which is compatible with the destination hypervisor. The remote session is then launched on the destination hypervisor using another VM executed using the converted VM image file.


