Hypervisor Feature-Driven Backend Device Switching

Solution Overview

Problem

Current virtual machine systems require cumbersome and inefficient manual intervention by system administrators to switch backend devices, as guest operating systems lack transparency and autonomy in accessing devices with desired features, leading to inefficient resource allocation and operation.

Innovation Solution

A feature-driven mechanism is implemented within the hypervisor to automatically switch backend devices based on predefined conditions, allowing seamless transitions without administrator intervention, using a device manager that tracks device features and switching criteria in a configuration table, ensuring transparent operations for the guest.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual intervention by system administrator is used to switch backend devices, then device switching can be performed, but the operation becomes cumbersome and inefficient

Engineering Contradiction:

Improvebackend device switching operationVSAvoidtime for administrator intervention

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The system enables self-service by allowing the guest operating system to autonomously request backend device switching based on its own needs. The guest OS can indicate when it requires a different backend device feature, and the hypervisor automatically processes these requests without requiring system administrator intervention, thus making the system serve itself rather than relying on external manual control.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms where the guest operating system provides information about its device requirements to the hypervisor. The hypervisor monitors these requests and automatically responds by switching backend devices accordingly. This closed-loop feedback system eliminates the need for manual administrator intervention while ensuring the guest's needs are met.

Inventive Principle:

Principle #23Feedback

2Adaptability or versatility

If hotplug operations are used to switch backend devices, then device switching is possible, but the operation is not transparent to the guest

Engineering Contradiction:

Improvebackend device switching capabilityVSAvoidtransparency to guest

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The hypervisor acts as an intermediary between the guest operating system and the backend devices. It abstracts the complex hotplug operations from the guest by handling device switching in the background. The guest interacts only with the hypervisor's simplified interface, while the hypervisor manages the actual device transitions, making the operation transparent to the guest.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the device switching process into two distinct layers: the guest operating system layer that makes high-level feature requests, and the hypervisor layer that handles the detailed device switching operations. This segmentation allows the guest to operate without knowledge of the underlying complexity while the hypervisor manages the actual device transitions seamlessly.

Inventive Principle:

Principle #1Segmentation

3Reliability

If system administrator manually manages backend devices, then device allocation can be controlled, but resource allocation efficiency decreases

Engineering Contradiction:

Improvedevice allocation controlVSAvoidresource allocation efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system enables self-service by allowing the guest operating system to autonomously request backend device switching based on its own needs. The guest OS can indicate when it requires a different backend device feature, and the hypervisor automatically processes these requests without requiring system administrator intervention, thus making the system serve itself rather than relying on external manual control.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms where the guest operating system provides information about its device requirements to the hypervisor. The hypervisor monitors these requests and automatically responds by switching backend devices accordingly. This closed-loop feedback system eliminates the need for manual administrator intervention while ensuring the guest's needs are met.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS9563456B2Feature driven backend switching

Publication Date: 2017.02.07 RED HAT ISRAEL

AI summary

A method and system for switching backend devices in a virtual machine system based on features of the backend devices. In one embodiment, a computer system includes at least a first device and a second device that function as a backend device. The first device is currently used by a guest of the computer system as the backend device. A hypervisor of the computer system receives an indication from the guest to use a feature of the backend device. The hypervisor determines whether the use of the feature of the backend device triggers a switching condition. In response to a determination that the switching condition is triggered, the guest is switched to use the second device as the backend device. The switching operation can be transparent to the guest.