Global Resource Capping Service for Virtual Memory Management

Solution Overview

Problem

Existing resource capping mechanisms in virtualization, such as those in the SOLARIS operating system, are inadequate for effectively managing physical memory across zones, as they require instances of the resource capping daemon to run within each zone, leading to security issues and complex configuration, especially when zone administrators are untrusted and can circumvent caps.

Innovation Solution

Implementing a global resource capping background service that enforces physical memory caps across separate environments, such as zones and virtual machines, from a single trusted process in the global zone, simplifying configuration and enhancing security by centralizing memory cap enforcement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If resource capping daemon instances are run within each zone to enforce memory caps, then memory management capability is provided, but security issues arise and configuration becomes complex when zone administrators are untrusted

Engineering Contradiction:

Improvememory cap enforcement reliabilityVSAvoidconfiguration complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the resource capping daemon from within zones and places it in the global zone. This extraction eliminates the security issues where untrusted zone administrators could circumvent memory caps, while also simplifying configuration by having a single centralized daemon instead of multiple instances within each zone.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The global zone acts as an intermediary between the resource capping daemon and zones. The daemon runs in the global zone and enforces memory caps on zones, providing a trusted mediation layer that prevents direct access by untrusted zone administrators while maintaining effective memory management.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If resource capping daemon instances are run within each zone to enforce memory caps, then memory management capability is provided, but security issues arise when zone administrators are untrusted

Engineering Contradiction:

Improvememory cap enforcement reliabilityVSAvoidsecurity vulnerabilities

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the resource capping daemon from within zones and places it in the global zone. This extraction eliminates the security issues where untrusted zone administrators could circumvent memory caps, while also simplifying configuration by having a single centralized daemon instead of multiple instances within each zone.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The global zone acts as an intermediary between the resource capping daemon and zones. The daemon runs in the global zone and enforces memory caps on zones, providing a trusted mediation layer that prevents direct access by untrusted zone administrators while maintaining effective memory management.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If a global resource capping background service is implemented to enforce memory caps from a single trusted process, then configuration is simplified and security is enhanced, but system architecture complexity increases

Engineering Contradiction:

Improveconfiguration easeVSAvoidsystem architecture complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent merges multiple resource capping daemon instances (one per zone) into a single global resource capping background service. This consolidation simplifies configuration by having one centralized daemon that manages memory caps for all zones, reducing the operational complexity of managing multiple instances while maintaining effective memory management.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS8954686B2Physical memory capping for use in virtualization

Publication Date: 2015.02.10 SUN MICROSYSTEMS INC

AI summary

A method of implementing virtualization involves an improved approach to resource management. A virtualizing subsystem is capable of creating separate environments that logically isolate applications from each other. Some of the separate environments share physical resources including physical memory. When a separate environment is configured, properties for the separate environment are defined. Configuring a separate environment may include specifying a physical memory usage cap for the separate environment. A global resource capping background service enforces physical memory caps on any separate environments that have specified physical memory caps.