Virtual Machine Provisioning Using Shared Read-Only OS Images

Solution Overview

Problem

The existing virtual machine provisioning process is slow and resource-intensive due to the need to copy and replicate entire virtual machine images, leading to memory shortages and increased time requirements when creating multiple virtual machines.

Innovation Solution

A virtual machine provisioning method that uses a template with only a read-only operating system and system file images, loading the OS image into memory and building a shared root file system using a system file image, while storing system configuration and user data files separately in disk storage, allowing them to be connected to the root file system post-provisioning.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the entire virtual machine image is copied for provisioning, then the virtual machine can be created, but the provisioning process requires a lot of time and system resources

Engineering Contradiction:

Improveprovisioning speedVSAvoidprovisioning time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The virtual machine image is segmented into three distinct components: OS image (read-only, loaded once), system file image (read-only, shared), and configuration/data files (writable, per-VM). This segmentation allows the common read-only components to be loaded once and shared across multiple VMs, while only the necessary configuration and data files are copied for each new VM, dramatically reducing provisioning time and resource consumption.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of copying the entire virtual machine image for each new VM, the patent copies only the necessary writable components (configuration files and data files) while sharing the read-only components (OS image and system file image) across multiple VMs. This selective copying approach minimizes the data that needs to be replicated, improving provisioning speed and reducing system resource usage.

Inventive Principle:

Principle #26Copying

2Productivity

If the entire virtual machine image is copied for provisioning, then the virtual machine can be created, but a large amount of memory is required due to memory shortage

Engineering Contradiction:

Improveprovisioning efficiencyVSAvoidmemory usage

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The virtual machine image is segmented into three distinct components: OS image (read-only, loaded once), system file image (read-only, shared), and configuration/data files (writable, per-VM). This segmentation allows the common read-only components to be loaded once and shared across multiple VMs, while only the necessary configuration and data files are copied for each new VM, dramatically reducing provisioning time and resource consumption.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The OS image and system file image are designed as universal, read-only components that can be shared across multiple virtual machines simultaneously. These common components contain the operating system and system files that are identical for all VMs, allowing them to be loaded once into memory and referenced by multiple VM instances, thereby reducing overall memory requirements while maintaining VM functionality.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of operation

If the entire virtual machine image is copied, then all files are available, but the system resources are consumed inefficiently

Engineering Contradiction:

Improvefile availabilityVSAvoidsystem resource usage

Core Design Contradiction:

Ease of operationVSUse of energy by moving object

Solution Approach 1:

The virtual machine image is segmented into three distinct components: OS image (read-only, loaded once), system file image (read-only, shared), and configuration/data files (writable, per-VM). This segmentation allows the common read-only components to be loaded once and shared across multiple VMs, while only the necessary configuration and data files are copied for each new VM, dramatically reducing provisioning time and resource consumption.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent extracts and separates the read-only components (OS image and system file image) from the writable components (configuration files and data files). By taking out the common read-only portions and making them shareable, the system avoids redundant copying of these components for each new VM, thereby reducing system resource consumption while maintaining full file availability for each VM instance.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS12099865B2Virtual machine system and virtual machine provisioning method using the same

Publication Date: 2024.09.24 COONTEC CO LTD

AI summary

A virtual machine provisioning method according to an embodiment includes a provisioning module that creates a virtual machine image template including only an operating system image and a system file image, a virtual machine management module that extracts the OS image of the virtual machine image template according to a virtual machine creation command from a user, to load the OS image into a memory allocated a virtual machine, and execute the OS image, and an interface module that extracts a system file image of the virtual machine image template according to the virtual machine creation command to build a root file system for the virtual machine.