JP2008299791A - Virtual computer system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent a group of virtual computers, which communicate each other without using physical lines, from being distributed to different host computers to suppress band consumption and reliability deterioration in an external network. <P>SOLUTION: A virtual computer system is provided with a plurality of virtual computers formed on physical computers and a hypervisor which executes communication among the virtual computers. In this case, the hypervisor is provided with; a communication management part which monitors the communication among the plurality of virtual computers; and a dependence determination part which determines dependence among the virtual computers. When a virtual computer is required to move to another host computer, it is determined whether there is a virtual computer highly depending on the virtual computer. When such a virtual computer is found as the result of determination, a warning is issued at a request for movement. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a virtual machine system, and more particularly to management of dependency between virtual machines when a virtual machine built on a certain physical computer migrates to another physical computer.

  With server virtualization technology that consolidates multiple tasks on a single physical server, it is possible to increase the utilization efficiency of hardware resources such as processors, memory, and input / output devices, and to change resource allocation according to the amount of processing. It is. Since the excessive initial investment of the computer system can be suppressed, there is an increasing expectation for server virtualization technology not only in the high-end server but also in the PC architecture. When a plurality of virtual machines are constructed on one physical server, various applications that are considered to have operational interdependencies among the virtual machines may be processed.

  For example, Patent Document 1 (Japanese Patent Application Laid-Open No. 2002-342280) discloses a secure message passing method between operating systems (OS) in a section on a physical server in electronic commerce. By making communication between virtual computers via a shared storage area, it is possible to move the storage contents at a memory speed without using a network device.

  In the server virtualization technology, a virtual machine running on a physical server can be moved to another physical server. The migration of a virtual machine is implemented as a countermeasure when a different virtual machine is migrated to a different server in order to increase the resource of a certain virtual machine, when the server is maintained or prevented, or when a failure occurs in the server. Communication and input / output operations are often stopped during migration. However, according to the virtual machine migration method disclosed in Patent Document 2 (Japanese Patent Laid-Open No. 2005-327279), a virtual machine after moving a communication queue By resident in the shared memory, migration can be performed without losing communication or stopping subsequent communication.

JP 2002-342280 A JP 2005-327279 A

  However, as disclosed in Patent Document 2, when migrating a virtual machine, if one virtual machine communicating between virtual machines without using a physical line is migrated to another computer, the communication between virtual machines is physically performed. It goes through the line and consumes the bandwidth of the external network. Moreover, since it becomes difficult to ensure the breakdown of network devices and security (that is, to be seen from the outside), the reliability is lowered.

An object of the present invention is to manage the dependency between virtual machines built on a computer, and to prevent bandwidth consumption and reliability degradation of an external network.
More specifically, the present invention is to prevent a group of virtual machines communicating without using a physical line between virtual machines built on a physical computer from being distributed to other different computers. .

  The virtual computer system according to the present invention is preferably configured such that a plurality of virtual computers connected to each other via a communication line and formed on the physical computer, and communication processing between the plurality of virtual computers. In a virtual machine system having a hypervisor to be executed, the hypervisor has a communication management unit that monitors communication processing between a plurality of virtual machines, and dependency that determines the degree of dependence between virtual machines using information from the communication management unit A virtual machine formed on a certain physical computer to another virtual machine formed in the same physical computer or on another physical computer according to the determination by the dependency determining part It is configured as a virtual computer system characterized by presenting whether or not it is possible to shift to a virtual computer.

In a preferred example, the communication management unit holds communication path information between virtual machines, and the dependency level determination unit determines a dependency level between virtual machines using the communication path information.
Preferably, the communication management unit retains communication history information between virtual computers, and the dependency level determination unit determines a dependency level between virtual computers using the communication history information.
Preferably, the dependency degree determination unit holds at least one condition for determining the dependency degree, and the hypervisor has a dependency condition setting unit for changing the condition for determining the dependency degree.

In a preferred example, the management apparatus includes a management apparatus that is connected to the plurality of physical computers and manages virtual machines, and the management apparatus requests to migrate a virtual machine formed on a certain physical computer to another physical computer. An input unit that inputs a determination result of the dependency determination unit, a unit that is specified by the input unit, determines whether there is a virtual machine that is requested to be migrated and a virtual computer with a strong dependency, and a determination unit As a result of the determination, if there is a virtual machine with a strong dependency, the virtual machine system includes an output unit that outputs a warning for the migration request.
Preferably, the management apparatus outputs dependency information between virtual machines to an output unit.
Further, preferably, when the virtual machine is determined to be connected using a physical communication line, the dependency degree determining unit prohibits the virtual machine from being transferred to another virtual machine.

