Microsoft Technology Licensing, LLC

Aol Inc.

America Online, Inc.

Scott Chao-Chueh Lee

Robin Andrew Alexander

Bryan Stephen Matthew

Srinivasan Sudanagunta

Eric Carl Rehm

Charles A Porter

Aram Christian Abajian

Austin David Dahl

Lee Edward Prewitt

John Anthony Derosa

Vladimir Sadovsky

Jennifer Lynn Kolar

Neal Robert Christiansen

Rajsekhar Das

Ayberk Ozturk

Brennan Alexander Watt

Lei Kou

Vishal Jose Mannanal

Chiuchin Chen

Aaron William Ogus

Vadim Makhervaks

Jason Stewart Wohlgemuth

James Anthony Schwartz, Jr

Monish Shantilal Shah

Yimin Deng

Laura Marie Caulfield

Matthew David Kurjanowicz

Gaurav Jagtiani

Liang Yang

Ioan Oltean

Madhav Himanshubhai Pandya

Binit Ranjan Mishra

Emma Sutherland Boyd

Donald MacGregor

Cosmos Darwin

Hari R Pulapaka

Karan Mehra

Bryan David Kelly

William R Tipton

Nathan Steven Obr

James George Cavalaris

Garret Buban

Innokentiy Basmov

Sriram Govindan

Vinod R Shankar

Emily Nicole Wilson

Shen Wang

Alex Mark Semenko

Kirsten Valery Stark

Omar Carey

Kevin A Chin

Chesong Lee

Yuri Dotsenko

Naga Govindaraju

Mark A Shaw

Martijn De Kort

Abhay Sudhir Ketkar

Ho-Yuen Chau

Attilio Mainetti

Minsang Kim

Chandra Kumar Konamki Vijayamuneeswaralu

Tristan Charles Griffith

Aacer Hatem Daken

Cody D Hartwig

Steven Adrian West

Peter Hanpeng Jiang

Shekhar Agrawal

Emily Cara Clemens

Atul Pankaj Talesara

Jonathan Robert Nowitz

Srinivasan Malayala

Chin Hwan Park

Brenda Wai Yan Bell

Vijaybalaji Madhanagopal

Christina Marianne Curlette

David Wimmel

Erik Schmidt

Mukhtar Ahmed

Sri Harsha Kanukuntla

Drew Douglas Cross

Sharon Scarlet Tang

Jennifer Marie Bourlier

Terence Kwok Tak Chan

Raz Meir Aloni

Shailesh Padmakar Joshi

Pedro d'Aquino Filocre Fs Barbuda

Vincent Orgovan, Jr

Ken Alan Berkun

Subhasish Bhattacharya

Atul P Talesara

A computer system identifies an event from a management system log associated with a first container host. The presence of the event in the management system log is indicative that the first container host identified a fatal system error at the first container host. Based on the event, the computer system determines that a first instance of a container that is provisioned at the first container host has been isolated to the first container host. Based on the first instance of the container having been isolated to the first container host, the computer system instructs a second container host to provision a second instance of the container at the second container host.

Accelerated fatal system error recovery of container host

In-place recovery of fatal system errors at virtualization hosts. A device identifies an occurrence of a fatal system error in the first instance of a host operating system (OS) executing in a computer system. The device determines to perform an in-place recovery for the fatal system error. The device performs the in-place recovery, including pausing the execution of a virtual machine (VM) by the first instance of the host OS, preserving a state of the VM within system memory of the computer system, and resuming the execution of the VM by a second instance of the host OS executing in the computer system based on the state of the VM that is preserved within the system memory of the computer system.

In-place recovery of fatal system errors at virtualization hosts

The described technologies enable a computing device to allocate at least a portion of its persistent memory as volatile memory during runtime. At least some implementations create a file in the persistent memory of the computing device. The file is created in the persistent memory of the computing device during runtime of a virtual machine (VM) hosted by the computing device. The file may be allocated to the VM. The file allocated to the VM may be used as volatile memory. For example, the VM may use the file to store temporary data (e.g., volatile data). In some implementations, the temporary data is associated with an application executing in the VM.

Runtime allocation and utilization of persistent memory as volatile memory

Zone hints for use with a zoned namespace (ZNS) storage device. Zone hints include one or more of a first hint indicating that a zone is part of a group of a plurality of zones, a second hint indicating that the zone is to be fast-filled, or a third hint indicating that the zone is associated with a background operation. The first hint is structured to instruct the ZNS storage device to allocate to the zone a first storage resources that are physically adjacent to second storage resources reserved for others of the plurality of zones. The second hint is structured to instruct the ZNS storage device to bypass a staging area when writing to the zone. The third hint is structured to instruct the ZNS storage device to deprioritizing at least one operation writing to the zone, or to bypass the staging area when writing to the zone.

Zone hints for zoned namespace storage devices

