Per-VM Swap Files for Virtual Machine Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional virtualized computer systems use a common swap space for all virtual machines, leading to inefficient VM migration, administrative burdens, security concerns, and lack of control over swap space allocation, which disrupts host performance and limits flexibility in managing swap spaces.

Innovation Solution

Implementing a per-VM swap space with separate swap files for each virtual machine, allowing for independent management, flexible placement, and fine-grained access controls, which enables efficient VM migration and improved performance by allowing swap files to be arbitrarily located, resized, and secured at a per-VM level.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a common swap space is used for all virtual machines, then memory management is simplified, but VM migration efficiency deteriorates and security control is weakened

Engineering Contradiction:
Improveswap space management complexityVSAvoidVM migration efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent divides the common swap space into separate swap files for each virtual machine. Each swap file is dedicated to a specific VM, allowing independent management and migration. This segmentation resolves the contradiction by maintaining simplified management through centralized control while enabling efficient migration through isolated, portable swap files.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent assigns different properties to different swap files based on their associated VMs. Each swap file can have customized permissions, encryption, and location optimized for its specific VM's requirements. This local quality approach allows tailored security and performance optimization for each VM while maintaining overall system coherence.

Inventive Principle:
Principle #3Local quality

2Device complexity

If a common swap space is used for all virtual machines, then administrative overhead is reduced, but security isolation deteriorates

Engineering Contradiction:
Improveadministrative overheadVSAvoidsecurity isolation
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

By segmenting the swap space into separate swap files for each VM, the patent enables granular security controls while maintaining centralized administrative management. Each swap file can have its own access permissions and encryption settings, providing security isolation without requiring complex distributed administration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a virtualization layer that mediates between the host system and individual VM swap files. This intermediary manages security policies, access controls, and encryption for each swap file, providing strong security isolation while keeping administrative overhead low through automated policy enforcement.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If separate swap files are used for each virtual machine, then security isolation and migration efficiency are improved, but system complexity increases

Engineering Contradiction:
Improvesecurity isolationVSAvoidswap space management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where each VM's swap file automatically manages its own security attributes, encryption, and lifecycle. The virtualization layer provides templates and automated policies that enable swap files to configure themselves, reducing the perceived complexity for administrators while maintaining strong security isolation.

Inventive Principle:
Principle #25Self-service

4Productivity

If a common swap space is used, then resource utilization is optimized, but control over swap space allocation deteriorates

Engineering Contradiction:
Improveresource utilizationVSAvoidswap space allocation control
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent creates a dynamic swap space management system where swap files can be dynamically allocated, resized, and relocated based on individual VM needs while maintaining overall resource optimization. The virtualization layer provides real-time control over swap file allocation, enabling both efficient resource utilization and granular allocation control.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8099568B2Separate swap files corresponding to different virtual machines in a host computer system
Publication Date: 2012.01.17 VMWARE INC
  • US8099568B2 patent drawing
  • US8099568B2 patent drawing
  • US8099568B2 patent drawing

AI summary

A swap space is provided for a host computer system, where the swap space includes a plurality of swap files with each individual swap file for swapping data only for a single corresponding virtual machine (VM). The per-VM swap space is used solely by the single, corresponding VM, such that only that particular VM's memory is allowed to be swapped out to the swap file.