In the virtual computer management method according to the present invention, preferably, a plurality of virtual computers that are connected to each other via a communication line and can be formed on the physical computer, and communication between the plurality of virtual computers. A virtual machine management method in a virtual machine system having a hypervisor for executing processing,
A communication management step for monitoring communication processing between a plurality of virtual machines, a dependence judgment step for judging the degree of dependence between virtual machines, and on a certain physical computer according to the judgment of the degree of dependence related to communication management. Presenting whether or not the formed virtual machine can be migrated to another virtual machine formed in the same physical computer or to a virtual machine formed in another physical computer. It is configured as a virtual machine management method.

  The program for managing a virtual machine according to the present invention preferably includes a plurality of virtual machines that are connected to a plurality of physical computers via a communication line and can be formed on the physical computer, and a plurality of virtual computers. In a virtual machine system having a hypervisor that executes communication processing between virtual machines, a program for managing virtual machines executed on the hypervisor, the communication management for monitoring communication processes between a plurality of virtual machines Functions, a dependency determination function that determines the dependency between virtual machines, and a virtual machine formed on a physical computer in the same physical computer according to the dependency determination related to communication management A function of presenting whether or not it is possible to migrate to a virtual machine formed on another virtual machine or a virtual machine formed on another physical computer; Configured as a program for the management of the virtual machine, characterized in that the implement.

  According to the present invention, it is possible to manage the dependency between virtual machines built on a computer. In particular, a computer with a different virtual machine group that communicates between virtual machines without using a physical line is warned when a part of a highly dependent virtual machine group is moved to another computer Can be prevented from being dispersed.

An embodiment of the present invention will be described below with reference to the drawings.
FIG. 1 schematically shows a configuration of a virtual machine system 10 in one embodiment. The virtual machine system 10 includes a plurality of virtual machines 200 constructed on a physical computer and a hypervisor 300 that manages communication between the virtual machines 200. The individual virtual machines may be indicated as 2001 and 200n, respectively.
Each virtual machine 200 can be executed by installing a different OS. An OS installed in the virtual machine 200 is called a guest OS 201. In addition, the virtual machine 200 includes a virtual communication device 202 used by the guest OS 201.

  The hypervisor 300 includes a communication device emulator 301, an inter-virtual computer communication management unit (hereinafter simply referred to as a communication management unit) 304 that monitors communication processing between a plurality of virtual computers, and a virtual that determines the degree of dependence between virtual computers. A computer dependence management unit (hereinafter simply referred to as a dependence management unit) 305 is included. The hypervisor 300 is a component that mediates in order to pass data to a transmission destination when the virtual computer 200 executes communication processing using the virtual communication device 202. The functions of the communication manager 304 and the dependency manager 305 will be described in detail later. Note that “LPAR” in which a logical partition is rephrased may be used as a synonym for a virtual machine.

FIG. 2 shows a hardware configuration of a computer system in which the virtual machine system is realized.
Two host computers 1001 and 1002 as physical computers, a storage device 400, and a management device 500 are connected via a network. Here, the host computers 1001 and 1002 are collectively denoted by reference numeral 100. The storage device 400 may be in the host computer 100.

