Virtual Machine Deployment Pause for User Settings

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing virtual machine deployment methods require a reboot to apply user-specific settings, which consumes significant time and resources.

Innovation Solution

The proposed solution involves pausing the deployment of a virtual machine prior to a machine name dependency, allowing user-specific settings to be applied without a reboot by executing a machine-based and user-specific provisioning agent.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a pre-provisioned virtual machine is configured with user-specific settings, then the virtual machine can be customized for user needs, but a reboot is required which consumes substantial time

Engineering Contradiction:
Improvevirtual machine customizationVSAvoidreboot time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pausing the virtual machine deployment process before the machine name dependency point, allowing user-specific settings to be configured in advance. This pause state enables the system to prepare the virtual machine with customized settings before resuming deployment, eliminating the need for a reboot and thus reducing the time loss while maintaining adaptability.

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If deployment is paused before machine name dependency, then user-specific settings can be applied without reboot, but deployment process complexity increases

Engineering Contradiction:
Improvedeployment timeVSAvoiddeployment process complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the deployment process into distinct phases: an initial deployment phase that pauses before the machine name dependency, a configuration phase where user-specific settings are applied, and a resumption phase where deployment continues. This segmentation allows the system to manage complexity by handling configuration separately from the main deployment flow, reducing overall deployment time while organizing the process into manageable segments.

Inventive Principle:
Principle #1Segmentation

3Productivity

If pre-provisioned virtual machines are reused with user-specific settings, then resource efficiency improves, but machine name dependencies may cause conflicts

Engineering Contradiction:
Improvevirtual machine provisioning efficiencyVSAvoidconfiguration reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by performing the pause operation at a specific point in the deployment process before machine name dependencies are encountered. This timing allows user-specific settings to be configured in advance while avoiding conflicts with subsequent machine name-dependent operations. The pause state ensures that configurations are applied to pre-provisioned virtual machines without compromising reliability, as the deployment process is halted at the appropriate moment to prevent conflicts.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4055476B1Pausing deployment of a virtual machine prior to a machine name dependency
Publication Date: 2025.04.02 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP4055476B1 patent drawingFigure 1
  • EP4055476B1 patent drawingFigure 2
  • EP4055476B1 patent drawingFigure 3

AI summary

Techniques are described herein that are capable of pausing deployment of a pre-provisioned virtual machine. Deployment of a virtual machine on a computing system is initiated. The deployment of the virtual machine is paused, prior to execution of code that depends on a name of the virtual machine, to wait for receipt of user-specific setting(s) of the virtual machine. The deployment of the virtual machine is continued based at least in part on receipt of the user-specific setting(s). Continuing the deployment includes configuring the virtual machine to have at least one of the user-specific setting(s).