# US 2019/0377646 A1 · Managing A Pool Of Virtual Functions

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

- Number: US 2019/0377646 A1
- Document ID: US20190377646A1
- Status: Published application
- Kind: A1
- Application number: 16/002,247
- Filed: 2018-06-07
- Published: 2019-12-12
- Earliest claimed: 2018-06-07
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: TIMOTHY J. SCHIMKE; PRATHIMA KOMMINENI; AMARESWARI VEGURU; JESSE P. ARROYO
- Web page: https://patentgrep.com/patent/US20190377646A1

## CPC

- G06F 11/1484: {involving virtual machines}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)}
- G06F 2009/45579: {I/O management, e.g. providing access to device drivers or storage}
- G06F 2009/45591: {Monitoring or debugging support}
- G06F 2201/815: Virtual
- G06F 2209/5011: Pool
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Managing a pool of virtual functions including generating a virtual function pool comprising a plurality of virtual functions for at least one single root input/output virtualization (SR-IOV) adapter; creating a control path from a client virtual network interface controller (VNIC) driver in a first client partition to a target network using an active virtual function; receiving a failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed; selecting, from the virtual function pool, a backup virtual function for the first client partition based on the failure alert; and recreating the control path from the client VNIC driver in the first client partition to the target network using the backup virtual function.

## Claims

### Claim 1

A method of managing a pool of virtual functions, the method comprising:
generating a virtual function pool comprising a plurality of virtual functions for at least one single root input/output virtualization (SR-IOV) adapter, wherein the virtual function pool is generated using a fault tolerance indicating an amount and type of failures to accommodate without loss of access by the plurality of virtual functions;
creating a control path from a client virtual network interface controller (VNIC) driver in a first client partition to a target network using an active virtual function, wherein the active virtual function is selected from the virtual function pool;
receiving a failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed;
selecting, from the virtual function pool, a backup virtual function for the first client partition based on the failure alert; and
recreating the control path from the client VNIC driver in the first client partition to the target network using the backup virtual function.

### Claim 2 (depends on 1)

The method of claim 1,
wherein receiving the failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed comprises determining that the control path has failed due to a software malfunction; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises determining that the backup virtual function and the active virtual function are associated with a same physical port on a same SR-IOV adapter.

### Claim 3 (depends on 1)

The method of claim 1,
wherein receiving the failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed comprises determining that the control path has failed due to a hardware malfunction; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises determining that the backup virtual function and the active virtual function are associated with different physical ports.

### Claim 4 (depends on 1)

The method of claim 1,
wherein receiving the failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed comprises determining that the control path has failed due to a change in traffic patterns; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises determining that the backup virtual function provides greater throughput than the active virtual function.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
adding an additional virtual function to the virtual function pool in response to receiving, from a hardware management console, a description of the additional virtual function to add to the virtual function pool;
determining that the additional virtual function provides greater throughput for the control path from the client VNIC driver in the first client partition to the target network; and
recreating the control path from the client VNIC driver in the first client partition to the target network using the additional virtual function.

### Claim 6 (depends on 1)

The method of claim 1,
wherein the failure alert further indicates that a control path for a second client partition has failed; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises selecting, from the virtual function pool, a backup virtual function for the second client partition based on the failure alert.

### Claim 7 (depends on 1)

The method of claim 1,
wherein the failure alert further indicates that a threshold number of control paths have failed; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises selecting, from the virtual function pool, a backup virtual function for each of the threshold number of control paths, and wherein each backup virtual function provides a minimum amount of throughput for each of the client partitions.

### Claim 8

An apparatus for managing a pool of virtual functions, the apparatus comprising a computer processor, a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of:
generating a virtual function pool comprising a plurality of virtual functions for at least one single root input/output virtualization (SR-IOV) adapter, wherein the virtual function pool is generated using a fault tolerance indicating an amount and type of failures to accommodate without loss of access by the plurality of virtual functions;
creating a control path from a client virtual network interface controller (VNIC) driver in a first client partition to a target network using an active virtual function, wherein the active virtual function is selected from the virtual function pool;
receiving a failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed;
selecting, from the virtual function pool, a backup virtual function for the first client partition based on the failure alert; and
recreating the control path from the client VNIC driver in the first client partition to the target network using the backup virtual function.

