VMM Segmentation for VM Isolation and Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current virtualization technologies face security threats when the Virtual Machine Monitor (VMM) has vulnerabilities or errors, as isolation between Virtual Machines (VMs) is primarily hardware-based, limiting resource flexibility and reducing resource utilization.

Innovation Solution

The implementation of a Memory Management Unit (MMU) control module and a shared service module within the VMM, which are mutually independent and isolated, allowing for the detection and isolation of attack information by processing request messages and deleting affected VMs and VM instances to prevent security breaches.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If isolation between VMs is implemented by using hardware function, then information security of the physical host is improved, but resource flexibility and resource utilization are reduced

Engineering Contradiction:
Improveinformation securityVSAvoidresource flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The VMM is segmented into multiple independent modules (MMU control module, shared service module, VM instance module) with isolated memory spaces. Each module handles specific functions and cannot access other modules' data, achieving security through architectural segmentation rather than hardware isolation. This allows flexible resource allocation while maintaining security boundaries.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The MMU control module acts as an intermediary between VMs and the shared service module. It manages memory access requests, validates addresses, and controls data flow between modules. This intermediary mechanism enables secure communication and resource sharing without requiring hardware-level isolation, thus improving both security and resource flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If resources are allocated in advance to VMs, then information security is improved through isolation, but flexibility of subsequent resource scheduling is reduced

Engineering Contradiction:
Improveinformation securityVSAvoidresource scheduling flexibility
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system implements dynamic resource allocation where the MMU control module can adjust memory mappings and resource assignments during VM runtime. Resources are not statically bound but can be dynamically allocated or deallocated based on system conditions and VM needs, enabling load balancing and efficient resource utilization while maintaining security through controlled access mechanisms.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes memory management parameters dynamically through the MMU control module. Memory allocation sizes, access permissions, and mapping relationships are adjustable parameters that can be modified during operation. This allows the system to adapt resource allocation to changing conditions while maintaining security boundaries, achieving both security and scheduling flexibility.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If the VMM is designed as a unified structure, then ease of operation is improved, but security against attacks is reduced

Engineering Contradiction:
Improvesystem simplicityVSAvoidsecurity vulnerability
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The VMM is divided into functionally independent modules (MMU control module, shared service module, VM instance module) with distinct memory spaces and access permissions. This segmentation limits the impact of potential attacks to specific modules rather than compromising the entire system. Each module's security breach cannot easily propagate to other modules due to the isolated architectural design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different modules are assigned specific security qualities and access permissions tailored to their functions. The MMU control module has strict access control over the shared service module, while VM instances have controlled access to virtualized resources. This localized security approach maintains operational simplicity while enhancing overall system security through differentiated access controls.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP3579106B1Information protection method and device
Publication Date: 2022.05.25 HUAWEI TECH CO LTD
  • EP3579106B1 patent drawingFigure 1A~1B
  • EP3579106B1 patent drawingFigure 1C~1D
  • EP3579106B1 patent drawingFigure 2

AI summary

An information protection method and apparatus are provided, and pertain to the field of virtualization technologies. The information protection apparatus includes a VMM and a plurality of VMs, the VMM includes an MMU control module, a plurality of VM instances, and a shared service module, and the plurality of VM instances are in a one-to-one correspondence with the plurality of VMs. When receiving a request message sent by any one of the plurality of VMs, the MMU control module may send, based on context information carried in the request message, the request message to a VM instance corresponding to the VM or the shared service module. If the VM instance or the shared service module determines that there is attack information, the VM instance may send an information protection notification message to the MMU control module, so that when receiving the information protection notification message, the MMU control module deletes the VM that sends the request message and the VM instance corresponding to the VM, thereby avoiding impact of the attack information on another module, and implementing information protection.