# US 2024/0004820 A1 · Hypervisor Bridging of Different Versions of an IO Protocol

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

- Number: US 2024/0004820 A1
- Document ID: US20240004820A1
- Status: Published application
- Kind: A1
- Application number: 17/855,907
- Filed: 2022-07-01
- Published: 2024-01-04
- Earliest claimed: 2022-07-01
- Assignees: Dell Products L.P.
- Applicants: Dell Products, L.P.
- Inventors: Matthew H. Fredette
- Web page: https://patentgrep.com/patent/US20240004820A1

## CPC

- G06F 13/387: {for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system}
- G06F 9/45545: {Guest-host, i.e. hypervisor is an application program itself, e.g. VirtualBox}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 13/4027: {using bus bridges (G06F13/4022 takes precedence)}
- G06F 2009/45579: {I/O management, e.g. providing access to device drivers or storage}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A hypervisor is configured to bridge I/O operations between the NVMeoPCIe version of the NVMe I/O protocol and the NVMeoF version of the NVMe I/O protocol. By providing a bridging hypervisor, guests can use the NVMePCIe version of the NVMe I/O protocol for storage access operations, while the hypervisor can use the NVMeoF version of the NVMe I/O protocol to implement the storage access operations on attached storage resources of the storage system. The hypervisor handles administrative actions associated with creating, managing, and destroying submission queues and completion queues. Once the desired queue configuration has been created, NVMeoPCIe I/O operations are able to be transparently bridged by the hypervisor, which greatly reduces the amount of processing that would be required if the hypervisor were required to terminate each NVMeoPCIe I/O operation, generate corresponding NVMeoF I/O operations, and keep track of each such pair of I/O operations.

## Claims

### Claim 1

A non-transitory tangible computer readable storage medium having stored thereon a computer program for hypervisor bridging of different versions of an I/O protocol, the computer program including a set of instructions which, when executed by a computer, cause the computer to perform a method comprising the steps of:
receiving, by the hypervisor, a first request from a guest using a first version of the I/O protocol to create a first protocol admin Submission Queue (ASQ) and first protocol admin Completion Queue (ASQ) to be used to handle administrative commands using the first version of the I/O protocol;
in response to receiving the first request, transmitting, by the hypervisor, a second request to a second protocol endpoint using a second version of the I/O protocol to create a second protocol admin Submission Queue (ASQ) and second protocol admin Completion Queue (ACQ) to be used to handle administrative commands using the second version of the I/O protocol;
receiving a confirmation message, from the second protocol endpoint indicating that the second protocol ASQ and second protocol ACQ have been configured; and
in response to receiving the confirmation message, changing a status of the first protocol ASQ and the first protocol ACQ to activate the first protocol ASQ and first protocol ACQ.

### Claim 2 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, wherein the first request comprises writing addresses and sizes for the first protocol ASQ and the first protocol ACQ by the guest into registers in the hypervisor.

### Claim 3 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, further comprising receiving a third request from the guest using the first version of the I/O protocol to create a first protocol I/O Completion Queue (I/O CQ) to be used to handle I/O operations using the first version of the I/O protocol; and
in response to receiving the third request, transmitting, by the hypervisor, a fourth request to the second protocol endpoint using the second version of the I/O protocol to create a second protocol I/O Submission Queue (I/O SQ) and corresponding second protocol I/O Completion Queue (I/O CQ) to be used to handle I/O operations using the second version of the I/O protocol.

### Claim 4 (depends on 3)

The non-transitory tangible computer readable storage medium of claim 3, further comprising receiving a fifth request from the guest using the first version of the I/O protocol to create a first protocol I/O Submission Queue (I/O SQ) to be associated with the first protocol I/O Completion Queue (I/O CQ); and
in response to receiving the fifth request:
transmitting a dummy request to the second protocol endpoint using the second version of the I/O protocol;
receiving a response to the dummy request; and
in response to receiving the response to the dummy request, changing a status of the first protocol I/O SQ to activate the first I/O SQ.

### Claim 5 (depends on 4)

The non-transitory tangible computer readable storage medium of claim 4, further comprising receiving, by the hypervisor, a sixth request from the guest using the first version of the I/O protocol to delete the first protocol I/O SQ; and
in response to receiving the fifth request, deactivating the I/O SQ without deleting the second protocol I/O Submission Queue (I/O SQ).

### Claim 6 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, further comprising bridging unmanaged admin commands, by the hypervisor, from the first protocol ASQ to the second protocol ASQ, and from the second protocol ACQ to the first protocol ACQ.

### Claim 7 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, further comprising bridging I/O operations, by the hypervisor, from the first protocol I/O SQ to the second protocol I/O SQ, and from the second protocol I/O CQ to the first protocol I/O CQ.

### Claim 8 (depends on 1)

The non-transitory tangible computer readable storage medium of claim 1, wherein the I/O protocol is Non-Volatile Memory express (NVMe), the first version of the I/O protocol is a version of NVMe configured to be implemented over a Peripheral Connect Internet Express bus (NVMeoPCIe), and the second version of the I/O protocol is a version of NVMe configured to be implemented over a fabric (NVMeoF).

### Claim 9

