Shadow VM for Virtual Disk Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data replication systems in virtual environments face challenges in efficiently accessing and managing multiple virtual disks, particularly due to limitations in the number of virtual machines that can be attached to a virtual disk, leading to resource issues and performance bottlenecks.

Innovation Solution

The implementation of a shadow virtual machine with minimal resource allocation, configured to run only the BIOS, allows access to a target VMDK without fully powering up the VM, enabling efficient access and management of multiple virtual disks through a pseudo data storage system and kernel interface, thereby overcoming resource constraints and improving performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a target virtual machine is fully powered up to access a target VMDK, then access to the virtual disk is enabled, but resource consumption increases significantly

Engineering Contradiction:
ImproveAccess to target VMDKVSAvoidResource consumption
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the essential component needed for disk access by creating a shadow VM that contains minimal system components (BIOS only) while excluding the full operating system and application layers. This allows the shadow VM to access the target VMDK without consuming the resources required by a fully powered-up VM.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a shadow VM as a simplified copy of the target VM configuration, replicating only the necessary identifiers (VM ID, VMDK attachments) while omitting resource-intensive components. This copy enables disk access functionality without the overhead of a complete VM instance.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If multiple virtual machines are attached to a virtual disk, then access flexibility is improved, but resource issues and performance bottlenecks occur

Engineering Contradiction:
ImproveAccess flexibilityVSAvoidPerformance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The shadow VM acts as an intermediary between the storage system and the target VMDK, providing a dedicated access path that does not interfere with other VMs. This mediator role allows multiple VMs to access the same storage resources without creating performance bottlenecks, as each VM including shadow VMs has its own isolated access channel.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Use of energy by moving object

If a shadow VM is configured with minimal resources to access target VMDK, then resource consumption is minimized, but the VM cannot perform full operational tasks

Engineering Contradiction:
ImproveResource consumptionVSAvoidOperational capability
Core Design Contradiction:
Use of energy by moving objectVSAdaptability or versatility

Solution Approach 1:

The shadow VM provides dynamic access to the target VMDK for read operations and replication tasks without requiring the static overhead of a full operating system. The minimal configuration is sufficient for the specific purpose of disk access and data replication, while full operational capabilities remain available in the original target VM when needed.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10296419B1Accessing a virtual device using a kernel
Publication Date: 2019.05.21 EMC IP HLDG CO LLC
  • US10296419B1 patent drawing
  • US10296419B1 patent drawing
  • US10296419B1 patent drawing

AI summary

In one aspect, a method includes powering down a target virtual machine (VM), removing the target VM from an inventory of virtual machine hosts after powering down the virtual VM, configuring a shadow VM by assigning an ID to the shadow VM to be the same as the target VM and by attaching a target VMDK to the shadow VM, adding the shadow VM to the inventory and powering up the shadow VM to run no more than a BIOS and to enable access of the target VMDK.