The host computer 100 includes an interface (I / I) for connecting the communication device 101, the CPU 102, the memory 103, the input device 104, the display device 105, another host computer 100, the storage device 400, and the management device 500. F) 106.
The management apparatus 500 is a computer that controls the virtual machine system 10 using the host computer 100. Similar to the host computer 100, the management apparatus 500 includes a communication device 501, a CPU 502, a memory 503, an input device 504, and a display. A device 505 and an interface (I / F) 506 for connecting the host computer 100 and the storage device 400 are provided.

  FIG. 3 shows a system configuration when virtual machines on different host computers communicate using physical lines. Host computers 1001 and 1002 are connected via a communication line 107. Virtual computers 2001, 2002, and 2003 are constructed in the host computer 1001, and a virtual computer 2004 is constructed in the other host computer 1002.

  For example, when communicating between a virtual machine 2001 and a virtual machine 2002 on the same host computer 1001, for example, a communication request is sent from the virtual communication device 202 of the virtual machine 2001 to the hypervisor 3001, and the virtual communication device 202 of the virtual machine 2002. For example, processing such as data copying can be performed. At that time, the communication device emulator 301 of the hypervisor 3001 may copy data between the communication buffers prepared as the virtual communication devices 202 of the two virtual machines 2001 and 2002, though the communication interface 106 of the host computer 1001 may be used. Sometimes. When such a communication path is used, since the external communication line 107 is not used, data communication is possible even if the communication line 107 breaks down, and data is transferred to a device other than the original communication destination. It is possible to prevent data from being falsified during communication.

  On the other hand, for example, when the virtual machine 2003 and the virtual machine 2004 communicate with each other, the host computer is different, so the external communication line 107 must be passed between the two virtual machines 2003 and 2004. Similarly, when the virtual machine 2004 is not a virtual machine but an actual machine, it must pass through the communication line 107 in the same manner. In this case, since the external communication line 107 is passed, there is a possibility that data may be sent to a device other than the original communication destination as compared to the case where communication is performed between virtual machines in the same host computer via a buffer. In some cases, data may be tampered with during communication, reducing the reliability of data communication.

  FIG. 4 schematically shows an internal configuration of the inter-virtual machine communication management unit 304 in the hypervisor 300. The inter-virtual computer communication management unit 304 includes communication path information 341, communication history information 342, a communication history processing program 343, and a communication execution program 344 that executes communication between virtual computers. Each of these functions and programs will be described in detail later.

  FIG. 5 schematically shows an internal configuration of the virtual machine dependency management unit 305 in the hypervisor 300. The virtual machine dependence degree management unit 305 includes a virtual machine dependence degree judgment condition 351, virtual machine dependence degree information 352, a virtual machine information management processing program 353, and a virtual machine dependence degree judgment program 354. Each of these functions and programs will be described in detail later.

  FIG. 6 schematically shows an internal configuration of the memory 503 of the management apparatus 500. The memory 503 stores virtual machine management information 601, a virtual machine dependence determination condition setting program 602, a virtual machine management program 603, a virtual machine migration procedure program 604, and a virtual machine dependence information display program 605. . The CPU 502 (FIG. 2) of the management apparatus 500 reads out and executes the virtual machine dependence determination condition setting program 602, the virtual machine dependence information display program 603, and the virtual machine migration procedure program 604 from the memory 503. Various processes associated with the construction of the virtual machine are performed. Each of these functions and programs will be described later.

  FIG. 14 schematically shows an example of a communication path between the virtual machine 200 in the communication device emulator 301. The communication device emulator 301 receives communication data from the virtual communication device 202 in accordance with a communication request in the virtual computer 2001. The communication execution program 344 of the inter-virtual computer communication management unit 304 executes the virtual machine information of the transmission destination and the determination of which communication path is used. For example, if the direct memory access circuit 1410 is used, data can be passed to the destination virtual communication device 202 without consuming processing steps of the CPU 102. Apart from this, when the inter-virtual communication device memory copy processing 1420 is used, the CPU 102 processes the memory copy from the transmission source buffer of the virtual communication device 202 to the transmission destination buffer. In addition, when the data copy process 1430 is used, the data is temporarily copied to the communication apparatus 101, and is then looped back, and the data copy process 1431 is executed on the transmission destination buffer. When this communication path is used, the number of data copies and the number of CPU processing steps are increased and the communication time is increased as compared with the case where the memory copy process 1420 between virtual communication apparatuses is used.

FIG. 7 shows an example of the contents of the virtual machine communication path information 341 (FIG. 4).
The virtual machine communication path information 341 identifies information 710 identifying the virtual machine 200 of the virtual machine system 10, and identifying the virtual machine 200 of the virtual machine system 10 that may have a communication path with the virtual machine 200 indicated by the information 710. A field 730 having information 720 and indicating a combination of the virtual machine identification information 710 and the virtual machine identification information 720 has communication path information between the virtual machines.

  In this embodiment, the direct memory access circuit 1410 (FIG. 14) is used for the communication path of LPAR1 and LPAR2, and the communication device 101 via data copy processing 1430 and 1431 (FIG. 14) is used for the communication path of LPAR2 and LPAR3. It is shown that the physical line 107 is used for the communication path of LPAR3 and LPAR4, and the inter-virtual communication device memory copy process 1420 (FIG. 14) is used for the communication path of LPAR1 and LPAR4. In a configuration in which communication is not performed between virtual machines, the information is that there is no communication path.

Next, a dependency condition setting process 602 between virtual machines in the management apparatus 500 will be described with reference to FIGS. 9 and 17.
FIG. 17 shows an example of the contents of the virtual machine dependence determination condition 351 (FIG. 5).
The virtual machine dependency determination condition 351 includes a condition type of whether the determination condition is related to a communication path between virtual machines 1710, communication history 1720, or the identification information of the virtual machine is directly set and the condition is set to 1730. Register separately. A condition item is set for each condition type, and the degree of dependence between virtual machines on the condition item is indicated by a condition value. The greater the condition value, the greater the priority of the corresponding condition item.

  If the condition type is an inter-virtual computer communication path, the direct memory access circuit 1410 of the communication device emulator 301 (FIG. 14), the inter-virtual communication device memory copy processing 1420, and the intra-communication device loopback data copy processing 1430 and 1431 A numerical value indicating in which area the degree of dependence between the virtual machines communicating via is strong is set in area 1710.

If the condition type is a communication history, a numerical value indicating the relationship between the communication frequency, the threshold of the communication amount, and the dependency of the virtual calculation period corresponding to the effective period of the communication history information is set in the area 1720. .
In the case where conditions are set by directly specifying virtual machine identification information, an area 1730 is used.
When new conditions are set in the areas 1710, 1720, and 1730, the update time is set in the area 1740.