A method of hypervisor bridging of different versions of an I/O protocol, comprising:
receiving, by the hypervisor, a first request from a guest using a first version of the I/O protocol to create a first protocol admin Submission Queue (ASQ) and first protocol admin Completion Queue (ASQ) to be used to handle administrative commands using the first version of the I/O protocol;
in response to receiving the first request, transmitting, by the hypervisor, a second request to a second protocol endpoint using a second version of the I/O protocol to create a second protocol admin Submission Queue (ASQ) and second protocol admin Completion Queue (ACQ) to be used to handle administrative commands using the second version of the I/O protocol;
receiving a confirmation message, from the second protocol endpoint indicating that the second protocol ASQ and second protocol ACQ have been configured; and
in response to receiving the confirmation message, changing a status of the first protocol ASQ and the first protocol ACQ to activate the first protocol ASQ and first protocol ACQ.

### Claim 10 (depends on 9)

The method of claim 9, wherein the first request comprises writing addresses and sizes for the first protocol ASQ and the first protocol ACQ by the guest into registers in the hypervisor.

### Claim 11 (depends on 9)

The method of claim 9, further comprising receiving a third request from the guest using the first version of the I/O protocol to create a first protocol I/O Completion Queue (I/O CQ) to be used to handle I/O operations using the first version of the I/O protocol; and
in response to receiving the third request, transmitting, by the hypervisor, a fourth request to the second protocol endpoint using the second version of the I/O protocol to create a second protocol I/O Submission Queue (I/O SQ) and corresponding second protocol I/O Completion Queue (I/O CQ) to be used to handle I/O operations using the second version of the I/O protocol.

### Claim 12 (depends on 11)

The method of claim 11, further comprising receiving a fifth request from the guest using the first version of the I/O protocol to create a first protocol I/O Submission Queue (I/O SQ) to be associated with the first protocol I/O Completion Queue (I/O CQ); and
in response to receiving the fifth request:
transmitting a dummy request to the second protocol endpoint using the second version of the I/O protocol;
receiving a response to the dummy request; and
in response to receiving the response to the dummy request, changing a status of the first protocol I/O SQ to activate the first I/O SQ.

### Claim 13 (depends on 12)

The method of claim 12, further comprising receiving, by the hypervisor, a sixth request from the guest using the first version of the I/O protocol to delete the first protocol I/O SQ; and
in response to receiving the fifth request, deactivating the I/O SQ without deleting the second protocol I/O Submission Queue (I/O SQ).

### Claim 14 (depends on 9)

The method of claim 9, further comprising bridging unmanaged admin commands, by the hypervisor, from the first protocol ASQ to the second protocol ASQ, and from the second protocol ACQ to the first protocol ACQ.

### Claim 15 (depends on 9)

The method of claim 9, further comprising bridging I/O operations, by the hypervisor, from the first protocol I/O SQ to the second protocol I/O SQ, and from the second protocol I/O CQ to the first protocol I/O CQ.

### Claim 16 (depends on 9)

The method of claim 9, wherein the I/O protocol is Non-Volatile Memory express (NVMe), the first version of the I/O protocol is a version of NVMe configured to be implemented over a Peripheral Connect Internet Express bus (NVMeoPCIe), and the second version of the I/O protocol is a version of NVMe configured to be implemented over a fabric (NVMeoF).

### Claim 17

A system, comprising:
a processor;
a hypervisor executing on the processor;
a memory device; and
wherein the hypervisor is programed to:
receive a first request from a guest using a first version of the I/O protocol to create a first protocol admin Submission Queue (ASQ) and first protocol admin Completion Queue (ASQ) to be used to handle administrative commands using the first version of the I/O protocol;
in response to receiving the first request, transmit a second request to a second protocol endpoint using a second version of the I/O protocol to create a second protocol admin Submission Queue (ASQ) and second protocol admin Completion Queue (ACQ) to be used to handle administrative commands using the second version of the I/O protocol;
receive a confirmation message, from the second protocol endpoint indicating that the second protocol ASQ and second protocol ACQ have been configured; and
in response to receiving the confirmation message, change a status of the first protocol ASQ and the first protocol ACQ to activate the first protocol ASQ and first protocol ACQ.

### Claim 18 (depends on 17)

The system of claim 17, wherein the hypervisor is further programmed to:
receive a third request from the guest using the first version of the I/O protocol to create a first protocol I/O Completion Queue (I/O CQ) to be used to handle I/O operations using the first version of the I/O protocol; and
in response to receiving the third request, transmit a fourth request to the second protocol endpoint using the second version of the I/O protocol to create a second protocol I/O Submission Queue (I/O SQ) and corresponding second protocol I/O Completion Queue (I/O CQ) to be used to handle I/O operations using the second version of the I/O protocol.

### Claim 19 (depends on 17)

The system of claim 17, wherein the hypervisor is further programmed to:
receive a fifth request from the guest using the first version of the I/O protocol to create a first protocol I/O Submission Queue (I/O SQ) to be associated with the first protocol I/O Completion Queue (I/O CQ); and
in response to receiving the fifth request:
transmit a dummy request to the second protocol endpoint using the second version of the I/O protocol;
receive a response to the dummy request; and
in response to receiving the response to the dummy request, change a status of the first protocol I/O SQ to activate the first I/O SQ.

### Claim 20 (depends on 17)

The system of claim 17, wherein the I/O protocol is Non-Volatile Memory express (NVMe), the first version of the I/O protocol is a version of NVMe configured to be implemented over a Peripheral Connect Internet Express bus (NVMeoPCIe), and the second version of the I/O protocol is a version of NVMe configured to be implemented over a fabric (NVMeoF).
