OS Update Without Memory Reset via Virtual Snapshots

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for reloading an operating system (OS) in computer systems require memory reset, leading to data loss and costly downtime, especially in servers with large RAM, due to unstable technologies like Microsoft Windows Hotpatching and complex data migration processes.

Innovation Solution

A method that reloads the OS without memory reset by using snapshots of Virtual Machines or containers, allowing the new OS to launch and restore system data from these snapshots, minimizing downtime and data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional OS reloading methods are used, then the operating system can be updated, but memory reset is required causing data loss and long downtime

Engineering Contradiction:
ImproveOS update reliabilityVSAvoidsystem downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by creating snapshots of the file system and memory state before OS reloading begins. These snapshots preserve data in advance, allowing the system to restore from them after the new OS is loaded, thereby avoiding data loss and minimizing downtime during the update process.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If data is transferred to external media for backup, then file system data is preserved, but transfer time becomes unacceptably long for large RAM

Engineering Contradiction:
Improvefile system data preservationVSAvoiddata transfer time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent uses copying by creating in-memory snapshots of the file system and memory state instead of transferring data to external media. These snapshot copies are maintained in system memory and can be rapidly restored after OS reloading, eliminating the need for slow external data transfer while preserving all file system data.

Inventive Principle:
Principle #26Copying

3Productivity

If hot-patching technology is used, then OS updates can be applied without full reinstallation, but the technology is highly unstable and complex

Engineering Contradiction:
ImproveOS update speedVSAvoidupdate stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces snapshots as an intermediary mechanism between the old and new operating systems. The snapshots serve as a stable mediator that preserves the system state, allowing the new OS to be loaded and configured without the instability and complexity of hot-patching, while still enabling rapid updates.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If data migration to another server is performed, then OS updates can be applied, but additional server cost and migration downtime are required

Engineering Contradiction:
ImproveOS update capabilityVSAvoidserver infrastructure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the data preservation function from external infrastructure (other servers or media) and implements it directly within the system memory through snapshots. This eliminates the need for additional servers or complex migration infrastructure, reducing device complexity while maintaining reliable OS update capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS9448786B1Method for updating operating system without memory reset
Publication Date: 2016.09.20 VIRTUOZZO INT GMBH
  • US9448786B1 patent drawing
  • US9448786B1 patent drawing
  • US9448786B1 patent drawing

AI summary

The invention relates to a computer-implemented method for updating an operating system (OS) without a memory reset. The method includes launching a Virtual Execution Environment (VEE) under a host OS of a computer system. The VEE can be a VM or a Container. Next, a snapshot of the VEE is generated, including snapshotting user process data, of any processes that run under the VEE. A new OS is loaded onto the computer system, and control is given to the new OS without performing the memory reset. It is ensured that the user process data that is part of the snapshot is unaffected by the loading of the new OS and that the user process data remains in its original location. The VEE is re-launched under the new OS. User process data is restored from the snapshot into a random access memory.