Architecture for managing I/O and storage for a virtualization environment with multiple hypervisor types

• US 9,652,265 B1
• Filed: 03/14/2013
• Issued: 05/16/2017
• Est. Priority Date: 08/10/2011
• Status: Active Grant

• Current Assignee: Nutanix Incorporated
• Original Assignee: Nutanix Incorporated
• Inventors: Narayanasamy, Prakash, Guturi, Venkata Ranga Radhanikanth, Aron, Mohit, Pandey, Dheeraj, Singh, Ajeet
• Primary Examiner(s): Swift, Charles
• Application Number:
  US13/830,116
• Time in Patent Office: 1,524 Days
• Field of Search: None
• CPC Class Codes: G06F 13/00 Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units interface circuits for specific input/output devices G06F3/00 ; multiprogram control therefor G06F9/46; multiprocessor systems G06F15/16
• CPC Class Codes: G06F 13/10 Program control for peripheral devices G06F13/14 - G06F13/42 take precedence
• CPC Class Codes: G06F 13/102 where the programme performs an interfacing function, e.g. device driver G06F13/105 takes precedence; scheduling within device drivers G06F9/52; contention policies within device drivers G06F9/4881
• CPC Class Codes: G06F 13/105 where the programme performs an input/output emulation function
• CPC Class Codes: G06F 16/1748 De-duplication implemented within the file system, e.g. based on file segments de-duplication techniques in storage systems for the management of data blocks G06F3/0641
• CPC Class Codes: G06F 2009/45579 I/O management, e.g. providing access to device drivers or storage
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45537 Provision of facilities of other operating environments, e.g. WINE I/O emulation G06F13/105
• CPC Class Codes: G06F 9/4555 Para-virtualisation, i.e. guest operating system has to be modified
• CPC Class Codes: G06F 9/45554 Instruction set architectures of guest OS and hypervisor or native processor differ, e.g. Bochs or VirtualPC on PowerPC MacOS
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 49/356 for storage area networks

Abstract

A system for managing storage devices, includes a plurality of nodes that implement a virtualization environment, each node of the plurality of nodes comprising a hypervisor, a service virtual machine that sits above the hypervisor, and one or more user virtual machines that sit above the hypervisor; a plurality of storage devices that are accessed by the user virtual machines via the service virtual machines, wherein a first node of the plurality of nodes comprises a first hypervisor, a first service virtual machine and a first set of one or more user virtual machines, wherein a second node of the plurality of nodes comprises a second hypervisor, a second service virtual machine and a second set of one or more user virtual machines, wherein the first hypervisor and the second hypervisor are of different types, and wherein the first virtual machine and the second service virtual machine are of the same type.

Claims

1. A system comprising at least a processor for managing storage devices, comprising:

a plurality of nodes that implement a virtualization environment, a first node of the plurality of nodes comprising a first hypervisor, a first service virtual machine and a first set of one or more user virtual machines, a second node of the plurality of nodes comprises a second hypervisor, a second service virtual machine and a second set of one or more user virtual machines,

wherein the first hypervisor is of a first hypervisor type and the second hypervisor is of a second hypervisor type, the first hypervisor type and the second hypervisor type being different hypervisor types that use different sets of commands to operate; and

a plurality of storage devices that are accessed by the user virtual machines via the first service virtual machine and the second service virtual machine, wherein the first service virtual machine and the second service virtual machine in communication with each other through the first hypervisor of the first hypervisor type and the second hypervisor of the second hypervisor type to virtualize the plurality of storage devices as a global resource pool, and wherein the first service virtual machine communicates with the second service virtual machine to request relinquishment of ownership of a virtual disk managed by the second service virtual machine.

2. The system of claim 1, wherein a virtual disk is formed from the plurality of storage devices and the virtual disk can be accessed by both the first set of one or more user virtual machines and the second set of one or more user virtual machines.

3. The system of claim 1, wherein the first service virtual machine includes a hypervisor interface.

4. The system of claim 3, wherein the hypervisor interface configures the first service virtual machine to communicate with the first hypervisor.

5. The system of claim 4, wherein configuring the first service virtual machine to communicate with the first hypervisor comprises:

discovering the first hypervisor type; and

choosing a library of commands for communicating with the first hypervisor based at least in part on the first hypervisor type.

6. The system of claim 5, further comprising obtaining hardware, performance and configuration information from the first hypervisor using the library of commands.

7. The system of claim 6, wherein the hardware, performance and configuration information obtained from the first hypervisor comprises:

user virtual machines and service virtual machines running on the system;

performance statistics associated with the system;

or

configuration of the plurality of storage devices.

8. The system of claim 1, wherein the first hypervisor and the second hypervisor are of different types chosen from a set comprising:

VMware, ESX(i), Microsoft Hyper-V, or RedHat KVM.

9. The system of claim 3, wherein the hypervisor interface is configured to monitor the system during run-time.

10. The system of claim 3, wherein the hypervisor interface dynamically discovers the first hypervisor type by communicating with the first hypervisor using various different hypervisor languages until a match is found.

11. A system comprising at least a processor for storage device management having a plurality of nodes that implement a virtualization environment for accessing a plurality of storage devices, wherein:

a node of the plurality of nodes comprises a first hypervisor, an instantiation of a first service virtual machine, and one or more user virtual machines located above the first hypervisor;

the plurality of storage devices is accessed by the one or more user virtual machines via the instantiation of the first service virtual machine;

wherein the instantiation of the first service virtual machine is configurable to communicate with the first hypervisor regardless of hypervisor type,

wherein the first service virtual machine can communicate with another instantiation of a second service virtual machine through the first hypervisor of a first hypervisor type of the first service virtual machine and a second hypervisor of a second hypervisor type of the second service virtual machine to virtualize the plurality of storage devices as a global resource pool, and

wherein the instantiation of the first service virtual machine communicates with the instantiation of the second service virtual machine within the system to request relinquishment of ownership of a virtual disk managed by the second service virtual machine.

12. The system of claim 11, wherein the instantiation of the first service virtual machine comprises a hypervisor interface for configuring the instantiation of the first service virtual machine to communicate with the first hypervisor regardless of hypervisor type.

13. The system of claim 12, wherein configuring the instantiation of the first service virtual machine to communicate with the first hypervisor comprises:

discovering the first hypervisor type; and

choosing a library of commands for communicating with the first hypervisor based at least in part on the first hypervisor type.

14. The system of claim 13, further comprising obtaining hardware, performance and configuration information from the first hypervisor using the library of commands.

15. The system of claim 14, wherein the hardware and configuration information obtained from the first hypervisor comprises:

user virtual machines and service virtual machines running on the node;

performance statistics associated with the node;

or

configuration of the plurality of storage devices.

16. The system of claim 11, wherein the first hypervisor is of a type chosen from a set comprising:

VMware, ESX(i), Microsoft Hyper-V, or RedHat KVM.

17. The system of claim 11, wherein a hypervisor interface is configured to monitor the system during run-time.

18. The system of claim 12, wherein the hypervisor interface dynamically discovers the first hypervisor type by communicating with the first hypervisor using various different hypervisor languages until a match is found.

19. The system of claim 11, wherein the instantiation of the first service virtual machine can be replaced with another instantiation of a service virtual machine upon failure.

20. The system of claim 11, wherein the instantiation of the first service virtual machine can support various communication protocols.