The dependency condition setting process 602 will be described with reference to FIG.
First, the management device memory 503 receives a dependency determination condition update request from the input device 504 (S910). This request includes a condition type, a condition item, and a condition value. Next, it is determined whether or not the request condition type is a communication path (S920). As a result of the determination, if it is determined that it is not a communication path, the process proceeds to S940. On the other hand, if the communication path is determined, the process proceeds to S930. In S930, route information and condition values as condition items are stored in the area 1710 (FIG. 17) of the dependency determination condition 351.

  In step S940, it is determined whether the request condition type is communication history. As a result of the determination, if it is determined not to be a communication history, the process proceeds to S970. On the other hand, if the communication history is determined, the process proceeds to S950. In S950, the validity period of the history information to be used is stored in the area 1720 (FIG. 17) of the dependency determination condition 351 from the information stored in the virtual machine communication history information 342. Subsequently, the communication history condition is stored in the area 1720 (FIG. 17) (S960).

  Thereafter, it is determined whether or not the request condition type is a direct condition (S970). As a result of the determination, if it is determined that the condition is not a direct condition, the process proceeds to S990. On the other hand, if it is determined that the condition is a direct condition, the process proceeds to S980. In S980, the dependency determination condition specifying the virtual machine is stored in the area 1730 (FIG. 17) of the dependency determination condition 351.

  In the example of the area 1730 in FIG. 17, the virtual computer 2001 with the virtual computer identifier LPAR1 stores “x” indicating that the host computer 1002 that is different from the currently executing host computer 1001 may be migrated. . In addition, the virtual computer 2002 having the virtual computer identifier LPAR2 stores “◯” indicating that the host computer 1002 that is currently being executed is not migrated. Furthermore, the virtual machine 2003 with the virtual machine identifier LPAR3 and the virtual machine 2002 with the virtual machine identifier LPAR2 are set to prohibit the separation into different host computers 1002. Here, the virtual machines 2003 and 2002 with the virtual machine identifiers of LPAR3 and LPAR2 indicate that the dependence is very strong.

