Thin Client VM Launch via Hypervisor Status Check
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional network-based computer architectures face inefficiencies due to underutilization of resources and complex management, particularly in thin or zero client systems that rely on centralized servers for computing power, where virtual machines may not be launched or running, leading to communication failures with users.
Innovation Solution
A computing device with a processor, graphic processing unit, and non-volatile memory that includes a user interface to communicate with virtual machines hosted by a hypervisor, capable of initializing a virtual desktop client locally and sending web-services messages to manage hypervisor functions, such as launching virtual machines using SOAP messages according to WS-MAN specifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If thin or zero clients are used to reduce hardware costs and simplify management, then device complexity and cost are reduced, but reliability deteriorates because virtual machines may not be launched or running at the hypervisor, leading to communication failures
Solution Approach 1:
The system performs preliminary actions by checking whether the virtual machine is launched or running at the hypervisor before attempting to establish communication. The thin client queries the hypervisor status in advance, and if the VM is not running, it automatically triggers a launch request. This preliminary check and preparation prevent communication failures before they occur.
2Loss of energy
If centralized server-based computing is implemented to improve resource utilization, then resource efficiency is improved, but device complexity increases due to the need for hypervisor management and virtual machine coordination
Solution Approach 1:
The thin client is equipped with self-service capabilities to autonomously check the status of virtual machines at the hypervisor and automatically initiate launch requests when needed. This self-service mechanism eliminates the need for manual intervention or complex external management systems, allowing the client to independently resolve VM availability issues while maintaining resource-efficient centralized computing.
3Reliability
If manual monitoring and launching of virtual machines is performed to ensure availability, then reliability is improved, but productivity deteriorates due to time-consuming manual operations
Solution Approach 1:
The system implements an automated feedback mechanism where the thin client continuously monitors the status of virtual machines at the hypervisor. When the VM status is detected as not launched or not running, the system automatically sends a launch request and retries communication. This closed-loop feedback system ensures VM availability without requiring manual monitoring, thereby maintaining reliability while preserving user productivity.
Data Source
AI summary
Certain aspects direct to a computing device for launching a virtual machine at a hypervisor. In certain embodiments, the computing device is a thin client or a zero client, which stores a user interface (UI), a first virtual desktop client (VDC) and a communication module. The UI receives input from a user of the computing device, and initializes the first VDC locally. The first VDC communicates with a first virtual machine (VM) hosted by a hypervisor of a remote computer system, receives desktop video display signals from the first VM, and sends signals associated with input from a user to the VM hosted by the hypervisor. The communication module constructs a first web-services message in accordance with a first web services protocol, and sends the first web-services message to the hypervisor, wherein the first web-services message instructs the hypervisor to perform a hypervisor management function.