The disclosed technologies provide functionality for collecting quality of service ('QoS') statistics for in-use child physical functions of multiple physical function (“PF”) non-volatile memory devices (“MFNDs”). A host computing device creates a child PF on a MFND and configures the child PF on the MFND to provide a specified QoS level to an associated VM executing on the host computing device. The MFND then collects child PF QoS statistics for the child PF that describe the utilization of resources provided by child PF to an assigned VM. The MFND provides the child PF QoS statistics from the MFND to the host computing device. The collected child PF QoS statistics can be utilized to inform decisions regarding reallocation of MFND-provided resources, provisioning of new MFND-provided resources, and for other purposes.

Collecting quality of service statistics for in-use child physical functions of multiple physical function non-volatile memory devices

The disclosed technologies provide functionality for non-volatile memory device-assisted live migration of virtual machine ('VM') data. A host computing device (the “host”) requests that a source non-volatile memory device track changes to a namespace by a VM. In response thereto, the source device tracks changes made by the VM to the namespace and stores one or more data structures that identify the changed portions of the namespace. The host requests the data structures from the source device and requests the contents of the changed portions from the source device. The host then causes the data changed by the VM in the namespace to be written to a namespace on a target non-volatile memory device. The host can also retrieve the device internal state of a child physical function on the source device. The host migrates the retrieved device internal state to a child physical function on the target device.

Non-volatile memory device-assisted live migration of virtual machine data

The present disclosure relates to systems, methods, and computer readable media for identifying and responding to a panic condition on a storage system on a computing node. For example, systems disclosed herein may include establishing recovery instructions between a host system and a storage system in responding to a future instance of a panic condition. The storage system may provide an indication of a self-detected panic condition in a variety of ways. In response to identifying the panic condition, the host system may perform one or more recovery actions in accordance with recovery instructions accessible to the host system. This may include performing resets of specific components and reinitializing communication between the host system and storage system in less invasive ways than slower and more expensive conventional approaches for responding to panic conditions on computing nodes.

Detecting and recovering from fatal storage errors

A file system is implemented in a system comprising an anonymous-write storage device. A request for a file system operation that comprises semantics of the file system to receiving the request is received. The file system translates the file system operation to one or more commands that effect the file system operation while maintaining consistency with operation of the anonymous-write storage device. The one or more commands comprise one or more of updating file system metadata, sending a request to the anonymous-write storage device, or receiving a response from the anonymous-write storage device. The anonymous-write storage device is configured to write data in an append-only format and determine locations of data write operations agnostic of input of a write location from the file system. Metadata is updated to indicate results of the file system operation.

File system for anonymous write

An interface receives storage requests for storing data in a software-defined storage network using an append-only storage scheme. The requests include an identifier of a data object to be stored. The requests are agnostic of hardware-specific details of the storage devices. A virtualization layer accesses space allocation data for the storage devices; and policies for prioritizing performance. Based on the data and policies, a physical storage location at the plurality of storage devices is selected for storing the data object. Metadata is generated for the data object indicating that the data object is an append-only object and mapping the physical storage location of the data object to the identifier. The request is translated to instructions for storing the data object at the physical storage location using the append-only storage scheme. The data object is stored at the physical storage location using the append-only storage scheme.

Virtualized append-only storage device

An interface is instantiated for receiving storage requests for storing data in a software-defined storage network using an append-only storage scheme. The interface receives requests that are agnostic of interfaces and hardware-specific details of the storage devices of the software-defined storage network. A request comprises an identifier of a data object to be stored in the software-defined storage network using the append-only storage scheme. Metadata is generated for the data object indicating that the data object is an append-only object; and the request is translated to instructions for storing the data object in the storage devices using the append-only storage scheme. The data object is stored at one of the plurality of storage devices based on the instructions. The metadata is updated to indicate a mapping between the data object and a stored location of the data object.

Virtualized append-only interface

The disclosed technologies include functionality for managing Multiple Physical Function NVMe Devices ('MFNDs') and the physical functions ('PFs') provided by MFNDs. For example, host devices can discover MFNDs, query the capabilities of MFNDs, and change the operating mode of an MFND between a user mode and a super administrator mode. Hosts can also utilize the disclosed technologies to create and delete individual child PFs on MFNDs. The disclosed technologies also include functionality for managing the settings associated with individual PFs of MFNDs. For example, hosts can query and modify the settings associated with individual child PFs of an MFND. The disclosed technologies also include functionality for managing the QoS provided by individual PFs of a MFND. For example, hosts can also query and modify the QoS provided by individual child PFs of an MFND.

Management of multiple physical function nonvolatile memory devices

Techniques for block storage using a hybrid memory device are described. In at least some embodiments, a hybrid memory device includes a volatile memory portion, such as dynamic random access memory (DRAM). The hybrid memory device further includes non-volatile memory portion, such as flash memory. In at least some embodiments, the hybrid memory device can be embodied as a non-volatile dual in-line memory module, or NVDIMM. Techniques discussed herein employ various functionalities to enable the hybrid memory device to be exposed to various entities as an available block storage device.

Block storage using a hybrid memory device

Growing community of inventors

Bellevue, WA, United States of America

Scott Chao-Chueh Lee