### Claim 9 (depends on 8)

The apparatus of claim 8,
wherein receiving the failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed comprises determining that the control path has failed due to a software malfunction; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises determining that the backup virtual function and the active virtual function are associated with a same physical port on a same SR-IOV adapter.

### Claim 10 (depends on 8)

The apparatus of claim 8,
wherein receiving the failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed comprises determining that the control path has failed due to a hardware malfunction; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises determining that the backup virtual function and the active virtual function are associated with different physical ports.

### Claim 11 (depends on 8)

The apparatus of claim 8,
wherein receiving the failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed comprises determining that the control path has failed due to a change in traffic patterns; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises determining that the backup virtual function provides greater throughput than the active virtual function.

### Claim 12 (depends on 8)

The apparatus of claim 8, wherein the computer program instructions further cause the apparatus to carry out the steps of:
adding an additional virtual function to the virtual function pool in response to receiving, from a hardware management console, a description of the additional virtual function to add to the virtual function pool;
determining that the additional virtual function provides greater throughput for the control path from the client VNIC driver in the first client partition to the target network; and
recreating the control path from the client VNIC driver in the first client partition to the target network using the additional virtual function.

### Claim 13 (depends on 8)

The apparatus of claim 8,
wherein the failure alert further indicates that a control path for a second client partition has failed; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises selecting, from the virtual function pool, a backup virtual function for the second client partition based on the failure alert.

### Claim 14 (depends on 8)

The apparatus of claim 8,
wherein the failure alert further indicates that a threshold number of control paths have failed; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises selecting, from the virtual function pool, a backup virtual function for each of the threshold number of control paths, and wherein each backup virtual function provides a minimum amount of throughput for each of the client partitions.

### Claim 15

A computer program product for managing a pool of virtual functions, the computer program product disposed upon a computer readable medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of:
generating a virtual function pool comprising a plurality of virtual functions for at least one single root input/output virtualization (SR-IOV) adapter, wherein the virtual function pool is generated using a fault tolerance indicating an amount and type of failures to accommodate without loss of access by the plurality of virtual functions;
creating a control path from a client virtual network interface controller (VNIC) driver in a first client partition to a target network using an active virtual function, wherein the active virtual function is selected from the virtual function pool;
receiving a failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed;
selecting, from the virtual function pool, a backup virtual function for the first client partition based on the failure alert; and
recreating the control path from the client VNIC driver in the first client partition to the target network using the backup virtual function.

### Claim 16 (depends on 15)

The computer program product of claim 15,
wherein receiving the failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed comprises determining that the control path has failed due to a software malfunction; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises determining that the backup virtual function and the active virtual function are associated with a same physical port on a same SR-IOV adapter.

### Claim 17 (depends on 15)

The computer program product of claim 15,
wherein receiving the failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed comprises determining that the control path has failed due to a hardware malfunction; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises determining that the backup virtual function and the active virtual function are associated with different physical ports.

### Claim 18 (depends on 15)

The computer program product of claim 15,
wherein receiving the failure alert indicating that the control path from the client VNIC driver in the first client partition to the target network using the active virtual function has failed comprises determining that the control path has failed due to a change in traffic patterns; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises determining that the backup virtual function provides greater throughput than the active virtual function.

### Claim 19 (depends on 15)

The computer program product of claim 15, wherein the computer program instructions further cause the computer to carry out the steps of:
adding an additional virtual function to the virtual function pool in response to receiving, from a hardware management console, a description of the additional virtual function to add to the virtual function pool;
determining that the additional virtual function provides greater throughput for the control path from the client VNIC driver in the first client partition to the target network; and
recreating the control path from the client VNIC driver in the first client partition to the target network using the additional virtual function.

### Claim 20 (depends on 15)

The computer program product of claim 15,
wherein the failure alert further indicates that a control path for a second client partition has failed; and
wherein selecting, from the virtual function pool, the backup virtual function for the first client partition based on the failure alert comprises selecting, from the virtual function pool, a backup virtual function for the second client partition based on the failure alert.
