# US 2015/0178097 A1 · Memory-Preserving Reboot

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0178097 A1
- Document ID: US20150178097A1
- Status: Published application
- Kind: A1
- Application number: 14/136,890
- Filed: 2013-12-20
- Published: 2015-06-25
- Earliest claimed: 2013-12-20
- Assignees: Microsoft Corporation
- Applicants: Microsoft Corporation
- Inventors: Mark E. Russinovich
- Web page: https://patentgrep.com/patent/US20150178097A1

## CPC

- G06F 9/4418: {Suspend and resume; Hibernate and awake}
- G06F 8/656: while running
- G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57)
- G06F 9/442: {Shutdown}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 2009/45575: {Starting, stopping, suspending or resuming virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques are described for preserving application state in virtual memory during operating system reboot. A preserved virtual memory allocation that has been populated with state by an application is identified. The application is shutdown during the OS reboot. The operating system is rebooted without modifying the preserved virtual memory allocation. For example, physical memory and paging file pages associated with the preserved virtual memory allocation on the computer system are unmodified when the operating system is rebooted. The application is restarted after the operating system has been rebooted. The preserved virtual memory allocations are identified after the application is restarted, such as by checking contents of a memory region or by an API return value. The application is then reconnected to the preserved virtual memory allocation, which allows the application to immediately access the preserved state without having to rebuild new state.

## Claims

### Claim 1

A method of preserving virtual memory in a computer system, comprising:
identifying a preserved virtual memory allocation that is populated with state by an application;
shutting down the application;
rebooting an operating system in the computer system without modifying the preserved virtual memory allocation;
restarting the application after the operating system has been rebooted; and
reconnecting the application to the preserved virtual memory allocation.

### Claim 2 (depends on 1)

The method of claim 1, wherein rebooting the operating system further comprises:
receiving a copy of an updated host operating system;
suspending all virtual machines running on the computer system;
recording an allocation map and state for each of the virtual machines;
transferring execution from the active host operating system to a loader;
shutting down the active host operating system;
reading a kernel of updated host operating system into RAM via the loader;
loading the allocation map and state for each of the virtual machines; and
resuming operation of the virtual machines by the updated host operating system.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
leaving the virtual machines resident in RAM when the virtual machines are suspended.

### Claim 4 (depends on 1)

The method of claim 1, wherein physical memory associated with the preserved virtual memory allocation on the computer system is unmodified when the operating system is rebooted.

### Claim 5 (depends on 1)

The method of claim 1, wherein one or more paging file pages associated with the preserved virtual memory allocation on the computer system are unmodified when the operating system is rebooted.

### Claim 6 (depends on 1)

The method of claim 1, wherein the preserved virtual memory allocation is identified by the application using an API to select reboot-persistent virtual memory.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
identifying preserved virtual memory allocation after the application is restarted.

### Claim 8 (depends on 6)

The method of claim 6, wherein the preserved virtual memory allocation is identified by checking contents of a memory region.

### Claim 9 (depends on 6)

The method of claim 6, wherein the preserved virtual memory allocation is identified by an API return value.

### Claim 10

A computer system, comprising:
a processor;
system memory;
one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by the processor, causes the processor to preserve virtual memory during updates to a host operating system, the processor operating to:
identify a protected virtual memory allocation that is populated with state by an application;
shut down the application;
reboot an operating system in the computer system without modifying contents of the protected virtual memory allocation;
restart the application after the operating system has been rebooted; and
reconnect the application to the protected virtual memory allocation.

### Claim 11 (depends on 10)

The computer system of claim 10, the processor further operating to:
receive a copy of an updated host operating system;
suspend all virtual machines running on the computer system;
record an allocation map and state for each of the virtual machines;
transfer execution from the active host operating system to a loader;
shut down the active host operating system;
read a kernel of updated host operating system into RAM via the loader;
load the allocation map and state for each of the virtual machines; and
resume operation of the virtual machines by the updated host operating system.

### Claim 12 (depends on 10)

The computer system of claim 10, wherein physical memory associated with the protected virtual memory allocation on the computer system is unmodified when the operating system is rebooted.

### Claim 13 (depends on 10)

The computer system of claim 10, wherein one or more paging file pages associated with the protected virtual memory allocation on the computer system are unmodified when the operating system is rebooted.

### Claim 14 (depends on 10)

The computer system of claim 10, wherein the protected virtual memory allocation is identified by the application using an API to select reboot-persistent virtual memory.

### Claim 15 (depends on 10)

The computer system of claim 10, the processor further operating to:
identify preserved virtual memory allocation after the application is restarted by checking contents of a memory region.

### Claim 16 (depends on 10)

The computer system of claim 10, the processor further operating to:
identify preserved virtual memory allocation after the application is restarted by an API return value.

### Claim 17

A computer program product for implementing a method for preserving virtual memory allocations during updates to a host operating system, the computer program product comprising one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by one or more processors of a computer system, cause the computer system to perform the method comprising:
identifying a preserved virtual memory allocation that is populated with state by an application;
shutting down the application;
rebooting an operating system in the computer system without modifying the reserved virtual memory allocation;
restarting the application after the operating system has been rebooted; and
reconnecting the application to the preserved virtual memory allocation.

### Claim 18 (depends on 17)

The computer program product of claim 17, further comprising:
leaving the virtual machines resident in RAM when the virtual machines are suspended.

### Claim 19 (depends on 17)

The computer program product of claim 17, wherein physical memory associated with the preserved virtual memory allocation on the computer system is unmodified when the operating system is rebooted.

### Claim 20 (depends on 17)

The computer program product of claim 17, wherein one or more paging file pages associated with the preserved virtual memory allocation on the computer system are unmodified when the operating system is rebooted.