Thereafter, the current time is stored in the update time area 1740 of the dependency determination condition 351 (FIG. 17) (S990), and the fact that the dependency determination condition 351 has been updated is updated by the virtual machine dependency management unit 305 ( (S995).
According to this embodiment, the virtual computer system 10 can set conditions for determining the degree of dependence between the virtual computers 200.

Next, with reference to FIGS. 10 and 13, the inter-virtual computer dependency determination processing 354 in the virtual computer dependency management unit 305 will be described.
FIG. 13 shows an example of the contents of the virtual machine dependency information 352 (FIG. 5). In the field 1310 and the field 1320, the identification information of the virtual machine 200 running in the virtual machine system 10 is registered. In the virtual machine dependency information 352, dependency information between two virtual machines is stored in the lattice field of the field 1310 and the field 1320. The lattice field representing the virtual machine 200 having the same two virtual machine identification information stores the migration condition set in the virtual machine 200 set in the direct condition area 1730 (FIG. 17) of the virtual machine dependency determination condition 351. To do.

  Of the two virtual machine identification information, in the lattice field in which the identification information of the virtual machine 200 indicated by the field 1310 is larger than the identification information of the virtual machine 200 indicated by the field 1320, the communication path condition area of the virtual machine dependency determination condition 351 Dependency information based on the communication path condition set in 1710 (FIG. 17) is stored.

Among the two virtual machine identification information, the communication history condition area of the virtual machine dependence determination condition 351 is included in a lattice field in which the identification information of the virtual machine 200 indicated by the field 1310 is smaller than the identification information of the virtual machine 200 indicated by the field 1320. Dependency information based on the communication history condition set in 1720 (FIG. 17) is stored.
The field 1340 stores the update time of the virtual machine dependency information.

The virtual machine dependence determination process 354 will be described with reference to FIG.
First, the virtual machine dependency determination processing program 354 accepts a dependency determination request between virtual machines (S1005). Then, it is determined whether or not the condition update time 1740 (FIG. 17) of the virtual machine dependency determination condition 351 is greater than the dependency information update time 1340 of the virtual machine dependency information 352 (S1010). As a result of the determination, if it is determined that the condition update time 1740 (FIG. 17) is not greater than the dependency information update time 1340, the process proceeds to step S1050. On the other hand, if it is determined that the condition update time 1740 (FIG. 17) is greater than the dependency information update time 1340, the process proceeds to step S1015.

  In step S <b> 1015, it is determined whether a direct condition is set in the virtual machine dependency determination condition 351. As a result of the determination, if it is determined that the direct condition is not set, the process proceeds to step S1050. On the other hand, if it is determined that the direct condition is set, the process proceeds to step S1020.

  In S1020, it is determined whether or not the direct condition set in the virtual machine dependency determination condition 351 is a migration prohibition. As a result of the determination, if it is determined that the direct condition is not prohibition of the transition, the process proceeds to step S1025. On the other hand, if it is determined that the direct condition is prohibition of migration, the process proceeds to step S1025. In S1025, the migration prohibition “o” mark is stored in the lattice field of the field 1310 and the field 1320 in which the two virtual machine identification information of the virtual machine dependency information 352 is the same and directly matches the condition. .

  In S1030, it is determined whether or not the direct condition set in the virtual machine dependency determination condition 351 is migration recommendation. As a result of the determination, if it is determined that the direct condition is not migration recommendation, the process proceeds to step S1040. On the other hand, if it is determined that the direct condition is prohibition of transition, the process proceeds to step S1035. In S1035, the migration recommendation “x” mark is stored in the lattice field of the field 1310 and the field 1320 in which the two virtual machine identification information of the virtual machine dependency information 352 is the same and directly matches the condition. .

  In S1040, it is determined whether the direct condition set in the virtual machine dependency determination condition 351 is a non-separable condition. As a result, when it is determined that the direct condition does not include the non-separable condition, the process proceeds to step S1050. On the other hand, if it is determined that the direct condition includes a non-separable condition, the process proceeds to step S1045. In S <b> 1045, the “impossible” mark that cannot be separated is stored in the lattice field of the field 1310 and the field 1320 corresponding to the two virtual machine identification information designated as unseparable in the virtual machine dependency information 352.

  In S1050, it is determined whether or not the update time field 740 of the virtual machine communication path information 341 is greater than the condition update time 1740 (FIG. 17) of the virtual machine dependence determination condition 351. As a result, if it is determined that the update time field 740 is not greater than the condition update time 1740 (FIG. 17), the process proceeds to step S1065. On the other hand, if it is determined that the update time field 740 is greater than the condition update time 1740 (FIG. 17), the process proceeds to step S1055. In S1055, the virtual machine communication path information 341 is checked, and the latest communication path information between the two virtual machines is acquired. Then, the communication path condition 1710 of the virtual machine dependency determination condition 351 corresponding to the communication path information acquired in S1055 is checked, and the dependency value specified for the target communication path is changed to the specified two virtual machine identification information. Are stored in the lattice field of the field 1310 and the field 1320 corresponding to (S1060).

  Next, in S1065, the effective period of the communication history condition 1720 of the virtual machine dependence determination condition 351 is acquired, and communication history information within the effective period is selected from the inter-virtual machine communication history information 342 (FIG. 8). In S1070, the number of communications is calculated for each combination of two virtual machines from the communication history information selected in S1065, the number of communications per effective period is calculated, and it is determined whether or not the frequency condition of the communication history condition 1720 is greater. . As a result, if it is determined that the communication frequency is not greater than the frequency condition of the communication history condition 1720, the process proceeds to step S1080. On the other hand, if it is determined that the communication frequency is greater than the frequency condition of the communication history condition 1720, the process proceeds to step S1075. In S1075, the dependency value specified in the communication history condition 1720 of the virtual machine dependence determination condition 351 used in S1070 corresponds to the two specified virtual machine identification information, and the lattice field of the field 1310 and the field 1320 To store.

In S1080, the communication amount is obtained for each combination of two virtual machines from the communication history information selected in S1065, and the communication amount within the valid period is added. Then, in S1085, it is determined whether the communication amount obtained in S1080 is larger than the communication amount condition of the communication history condition 1720. As a result of the determination, if it is determined that the communication amount is not larger than the communication amount condition of the communication history condition 1720, the process is terminated. On the other hand, if it is determined that the communication amount is larger than the communication amount condition of the communication history condition 1720, the process proceeds to step S1090. In S1090, the dependency value specified in the communication history condition 1720 of the virtual machine dependence determination condition 351 used in S1085 corresponds to the two specified virtual machine identification information, and a lattice field of the field 1310 and the field 1320. To store.
According to this embodiment, the virtual machine system 10 can determine the degree of dependence between the virtual machines 200 and store the degree of dependence information.

Next, the inter-virtual computer communication history generation process 343 in the inter-virtual computer communication management unit 304 will be described with reference to FIGS.
FIG. 8 shows an example of the contents of the virtual machine communication history information 342 of the inter-virtual machine communication management unit 304 (FIG. 4). The field 810 stores identification information of the virtual machine 200 that is the transmission source, the field 820 stores the size of the communication data, the field 830 stores the identification information of the virtual machine 200 that is the transmission destination, The field 840 stores the occurrence time of communication between virtual machines.

With reference to FIG. 16, the inter-virtual machine communication history generation processing will be described.
First, the communication history generation program 343 detects that communication between virtual machines has been completed by the communication execution program 344 (S1610). Then, an entry for storing new history information is added to the virtual machine communication history information 342 (S1620). Next, the inter-virtual machine communication history information is stored in the new entry (S1630). The inter-virtual machine communication history information includes transmission source virtual machine identification information in field 810, communication size in field 820, transmission destination virtual machine identification information in field 830, and communication occurrence time in field 840.

Subsequently, a communication path between virtual machines used by the communication execution program 344 is acquired (S1640). Then, it is determined whether or not the communication path between the virtual machines acquired in S1640 is equal to the communication path corresponding to the transmission source and destination virtual machines registered in the virtual machine communication path information 341 (FIG. 7) (S1650). . As a result of the determination, if it is determined that the communication path is registered, the process ends. On the other hand, if it is determined that the communication path is different from the registered communication path, the process proceeds to S1660.
In S1660, the communication path information 730 corresponding to the transmission source and transmission destination virtual machines in the virtual calculation period communication path information 341 (FIG. 7) is updated to the latest path information acquired in S1640.

As a result of the above processing, the virtual machine communication history information 342 includes the history of sending 512 bytes from the source virtual machine LPAR1 to the destination virtual machine LPAR2 at time t1, and 32 bytes from the source virtual machine LPAR2 to the destination virtual machine. The history sent to LPAR1 at time t2 and the history sent from the source virtual machine LPAR3 to 4096 bytes to the destination virtual machine LPAR4 at time t3 are stored.
According to this embodiment, the communication history information between the virtual machines 200 can be held in the virtual machine system 10. Even when the communication path between virtual machines is changed, the latest communication path information can be registered.

  Next, the virtual machine dependence information display processing 603 in the management apparatus 500 will be described with reference to FIGS. FIG. 19 shows an example of the dependency information display operation of the virtual machine and the dependency information display screen displayed on the display device 505 of the management device 500.

The virtual machine dependent information display process will be described with reference to FIG.
First, the CPU 502 of the management device 500 receives a dependency information display request from the input device 504 (S1810). A field 1910 on the dependency information display screen 1900 indicates a command for inputting this request. A field 1920 is a dependency information display field for responding to this request.

  Next, the virtual machine dependence information 352 (FIG. 13) of the host computer 100 is input (S1820). Then, the virtual machine dependency information 352 is checked, the virtual machine identification information designated as migration recommendation is displayed, the virtual machine identification information designated as migration prohibited is displayed, and designated as non-separable 2 One or more pieces of virtual machine identification information are displayed (S1825). Next, it is determined whether there are a plurality of dependency numerical values of the same virtual computer pair in the virtual computer dependency information 352 (S1830). As a result, if it is determined that only one dependency value is registered, the process advances to step S1850. On the other hand, if it is determined that a plurality of dependence values are registered, the process advances to step S1840.

  In S1840, the values other than the maximum value among the numerical values of the dependency of the same virtual computer pair registered in the virtual computer dependency information 352 are deleted. Then, dependency values of all virtual computer pairs registered in the virtual machine dependency information 352 are displayed on the dependency information display screen 1900 in descending order (S1850).

As a result of the above-described processing, “LPAR1” in which “×” is registered in the virtual calculation period dependency information 352 as migration recommended virtual computer identification information in the dependency information display field 1920 is used as migration prohibited virtual computer identification information. “LPAR2” in which the “○” mark is registered in the virtual calculation period dependency information 352 is stored as “unusable” mark in the inter-virtual computer dependency information 352 as “unseparable virtual machine identification information”. “LPAR2-LPAR3” can be displayed as dependency information, indicating that LPAR1 and LPAR2 have a dependency of 80 and LPAR1 and LPAR4 have a dependency of 70 in descending order of dependency.
According to this embodiment, the management device 500 can display the dependency information of the virtual machine 200.

  Next, the virtual machine migration procedure processing 604 in the management apparatus 500 will be described with reference to FIGS. 11 and 12. FIG. 11 shows the flow of the migration procedure process of the virtual machine. FIG. 12 shows an example of a virtual computer migration operation and a warning message display screen displayed on the display device 505 of the management device 500.

  Referring to FIG. 11, first, the CPU 502 of the management apparatus 500 accepts a virtual machine migration request from the input apparatus 504 (S1110). A field 1210 of the migration operation screen 1200 is a command for inputting this request. A field 1220 is a migration procedure result display field for responding to this request.

Next, the virtual machine identification information requested to be migrated is acquired from the information input in the field 1210 (S1120). Then, the virtual machine dependency information 352 is input (S1130). Next, it is determined whether the migration target virtual machine is designated as a migration prohibited virtual machine in the virtual machine dependency information 352 (S1140). As a result, if it is determined that the virtual machine is designated as a migration-prohibited virtual machine, the process proceeds to S1175.
In S1175, the reason “designated as a migration prohibited virtual machine” is set as the migration warning text. On the other hand, if it is determined that the virtual machine is not designated as a migration-prohibited virtual machine, the process proceeds to S1150.

  Next, in S1150, it is determined whether the migration target virtual machine is designated as a migration recommended virtual machine in the virtual machine dependency information 352 (S1150). As a result, if it is determined that the virtual machine is designated as a migration recommended virtual machine, the process advances to step S1190 to start a virtual machine migration process. On the other hand, if it is determined in S1150 that the virtual machine is not designated as a migration recommended virtual machine, the process advances to step S1160.

  In S1160, the virtual machine to be migrated determines whether there is virtual machine pair information with a large degree of dependence in the virtual machine dependence information 352. As a result, for example, if it is determined that there is no virtual machine pair whose dependency is greater than 50, the process advances to step S1190. On the other hand, if it is determined that there is a virtual machine pair whose dependency is greater than 50, the process proceeds to S1170. In S1170, the reason that “a virtual machine with a large dependency exists” is set as the migration warning text. Then, a warning text relating to migration of the designated virtual machine is displayed in the field 1220 (S1180). Thereafter, when an input agreeing to the migration process is detected (S1185), the process proceeds to process S1190.

As a result of the above processing, since the dependency obtained from the communication path between LPAR2 and LPAR1 is registered as a high value “80” in the virtual machine dependency information 352 in response to a request to migrate LPAR2, FIG. As shown, a warning message that the LPAR2 communication path matches the non-separable condition can be displayed in the field 1220 of the display screen.
According to this embodiment, the management apparatus 500 can display a warning message for a migration request of the virtual machine 200.

Next, with reference to FIG. 15 and FIG. 20, a process 353 for managing the configuration information of the virtual machine in the virtual machine dependence management unit 305 will be described.
In FIG. 15, when the virtual machine information management program 353 detects the occurrence of a configuration change in the virtual machine system 10 (S1510), it is next determined whether the configuration change is a start of a new virtual machine (S1520). As a result, if it is determined that the virtual machine is not started, the process proceeds to step S1540. On the other hand, if it is determined that the virtual machine is activated, the process proceeds to S1530. In S1530, the communication path information of the newly activated virtual machine is additionally registered in the virtual machine communication path information 341 (FIG. 4).

In S1540, it is determined whether the configuration change is the end of the virtual machine. As a result, if it is determined that the virtual machine is not terminated, the process is terminated. On the other hand, if it is determined that the virtual machine has ended, the process advances to step S1550. In S1550, the related information entry is deleted. That is, the communication path information of the virtual machine to be ended is deleted from the virtual machine communication path information 341 (FIG. 4), the communication history regarding the virtual machine to be ended is deleted from the virtual machine communication history information 342 (FIG. 4), The dependency information related to the virtual computer to be ended is deleted from the computer dependency information 352 (FIG. 5), and the direct condition related to the virtual computer to be ended is deleted from the virtual computer dependency determination condition 351 (FIG. 5).

FIG. 20 shows an example of the contents of the virtual machine communication path information 341 (FIG. 4) after the virtual machine addition activation. In this embodiment, when LPAR5 is added, a field 750 is added to store information indicating that the communication path used by LPAR5 is a direct memory access circuit.
As described above, in the virtual machine system 10, the information held by the inter-virtual machine communication management unit 304 and the virtual machine dependency management unit 305 is updated with the configuration of the latest virtual machine in accordance with the activation and termination of the virtual machine 200. Can be updated.

  According to the management of virtual machines in the present embodiment, it is possible to set conditions for determining the degree of dependence between virtual machines 200. Moreover, the dependence degree between the virtual machines 200 can be determined and dependence degree information can be stored. Furthermore, the latest communication path information between the virtual machines 200 can be registered. In addition, the information held by the inter-virtual computer communication management unit 304 and the virtual computer dependency management unit 305 can be updated to the latest virtual computer configuration in accordance with the activation and termination of the virtual computer 200.

In the management apparatus 500, dependency information between virtual machines 200 can be displayed. Further, in response to a request to migrate the virtual machine 200, when the reliability is lowered by migrating the virtual machine 200 to a different host computer 100, it is possible to display a warning message prompting the migration to be stopped.

The figure which shows the structure of the virtual machine system in one Example. The figure which shows the structure of the hardware of the computer system by which a virtual machine system is implement | achieved. 1 is a diagram showing a system configuration in which virtual machines on different host computers communicate using physical lines. The figure which shows the internal structure of the communication management part 304 between virtual machines. The figure which shows the internal structure of the virtual machine dependence management part 305. The figure which shows schematically the internal structure of the memory 503 of the management apparatus 500. The figure which shows an example of virtual computer communication path information. The figure which shows an example of virtual computer communication log | history information. The flowchart which shows the flow of a dependence condition setting process. The flowchart which shows the flow of a virtual machine dependence determination process. The flowchart which shows the flow of the migration procedure process of a virtual machine. The figure which shows an example of transfer operation and a warning display screen of a virtual machine. The figure which shows an example of virtual machine dependence information. The figure which shows the attribute of the communication path between virtual machines. The flowchart which shows the flow of a virtual machine information management process. The flowchart which shows the flow of the communication history production | generation process between virtual machines. The figure which shows an example of virtual computer dependence determination conditions. The flowchart which shows the flow of a virtual machine dependence information display process. The figure which shows an example of the dependence information display operation of a virtual computer, and a dependence information display screen. The figure which shows an example of the virtual machine communication path information after the additional starting of a virtual machine.

Explanation of symbols

  10: Virtual computer system 100: Host computer 101: Communication device 102: CPU 103: Memory 104: Input device 105: Display device 106: Interface 107: Physical line network 200: Virtual computer 201: Guest OS 202: Virtual communication device 300: Hypervisor 301: Communication device emulator 304: Inter-virtual computer communication management unit 305: Virtual computer dependency management unit 400: Storage device 500: Management device 1410: Direct memory access circuit 1420: Inter-virtual communication device memory copy processing unit 1430: Communication Device data copy processing unit.

Claims (12)

In a virtual computer system having a plurality of virtual computers that are connected via a communication line and that can be formed on the physical computer, and a hypervisor that executes communication processing between the plurality of virtual computers A communication management unit that monitors communication processing between the plurality of virtual machines, and a dependency determination unit that determines the degree of dependence between the virtual machines using information from the communication management unit. A virtual computer formed on a certain physical computer to another virtual computer formed in the same physical computer or in a virtual computer formed on another physical computer according to the determination by the dependency determination unit A virtual computer system characterized by presenting whether or not to migrate to a computer. The communication management unit holds communication path information between the virtual machines,
The virtual machine system according to claim 1, wherein the dependence degree determination unit determines the dependence degree between the virtual machines using the communication path information. The communication management unit holds communication history information between the virtual machines,
The virtual machine system according to claim 1, wherein the dependence degree determination unit determines the degree of dependence between virtual machines using the communication history information. The dependence determination unit holds at least one condition for determining the dependence,
The virtual computer system according to claim 1, wherein the hypervisor includes a dependency condition setting unit that changes a condition for determining the dependency. A management device connected to the plurality of physical computers for managing the virtual machine;
The management device has an input unit for inputting a request to migrate the virtual machine formed on a physical computer to another physical computer and a determination result of the dependency determination unit, and is specified by the input unit , A means for determining whether there is a virtual machine having a strong dependency with a virtual machine requested to be migrated, and if there is a virtual machine with a strong dependency as a result of the determination by the determination means, a warning for the migration request is issued. The virtual computer system according to claim 1, further comprising an output unit that outputs the virtual computer system. 6. The virtual computer system according to claim 5, wherein the management device outputs dependency information between the virtual computers to the output unit. The dependency determination unit prohibits migration of the virtual machine to another virtual machine when it is determined that the virtual machine is connected using a physical communication line by migration. The virtual computer system according to claim 2. 4. The virtual computer according to claim 3, wherein the dependency determination unit determines the dependency between the virtual computers based on information relating to an effective period of the communication history information, a communication frequency, and a threshold of a communication amount. system. In a virtual computer system having a plurality of virtual computers that are connected via a communication line and can be formed on the physical computer, and a hypervisor that executes communication processing between the plurality of virtual computers A virtual machine management method,
There are a communication management step for monitoring communication processing between the plurality of virtual machines, a dependency determination step for determining the dependency between the virtual machines, and a determination of the dependency related to the communication management. Presenting whether or not the virtual machine formed on the physical computer can be migrated to another virtual machine formed in the same physical computer or to a virtual machine formed on another physical computer. A management method of a virtual machine, comprising: 10. The communication management step of the virtual computer according to claim 9, wherein in the communication management step, communication path information between the virtual machines is held, and the dependence between the virtual machines is determined using the held communication path information. Management method. 10. The virtual management system according to claim 9, wherein in the communication management unit step, communication history information between the virtual computers is held, and the dependence between the virtual computers is determined using the held communication history information. Computer management method. In a virtual computer system having a plurality of virtual computers that are connected via a communication line and that can be formed on the physical computer, and a hypervisor that executes communication processing between the plurality of virtual computers A program for managing virtual machines executed on the hypervisor, the communication management function for monitoring communication processing between the plurality of virtual machines, and the degree of dependence for determining the degree of dependence between the virtual machines In response to the determination function and the determination of the dependency in relation to the communication management, the virtual machine formed on one physical computer can be transferred to another virtual machine formed in the same physical computer or another A function for presenting whether or not to migrate to a virtual machine formed on a physical computer, and for managing a virtual machine characterized by realizing Program.

Images