Non-Executable Managed Object for Instant VM Cloning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In virtualized computing environments, the overhead memory required for a parent template VM when powering on across multiple hosts is significant, especially when instant cloning VMs across a cluster, leading to substantial memory commitment.

Innovation Solution

A non-executable managed object encapsulating the runtime state of a parent VM is created, allowing for instant cloning of VMs without the need for a running parent VM, thereby reducing memory, storage, and CPU overhead by suspending the parent VM, capturing its snapshot, and provisioning a child VM from this static object.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If a parent template VM is powered-on to support instant cloning across multiple hosts, then VM instantiation speed is improved, but memory commitment increases significantly

Engineering Contradiction:
ImproveVM instantiation speedVSAvoidmemory commitment
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent creates a non-executable copy (snapshot) of the parent VM's runtime state that can be distributed across multiple hosts. This copy contains all necessary runtime information but does not require the overhead memory of a running VM, enabling instant cloning without maintaining powered-on template VMs on each host.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent extracts the essential runtime state from the parent VM into a separate non-executable managed object. This extraction separates the functional capabilities needed for cloning from the overhead memory requirements of a running VM, allowing the runtime state to be stored and distributed without active execution.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If a parent template VM is maintained across multiple hosts for instant cloning, then cloning capability is improved, but storage overhead increases

Engineering Contradiction:
Improvecloning capabilityVSAvoidstorage overhead
Core Design Contradiction:
Adaptability or versatilityVSVolume of stationary object

Solution Approach 1:

The patent creates lightweight non-executable copies of the parent VM state that can be distributed across hosts. These copies require minimal storage compared to maintaining full VM images, enabling cloning capability across multiple hosts with reduced storage overhead.

Inventive Principle:
Principle #26Copying

3Productivity

If a parent template VM is powered-on for instant cloning, then VM provisioning speed is improved, but CPU overhead increases

Engineering Contradiction:
ImproveVM provisioning speedVSAvoidCPU overhead
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent uses non-executable copies of VM runtime state that can be rapidly distributed and used for instant cloning without requiring CPU-intensive operations. The copies are lightweight artifacts that enable fast provisioning without the continuous CPU overhead of running template VMs.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11625257B2Provisioning executable managed objects of a virtualized computing environment from non-executable managed objects
Publication Date: 2023.04.11 VMWARE INC
  • US11625257B2 patent drawing
  • US11625257B2 patent drawing
  • US11625257B2 patent drawing

AI summary

A managed object of a virtualized computing environment, which contains the runtime state of a parent virtual machine (VM) and can be placed in any host of the virtualized computing environment, is used for instantly cloning child VMs off that managed object. The managed object is not an executable object (i.e., the state of the managed object is static) and thus it does not require most of the overhead memory associated with a VM. As a result, this managed object can support instant cloning of VMs with a reduction in memory, storage, and CPU overhead relative to when a parent template VM is used.