Virtual Machine Snapshot Update via Clone Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Virtual machines face challenges in continuously applying program updates to all snapshots, leading to situations where virtual machines are operated with outdated software, compromising security and efficiency.
Innovation Solution
A method is introduced to automatically apply updates to virtual machine snapshots by creating a clone, disabling and re-enabling the virtual NIC, and applying updates through a network, ensuring all snapshots are up-to-date without disrupting the operational virtual machine.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If updates are applied to all virtual machine snapshots, then security and software currency are improved, but computational resources and time consumption increase significantly
Solution Approach 1:
The patent segments the snapshot management process by creating a clone virtual machine from the parent VM and applying updates only to the clone, rather than updating all snapshots directly. This segmentation allows selective update application to specific snapshot versions without affecting the entire snapshot hierarchy, reducing overall update time and resource consumption while maintaining security.
Solution Approach 2:
The patent performs preliminary actions by creating a clone virtual machine before applying updates. This preliminary clone is then updated with security patches and software updates, and the updated clone serves as a new snapshot. This approach prepares the update environment in advance, allowing the parent VM to continue operating while updates are applied to the clone, significantly reducing the time impact on production systems.
2Reliability
If updates are applied to snapshots, then software currency is improved, but operational disruption of the virtual machine occurs
Solution Approach 1:
The patent uses copying by creating a clone virtual machine from the parent VM snapshot. This clone is a complete copy that can be updated independently without affecting the operational parent VM. The update process is performed on the copied instance, and once updated, it becomes a new snapshot version. This copying mechanism ensures that the original VM continues to operate normally while receiving updates through the clone, maintaining operational continuity.
Solution Approach 2:
The clone virtual machine acts as an intermediary between the parent VM and the update application process. By introducing this intermediate clone, the patent enables update application without directly disrupting the parent VM operations. The intermediary clone absorbs the update process, allowing the parent VM to maintain normal operations while the clone receives and tests updates before becoming a new snapshot version.
3Stability of the object's composition
If virtual NIC is disabled and re-enabled in the clone, then network configuration stability is improved, but additional configuration steps increase complexity
Solution Approach 1:
The patent applies parameter changes by disabling and re-enabling the virtual NIC in the clone virtual machine. This parameter change (NIC state transition) ensures that the network interface is properly initialized with the updated system configuration, preventing network connectivity issues that could arise from snapshot inheritance. The temporary disabling and re-enabling refreshes the network stack parameters, ensuring stability and compatibility with the updated system state.
Data Source
AI summary
For automatically applying update to snapshots of a virtual machine (VM), a cloned virtual machine is created reproducing a state of an existing first snapshot of a virtual machine, a first virtual NIC in the cloned VM is disabled, an update is applied to the cloned VM to which a second virtual NIC has been added, the second virtual NIC is deleted from the cloned VM to which the update has been applied, the first virtual NIC is enabled, and a second snapshot of the cloned VM is generated with the enabled first virtual NIC wherein the second snapshot is associated with the virtual machine.


