Dynamic I/O virtualization system having guest memory management for mapping virtual addresses using virtualization application programming interface (API) in guest kernal
A system and method for providing dynamic I/O virtualization is herein disclosed. According to one embodiment, a device capable of performing hypervisor-agnostic and device-agnostic I/O virtualization includes a host computer interface, memory, I/O devices (GPU, disk, NIC), and efficient communication mechanisms for virtual machines to communicate their intention to perform I/O operations on the device. According to one embodiment, the communication mechanism may use shared memory. According to some embodiments, the device may be implemented purely in hardware, in software, or using a combination of hardware and software. According to some embodiments, the device may share its memory with guest processes to perform optimizations including but not limited to a shared page cache and a shared heap.
1. A system, comprising:
a host computer having a host kernel and a host memory, the host memory comprising an input output virtualization memory, wherein the input output virtualization memory includes a bridge code and an input output virtualization application programming interface (API);
one or more guest computers, each guest computer of the one or more guest computers having a guest kernel and a guest memory, the bridge code being configured for a guest application in the one or more guest computers to perform operations in the host computer, wherein the guest application is generated with the input output virtualization API; and
an input output virtualization interface configured to communicate between the host computer and the one or more guest computers.
2. The system of claim 1 , wherein the bridge code and the input output virtualization API resides in the input output virtualization memory and the guest kernel.
3. The system of claim 1 , wherein data that the bridge code operates on resides in the input output virtualization memory.
4. The system of claim 1 , wherein the input output virtualization memory comprises at least one of a storage cache or a shared heap.
5. The system of claim 1 , wherein the operations includes reading and writing on files in the host kernel.
6. The system of claim 1 , wherein the input output virtualization API initiates one or more input output virtualization operations, the operations including a remote system call.
7. The system of claim 6 , wherein a guest kernel driver in the guest computer is an initiator of the input output virtualization operations.
8. The system of claim 1 , wherein the input output virtualization API enables an input/output request from a cloud application layer to a native driver layer on the host computer.
9. The system of claim 1 , wherein the input output virtualization API enables an input/output request from a cloud platform management layer to a native driver layer on the host computer.
10. The system of claim 1 , wherein the input output virtualization API enables an input/output request from a cloud management platform layer to a native driver layer on the host computer.
11. The system of claim 1 , wherein a guest process and memory manager (PMM) maps the bridge code into an address space of the guest kernel and an address space of the guest application.
12. A computer-implemented method, comprising:
providing a host computer having a host kernel and a host memory, the host memory comprising an input output virtualization memory, wherein the input output virtualization memory includes a bridge code and an input output virtualization application programming interface (API);
providing one or more guest computers, each of the guest computer of the one or more guest computers having a guest kernel and a guest memory;
providing an input output virtualization interface to communicate between the host computer and the one or more guest computers;
generating a guest application with the input output virtualization API; and
allowing the guest application from the one or more guest computers to perform operations in the host computer.
13. The computer-implemented method of claim 12 , wherein the bridge code and the input output virtualization API resides in the input output virtualization memory and the guest kernel.
14. The computer-implemented method of claim 12 , wherein data that the bridge code operates on resides in the input output virtualization memory.
15. The computer-implemented method of claim 12 , wherein the input output virtualization memory comprises at least one of a storage cache or a shared heap.
16. The computer-implemented method of claim 12 , wherein the operations includes reading and writing on files in the host kernel.
17. The computer-implemented method of claim 12 , further comprising initiating, by the input output virtualization API, one or more input output virtualization operations, the operations including a remote system call.
18. The computer-implemented method of claim 17 , wherein a guest kernel driver in the guest computer is an initiator of the input output virtualization operations.
19. The computer-implemented method of claim 12 , further comprising enabling, by the input output virtualization API, an input/output request from a cloud application layer to a native driver layer on the host computer.
20. The computer-implemented method of claim 12 , further comprising enabling, by the input output virtualization API, an input/output request from a cloud platform management layer to a native driver layer on the host computer.
21. The computer-implemented method of claim 12 , further comprising enabling, by the input output virtualization API, an input/output request from a cloud management platform layer to a native driver layer on the host computer.
22. The computer-implemented method of claim 12 , further comprising mapping, by a guest process and memory manager (PMM), the bridge code into an address space of the guest kernel and an address space of the guest application.