Virtual Machine Memory Recycling to Skip Scrubbing on Reboot

Solution Overview

Problem

In shared virtualized hosting environments, memory scrubbing is resource-intensive and unnecessary when virtual machines are rebooted, as existing methods require scrubbing before reallocation, which can waste resources and compromise performance.

Innovation Solution

Implementing memory allocation recycling by marking memory portions for reuse without scrubbing for virtual machines that will be rebooted, allowing these portions to be reallocated directly without scrubbing, and performing scrubbing only when the virtual machine is terminated.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If memory is scrubbed before every reallocation to prevent information leakage, then data security is improved, but resource expenditure and processing time increase

Engineering Contradiction:

Improvedata securityVSAvoidresource expenditure

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by differentiating the scrubbing treatment based on the specific scenario: memory allocated to a virtual machine that is being rebooted does not require scrubbing, while memory allocated to different virtual machines or after termination does require scrubbing. This selective approach maintains security where needed while avoiding unnecessary resource expenditure in reboot scenarios.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent implements preliminary action by detecting the reboot scenario before memory reallocation occurs. The system proactively identifies when a virtual machine is being rebooted and prevents the scrubbing operation from executing in the first place, rather than performing scrubbing and then canceling it. This avoids the waste of resources on unnecessary scrubbing operations.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If memory is scrubbed before every reallocation to prevent information leakage, then data security is improved, but processing speed and performance decrease

Engineering Contradiction:

Improvedata securityVSAvoidprocessing speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent applies local quality by differentiating the scrubbing treatment based on the specific scenario: memory allocated to a virtual machine that is being rebooted does not require scrubbing, while memory allocated to different virtual machines or after termination does require scrubbing. This selective approach maintains security where needed while avoiding unnecessary resource expenditure in reboot scenarios.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent implements preliminary action by detecting the reboot scenario before memory reallocation occurs. The system proactively identifies when a virtual machine is being rebooted and prevents the scrubbing operation from executing in the first place, rather than performing scrubbing and then canceling it. This avoids the waste of resources on unnecessary scrubbing operations.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If memory is scrubbed after every deallocation to prevent information leakage, then data security is improved, but resource expenditure and processing time increase

Engineering Contradiction:

Improvedata securityVSAvoidprocessing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent applies local quality by differentiating the scrubbing treatment based on the specific scenario: memory allocated to a virtual machine that is being rebooted does not require scrubbing, while memory allocated to different virtual machines or after termination does require scrubbing. This selective approach maintains security where needed while avoiding unnecessary resource expenditure in reboot scenarios.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent implements preliminary action by detecting the reboot scenario before memory reallocation occurs. The system proactively identifies when a virtual machine is being rebooted and prevents the scrubbing operation from executing in the first place, rather than performing scrubbing and then canceling it. This avoids the waste of resources on unnecessary scrubbing operations.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11669441B1Secure virtual machine reboot via memory allocation recycling

Publication Date: 2023.06.06 AMAZON TECH INC

AI summary

Embodiments are disclosed for recycling memory after a virtual machine reboots. Memory allocated to a rebooting virtual machine instance can be associated with the instance or otherwise marked as to be reserved for use after the virtual machine instance reboots. Subsequently, after the reboot process is initiated, the reserved memory can be reallocated to the virtual machine instance. Memory scrubbing can be ordinarily performed to avoid data leakage between customers, but scrubbing can be inhibited for memory that is returned to a rebooting virtual machine instance. Further features, such as API calls to configure memory recycling, indications to disable recycling, and the like can be supported.