JPWO2019003286A1 - Virtual machine management apparatus and management method - Google Patents

Abstract

[PROBLEMS] To secure expected communication performance between a plurality of virtual machines even after rearranging virtual machines to be rearranged. A management apparatus for managing a plurality of virtual machines operating on a physical machine, and rearranging in consideration of a physical component of the physical machine in addition to a communication capacity between the plurality of virtual machines Determine the placement of the target virtual machine and place it.

Description

  The present invention relates to a virtual machine management apparatus and management method, and is particularly suitable for application to a management apparatus related to a technique for managing a virtual machine operating on a physical machine.

  Conventionally, when a plurality of virtual machines are arranged on a plurality of physical machines, the plurality of virtual machines are arranged on the same physical machine as much as possible in consideration of the communication capacity between the plurality of virtual machines. (See Patent Document 1).

JP 2010-140134 A

  However, the physical server components used by these multiple virtual machines are not taken into account, so when attempting to relocate some virtual machines, these virtual machines must be relocated before relocating. Communication performance as expected between multiple virtual machines could not be ensured reliably.

  The present invention has been made in consideration of the above points, and provides a virtual machine management apparatus and management method capable of ensuring the expected communication performance between a plurality of virtual machines even after rearranging the virtual machines to be rearranged. It is what we are going to propose.

  In order to solve such a problem, in the present invention, a virtual machine management apparatus that manages the arrangement of a plurality of virtual machines running on a physical machine, and manages the communication capacity between the plurality of virtual machines. A communication information management unit, a physical component management unit that manages physical components of the physical machine among the plurality of virtual machines, and a virtual machine among the plurality of virtual machines according to the communication capacity and the physical components. A placement destination determination unit that determines a placement destination of a placement target virtual machine.

  Further, according to the present invention, there is provided a virtual machine management method executed by a management apparatus that manages the arrangement of a plurality of virtual machines that are operating on a physical machine, wherein the management apparatus includes a plurality of virtual machines. A communication information management step for managing a communication capacity in the network, a physical component management step in which the management device manages a physical component of the physical machine between the plurality of virtual machines, and the management device includes the communication capacity and An arrangement destination determining step of determining an arrangement destination of a virtual machine to be rearranged among the plurality of virtual machines according to the physical component.

  According to the present invention, it is possible to ensure communication performance as expected between a plurality of virtual machines even after rearranging the virtual machines to be rearranged.

It is a block diagram which shows schematic structure of the management apparatus of the virtual machine by this Embodiment. It is a block diagram which shows schematic structure of the management apparatus of the virtual machine by this Embodiment. FIG. 3 is a diagram illustrating a configuration example of a physical machine ID management table illustrated in FIG. 2. It is a figure which shows the structural example of the physical CPU management table shown in FIG. FIG. 3 is a diagram illustrating a configuration example of a physical memory management table illustrated in FIG. 2. FIG. 3 is a diagram illustrating a configuration example of a virtual switch management table illustrated in FIG. 2. It is a figure which shows the structural example of the physical IO interface management table shown in FIG. FIG. 3 is a diagram illustrating a configuration example of a virtual machine ID management table illustrated in FIG. 2. It is a figure which shows the structural example of the virtual CPU management table shown in FIG. FIG. 3 is a diagram illustrating a configuration example of a virtual memory management table illustrated in FIG. 2. FIG. 3 is a diagram illustrating a configuration example of a virtual IO interface connection destination virtual switch management table illustrated in FIG. 2. FIG. 3 is a diagram illustrating a configuration example of a virtual machine arrangement priority definition table illustrated in FIG. 2. It is a figure which shows the structural example of the communication information management table between virtual machines shown in FIG. It is a figure which shows the structural example of the reallocation object virtual machine table shown in FIG. It is a figure which shows an example of the arrangement | positioning candidate table shown in FIG. FIG. 3 is a diagram illustrating a configuration example of a virtual machine arrangement priority definition table illustrated in FIG. 2. It is a figure which shows the structural example of the communication feeling definition table between virtual machines shown in FIG. It is a flowchart which shows an example of a measurement process. It is a flowchart which shows an example of a virtual machine rearrangement process. FIG. 20 is a flowchart showing a continuation of the virtual machine rearrangement process shown in FIG. 19. FIG.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

(1) Virtual Machine Management System According to this Embodiment (1-1) System Configuration FIGS. 1 and 2 show a schematic configuration of a computer system 1 according to this embodiment. Although FIG. 1 and FIG. 2 should originally be represented as one drawing, they are represented separately for the sake of explanation. 1 mainly illustrates a configuration example of the first physical machine 121A to the Nth (N: natural number) physical machine 121N, and FIG. 2 mainly illustrates the configuration of the management server 101 to which the storage unit 111 is connected. An example is shown.

  The computer system 1 includes a plurality of physical machines 121A to 121N illustrated in FIG. 1 as the at least one physical machine connected by the network 131, and the management server 101 illustrated in FIG. Since the plurality of physical machines 121A to 121N have substantially the same configuration, the following description of the configuration mainly exemplifies the first physical machine 121A unless it is necessary to refer to other physical machines.

  The first physical machine 121A includes, for example, three virtual machines 122A1, 122A2, 122A3, a virtualization engine unit 123A, a NUMA0-side physical memory 124A0, a 0-side physical CPU socket 125A0 and an IO interface 126A0, and a NUMA1-side physical. A memory 124A1, a physical CPU socket 125N1 on one side, and an IO interface 126N0 are provided.

  The NUMA0 side physical memory 124A0, the 0 side physical CPU socket 125A0 and the IO interface 126A0 constitute one node, while the NUMA1 side physical memory 124A1 and the 1 side physical CPU socket 125N1 and the IO interface 126N0 Another node is configured.

  The NUMA0-side physical memory 124A0 is used as a work area for a physical CPU that is a central processing unit mounted in the 0-side physical CPU socket 125A0. The IO interface 126A0 is an interface between a physical CPU and the outside, for example, a so-called PCI (Peripheral Component Interconnect) bus. On the other hand, in the physical memory 124A1 on the NUMA1 side, a physical CPU that is a central processing unit mounted on the physical CPU socket 125N1 on the one side is used as a work area. The IO interface 126N0 is an interface between the physical CPU and the outside, for example, a so-called PCI bus.

  The virtualization engine unit 123A includes a plurality of virtual CPU cores 131A, a plurality of virtual memories 132A, a plurality of virtual switches 133A, and a plurality of virtual IO interfaces 134A.

  In the following description, when there is no need to specify the virtual machine 122A1 or the like, the description may be omitted.

  The management server 101 shown in FIG. 2 includes a virtual machine configuration management unit 102, a physical machine configuration management unit 103, an inter-virtual machine communication information management unit 104, a virtual machine placement priority change unit 105, and a virtual machine relocation execution unit 106. ing.

  The virtual machine configuration management unit 102 has a function of managing the configurations of a plurality of virtual machines.

  The physical machine configuration management unit 103 has a function of managing a plurality of physical machines 121A to 121N.

  The inter-virtual machine communication information management unit 104 has a function of managing communication information between the first virtual machines 122A1, 122A2, and 122A3 to the Nth virtual machines 122N1, 122N2, and 122N3.

  The virtual machine arrangement priority changing unit 105 sets an arrangement priority indicating the degree of communication capacity that can be expected according to the arrangement between the first virtual machines 122A1, 122A2, and 122A3 to the Nth virtual machines 122N1, 122N2, and 122N3. Has the function to change.

  The virtual machine rearrangement execution unit 106 has a function of rearranging any one of the first virtual machines 122A1, 122A2, and 122A3 to the Nth virtual machines 122N1, 122N2, and 122N3. Details of the virtual machine rearrangement execution unit 106 will be described later.

  On the other hand, the storage unit 111 is a database device, for example, and stores the following table. That is, the storage unit 111 includes a physical machine ID management table 151, a physical CPU management table 152, a physical memory management table 153, a virtual switch management table 154, and a physical IO interface management table 155 as a physical machine related table group. The storage unit 111 includes a virtual machine ID management table 141, a virtual CPU management table 142, a virtual memory management table 143, a virtual IO interface connection destination virtual switch management table 144, a virtual machine placement destination physical machine management as a virtual machine related table group. A table 145 and a virtual machine communication information management table 146 are provided. The storage unit 111 further includes a rearrangement target virtual machine table 161 and an arrangement candidate table 162 as a rearrangement table group. The storage unit 111 includes a virtual machine arrangement priority definition table 171 and a virtual machine communication interval definition table 172 as a definition table group.

(1-2) Table Configuration FIG. 3 shows a configuration example of the physical machine ID management table 151. The physical machine ID management table 151 has a physical machine ID as its column, and manages the identifiers of physical machines existing in the system.

  FIG. 4 shows a configuration example of the physical CPU management table 152. The physical CPU management table 152 has, as its columns, the physical machine ID, the CPU socket number, and the number of cores per CPU socket. For each physical machine existing in this system, the CPU socket number and the CPU socket number. (CPU) Managing the number of cores.

  FIG. 5 shows a configuration example of the physical memory management table 153. The physical memory management table 153 includes, as its columns, a physical machine ID, a CPU socket number, a NUMA number, and a memory capacity (GB) per 1 NUMA, and manages a physical configuration for each physical machine.

  FIG. 6 shows a configuration example of the virtual switch management table 154. The virtual switch management table 154 has, as its columns, a physical machine ID, a virtual switch, a transmission band [Gbps] and a reception band [Gbps], and manages the transmission band and the reception band for each virtual switch of the physical machine. .

  FIG. 7 shows a configuration example of the physical IO interface management table 155. The physical IO interface management table 155 includes, as its columns, a physical machine ID, an IO interface number, a CPU socket number, a NUMA number, a virtual switch, a transmission bandwidth [Gbps], and a reception bandwidth [Gbps]. Is managing.

  FIG. 8 shows a configuration example of the virtual machine ID management table 141. The virtual machine ID management table 141 has a virtual machine ID as its column, and manages each virtual machine existing in this system.

  FIG. 9 shows a configuration example of the virtual CPU management table 142. The virtual CPU management table 142 has, as its columns, a virtual machine ID, the number of virtual CPUs, and virtual CPU affinity, and manages the configuration of the virtual memory.

  FIG. 10 shows a configuration example of the virtual memory management table 143. The virtual memory management table 143 has virtual machine ID, virtual memory capacity [GB], and NUMA affinity as its columns, and manages the configuration of virtual memory for each virtual machine.

  FIG. 11 shows a configuration example of the virtual IO interface connection destination virtual switch management table 144. The virtual IO interface connection destination virtual switch management table 144 has a virtual machine ID, a virtual ID interface number, and a connection destination virtual switch as its columns, and manages the interface-related configuration for each virtual machine.

  FIG. 12 shows a configuration example of the virtual machine placement destination physical machine management table 145. The virtual machine placement destination physical machine management table 145 has a virtual machine ID and a physical machine ID as its columns, and manages each virtual machine operating on each physical machine.

  FIG. 13 shows a configuration example of the inter-virtual machine communication information management table 146. The inter-virtual machine communication information management table 146 includes, as columns, a communication ID, a transmission source virtual machine ID, a transmission source virtual machine ID, a communication capacity [Gbps], an arrangement priority, a current arrangement, and a measurement start time.

  This inter-virtual machine communication information management table 146 includes, for each communication ID for identifying a plurality of communications, a transmission source virtual machine indicated by the transmission source virtual machine ID and a transmission destination virtual machine indicated by the transmission destination virtual machine ID. The communication capacity [Gbps], the arrangement priority, the current arrangement which is a value representing the current arrangement, and the measurement start time are managed.

  FIG. 14 shows a configuration example of the reallocation target virtual machine table 161. The reallocation target virtual machine table 161 includes, as its columns, a communication ID, a transmission source virtual machine ID, a transmission source virtual machine ID, a communication capacity [Gbps], an arrangement priority, a current arrangement, and a measurement start time. The columns of the reallocation target virtual machine table 161 are the same as the columns of the inter-virtual machine communication information management table 146.

  The rearrangement target virtual machine table 161 is different from the inter-virtual machine communication information management table 146 in that the information about only the rearrangement target virtual machine is managed.

  FIG. 15 shows a configuration example of the arrangement candidate table 162. The placement candidate table 162 includes, as its columns, a communication ID, a transmission source virtual machine ID, a transmission destination virtual machine ID, a physical machine ID, a CPU socket number, a NUMA number, and a virtual switch.

  This arrangement candidate table 162 manages combinations of a transmission source virtual machine and a transmission destination virtual machine as arrangement candidates on a certain physical machine for each communication ID.

  FIG. 16 shows a configuration example of the virtual machine arrangement priority definition table 171. The virtual machine placement priority definition table 171 has placement status and placement priority as its columns, and manages the priority (placement priority) of the placement status of the virtual machine on the physical machine.

  FIG. 17 shows a configuration example of the inter-virtual machine communication interval definition table 172. The inter-virtual machine communication interval definition table 172 has a communication ID and an acquisition interval [minute] as its columns, and manages the acquisition interval for each communication represented by the communication ID. This acquisition interval is a time interval used in a measurement process (see FIG. 18) described later.

(2) Virtual Machine Management Method The computer system 1 according to this embodiment has the above-described configuration. Next, an operation example of the computer system 1 will be described. In the present embodiment, after the measurement process is executed, the virtual machine rearrangement process is executed.

(2-1) Measurement Process FIG. 18 shows an example of the measurement process. In this measurement process, with the passage of time, it is determined whether to increase or maintain the arrangement priority described later.

  In the management server 101, the inter-virtual machine communication information management unit 104 reads and sets the acquisition interval [minute] corresponding to the communication ID recorded in the inter-virtual machine communication interval definition table 172 (see FIG. 17) (step S1). . The management server 101 actually measures the communication capacity (hereinafter referred to as “measured communication capacity”) at each acquisition interval (step S2).

  Next, in the management server 101, the inter-virtual machine communication information management unit 104 obtains the latest communication capacity [Gbps] and the current arrangement for each communication ID from the inter-virtual machine communication information management table 146 (see FIG. 13) (steps). S3).

  Next, in the management server 101, the virtual machine arrangement priority changing unit 105 compares the actually measured communication capacity acquired in step S2 with the latest communication capacity acquired in step S3 (step S4).

  As a result of the comparison, if | the latest communication capacity−actual communication capacity |> threshold and the latest communication capacity <actual communication capacity (when the communication capacity decreases), the management server 101 uses the virtual The machine arrangement priority changing unit 105 holds a value that is lowered by one level (subtracted by one) from the value indicating the current arrangement acquired in step S3 (step S5).

  As a result of the comparison, when | the latest communication capacity−actually measured communication capacity | <= threshold (when the communication capacity is the same), in the management server 101, the virtual machine arrangement priority changing unit 105 acquires in step S3. The value indicating the current arrangement is retained as it is (step S6).

  As a result of the comparison, when | the latest communication capacity−the actual communication capacity |> threshold and the latest communication capacity> the actual measurement communication capacity (when the communication capacity increases), the management server 101 uses the virtual The machine arrangement priority changing unit 105 holds a value that is one step higher than the value representing the current arrangement acquired in step S3 (step S7).

  Next, in the management server 101, the virtual machine placement priority changing unit 105 places the placement priority recorded in step S5 to step S7 in the inter-virtual machine communication information management table 146 (see FIG. 13) and the actual measurement obtained in step S2. The communication capacity and the current arrangement acquired in step S3 are newly registered (step S8).

  As described above, in the management server 101, the virtual machine arrangement priority changing unit 105 performs the “latest communication capacity−measured communication capacity”, which is a difference in communication capacity between a plurality of virtual machines by the measurement process, and “threshold value”. ", The placement priority is updated according to the increase or decrease of the communication capacity between a plurality of virtual machines measured at different times. In this way, the virtual machine to be rearranged can be arranged in the physical machine so that the communication capacity between the plurality of virtual machines is maintained at least.

(2-2) Virtual Machine Relocation Processing FIG. 19 shows an example of virtual machine relocation processing. In the management server 101, the inter-virtual machine communication information management unit 104 determines, for each communication ID, from the inter-virtual machine communication information management table 146 (see FIG. 13), a transmission source virtual machine ID, a transmission destination virtual machine ID, a communication capacity, The placement priority, the current placement, and the measurement start time are acquired (step S101).

  The management server 101 starts relocation of the virtual machine for information with the latest measurement start time for each communication ID among the information acquired in step S112 (step S102). In the present embodiment, the management server 101 exemplifies relocation of virtual machines for 13:00.

  In the management server 101, the inter-virtual machine communication information management unit 104 determines that the measurement start time corresponds to, for example, 13:00 on February 01, 2017 in the inter-virtual machine communication information management table 146 (see FIG. 13). Are sorted in descending order based on the placement priority (step S103), and the sorted information is stored in the relocation target virtual machine table 161 (see FIG. 14).

  Next, in the management server 101, the virtual machine relocation execution unit 106 selects a combination of virtual machines having the same placement priority from the information stored in the relocation target virtual machine table 161 with another specific priority (for example, Sorting is performed again according to the priority of the application operated at the upper level (step S104).

  Next, in the management server 101, the virtual machine rearrangement execution unit 106 determines whether or not the specific priority is the same (step S105), and when the specific priority is the same, sort again in ascending order according to the unique ID. (Step S106).

  Hereinafter, first, in the management server 101, the virtual machine rearrangement execution unit 106 starts rearrangement of a destination virtual machine among a plurality of virtual machines (step S107). Note that steps after step S116, which will be described later, are processes related to the transmission source virtual machine among the plurality of virtual machines.

  First, in the management server 101, the virtual machine rearrangement execution unit 106 checks whether or not the virtual CPU can be accommodated in the physical CPU (step S108). Specifically, in the management server 101, the virtual machine configuration management unit 102 refers to the virtual CPU management table 142 (see FIG. 9) to acquire the number of virtual CPUs corresponding to the virtual machine ID of the virtual machine, With reference to the physical CPU management table 152 (see FIG. 4), a CPU socket number and a physical machine ID in which the number of virtual CPUs is contained are acquired.

  In the management server 101, if it is determined in step S108 that there is no CPU socket in which the virtual CPU can be accommodated, the virtual machine configuration management unit 102 acquires the CPU socket number and physical machine ID with the largest number of physical CPUs that can be stored. On the other hand (step S109), if it is determined in step S8 that there is a CPU socket in which the virtual CPU can be accommodated, the following step S110 is executed without executing step S9.

  Next, in the management server 101, the virtual machine configuration management unit 102 checks whether or not the virtual memory capacity fits in the physical memory capacity (step S110). Specifically, the virtual machine configuration management unit 102 checks the virtual memory capacity of the virtual machine from the virtual memory management table 143 (see FIG. 10). Further, in the management server 101, the physical machine configuration management unit 103 refers to the physical memory management table 153 (see FIG. 5), and uses the combination of the physical machine ID and the CPU socket number acquired in step S8 or step S9. Get matching information. Further, in the management server 101, the physical machine configuration management unit 103 acquires a NUMA number and a physical machine ID in which the virtual memory capacity can be accommodated from the acquired information. Note that such processing is executed because the communication conditions such as the communication capacity between the transmission source virtual machine and the transmission destination virtual machine are better when the virtual memory and the virtual CPU are arranged in the same node as much as possible. Because.

  In the management server 101, the physical machine configuration management unit 103 acquires the NUMA number and physical machine ID with the largest allocated physical memory capacity when there is no physical memory capacity that can accommodate the virtual memory capacity in step S110. On the other hand (step S111), if there is a physical memory capacity that can accommodate the virtual memory capacity in step S110, the process is executed separately for each placement priority acquired in step S112 (step S112).

  In the management server 101, the virtual machine rearrangement execution unit 106 executes the following step S113 when the obtained placement priority is 1 or 2, while the obtained placement priority is 3 or 4. If so, step S114 to be described later is executed (step S112).

  In step S113, the virtual machine rearrangement execution unit 106 checks whether or not there is a connection switch of the virtual machine, that is, a virtual switch that can accommodate the communication band of the virtual machine. Specifically, the virtual machine relocation execution unit 106 determines whether the physical machine ID and CPU socket number acquired in step S8 or step S9 from the physical IO interface management table 155 (see FIG. 7), and in step S110 or step S111. Information matching the combination of the acquired physical machine ID and NUMA number is confirmed. Further, the virtual machine rearrangement execution unit 106 tries to acquire a virtual switch in which the communication band (transmission band and reception band) of the virtual machine falls from the acquired information.

  When there is a virtual switch that can accommodate the communication bandwidth of the virtual machine, in the management server 101, the virtual machine rearrangement execution unit 106 ends the processing for the transmission destination virtual machine as described above, as in step S116 and later described later. Start processing for the source virtual machine.

  On the other hand, if there is no virtual switch that can accommodate the communication bandwidth of the virtual machine, the virtual machine rearrangement execution unit 106 acquires a virtual switch that maximizes the communication capacity of the virtual machine (step S115), and performs steps S116 and later described later. Execute.

  On the other hand, in step S114, the virtual machine rearrangement execution unit 106 confirms information matching the physical machine ID acquired in step S111 or step S112 from the virtual machine connection destination switch, that is, the virtual switch management table. Specifically, the virtual machine rearrangement execution unit 106 tries to acquire a virtual switch in which the communication band (transmission band and reception band) of the virtual machine falls from the acquired information.

  In the management server 101, the virtual machine rearrangement execution unit 106 executes step S <b> 116 and subsequent steps when there is a virtual switch that can accommodate the virtual machine communication band, while there is a virtual switch that accommodates the virtual machine communication band. Step S115 described above is executed.

  In step S116, the virtual machine relocation execution unit 106 determines whether or not a transmission source relocation candidate has been determined. The virtual machine rearrangement execution unit 106 starts rearranging the transmission source virtual machine if it has not been determined and implements it from step S8 (step S117), and if it has already been determined, executes step S118. .

  In step S118, the virtual machine rearrangement execution unit 106 checks whether the combination of the physical CPU socket, the NUMA number, and the virtual switch exists in the arrangement candidate table 162 (see FIG. 15). In this arrangement candidate table 162, no arrangement candidates exist in the first loop, but arrangement candidates are accumulated through step S121 described later. In the management server 101, the virtual machine rearrangement execution unit 106 executes again from the above-described step S7 when these combinations exist in the arrangement candidate table 162 (see FIG. 15), while these combinations are displayed as arrangement candidates. If not present in the table 162, the following step S119 is executed.

  In this step S119, the virtual machine rearrangement execution unit 106 checks whether or not the rearrangement destination of the pair of the transmission source virtual machine and the transmission destination virtual machine has a configuration designated by the arrangement priority. If the configuration is specified by the placement priority, the virtual machine rearrangement execution unit 106 actually starts the rearrangement of the virtual machine (step S122).

  When the configuration is not specified by the placement priority and all placement combinations are tried, in the management server 101, the virtual machine rearrangement execution unit 106 includes the placement candidate table 162 (see FIG. 15). Therefore, the configuration in which the placement priority is the highest through the processing as described above is adopted (step S120), and the reallocation of the virtual machine is actually started (step S122).

  On the other hand, if the configuration is not specified by the placement priority and all placement combinations have not been tried, the virtual machine rearrangement execution unit 106 in the management server 101 causes the physical CPU socket, NUMA number, and virtual The switch combination is registered in the arrangement candidate table 162 (see FIG. 15), and the search for the rearrangement destination is attempted again (step S121).

  When reallocation of a virtual machine is actually started (step S122), in the management server 101, the virtual machine reallocation execution unit 106 displays a virtual machine representing this virtual machine in the virtual CPU management table 142 (see FIG. 9). The virtual CPU affinity corresponding to the ID is updated (step S123). Here, the affinity represents which socket is attached.

  Next, in the management server 101, the virtual machine relocation execution unit 106 updates the NUMA affinity corresponding to the virtual machine ID representing this virtual machine in the virtual memory management table 143 (see FIG. 10) (step S124).

  Next, in the management server 101, the virtual machine rearrangement execution unit 106 updates the physical machine ID corresponding to the virtual machine ID representing the virtual machine in the virtual machine placement destination physical machine management table 145 (see FIG. 12) ( Step S125).

  Next, in the management server 101, the virtual machine relocation execution unit 106 updates the connection destination virtual switch corresponding to the virtual machine ID representing the virtual machine in the virtual IO interface connection destination virtual switch management table 144 (see FIG. 11). (Step S126).

  Next, in the management server 101, the virtual machine placement priority changing unit 105, after rearranging the virtual machines, sets the source virtual machine ID and the destination virtual machine ID in the inter-virtual machine communication information management table 146 (see FIG. 13). The value of the current arrangement corresponding to the pair is updated with the arrangement priority of the actually arranged virtual machine (step S127), and the process ends.

  As described above, when some virtual machines among a plurality of virtual machines are rearranged, not only the traffic but also the physical components (for example, CPU, memory, PCI) of the physical machines on which the plurality of virtual machines are operated. Since some of the virtual machines will be rearranged in consideration, the physical components of the physical machines are taken into account among the virtual machines even after the rearrangement, as originally assumed. Communication performance can be ensured.

(3) Other Embodiments The above embodiment is an example for explaining the present invention, and is not intended to limit the present invention only to these embodiments. The present invention can be implemented in various forms without departing from the spirit of the present invention. For example, in the above-described embodiment, the processing of various programs is described sequentially, but this is not particularly concerned. Therefore, as long as there is no contradiction in the processing result, the processing order may be changed or the operation may be performed in parallel. Further, the program including each processing block in the above embodiment may be in a form stored in a non-transitory storage medium readable by a computer, for example.

  The present invention can be widely applied to a virtual machine management apparatus and management method when a plurality of virtual machines operate on a physical machine.

  101... Management server, 111... Storage unit, 121 A to 121 N... Physical machine, 122 A to 122 N.

Claims (14)

A virtual machine management device that manages the arrangement of multiple virtual machines running on a physical machine,
A communication information management unit for managing communication capacity between the plurality of virtual machines;
A physical component management unit that manages physical components of the physical machine among the plurality of virtual machines;
An arrangement destination determining unit that determines an arrangement destination of a virtual machine to be relocated among the plurality of virtual machines according to the communication capacity and the physical configuration element;
A virtual machine management apparatus comprising: The physical component management unit
Managing communication condition information including communication conditions according to the physical components of the physical machine;
The communication information management unit
While managing the placement priority indicating the degree of communication capacity that can be expected according to the placement between the plurality of virtual machines, the placement priority according to the increase or decrease of the communication capacity between the plurality of virtual machines measured at different times Update the degree,
The placement destination determination unit
According to the communication condition information and the placement priority, a plurality of placement destination candidates for a virtual machine to be relocated among the plurality of virtual machines are accumulated, and one placement destination candidate is determined from the plurality of placement search candidates. The virtual machine management device according to claim 1. The communication information management unit
Along with the communication capacity between the plurality of virtual machines, managing an index value representing the current arrangement of the virtual machine to be relocated,
The placement destination determination unit
When the performance of the virtual component of the relocation target virtual machine is within the range of the performance of the physical component of the physical machine, the relocation target virtual machine is relocated, and the communication information management unit The virtual machine management apparatus according to claim 2, wherein an index value indicating a current arrangement of the virtual machine to be relocated that is managed is updated. A virtual component management unit that manages each virtual component of the plurality of virtual machines;
The placement destination determination unit
The virtual component according to claim 3, wherein when the virtual machine to be rearranged is rearranged, each virtual component of the plurality of virtual machines managed by the virtual component management unit is updated. Machine management device. The physical component is at least:
A central processing unit of the physical machine;
A memory used as a work area by the central processing unit;
An interface between the central processing unit and the outside;
The virtual machine management device according to claim 1, comprising: The plurality of virtual machines are:
The virtual machine management apparatus according to claim 5, wherein the virtual machine management apparatus operates on one physical machine having a plurality of nodes including the physical components. There are a plurality of the physical machines,
6. The virtual machine management apparatus according to claim 5, wherein the plurality of virtual machines are operating on the plurality of physical machines each including the physical component. A virtual machine management method executed by a management device that manages the arrangement of a plurality of virtual machines running on a physical machine,
A communication information management step in which the management device manages a communication capacity between the plurality of virtual machines;
A physical component management step in which the management device manages physical components of the physical machine between the plurality of virtual machines;
The management apparatus determines a placement destination of a virtual machine to be relocated among the plurality of virtual machines according to the communication capacity and the physical component; and
A virtual machine management method characterized by comprising: In the physical component management step,
The management device manages communication condition information including communication conditions according to physical components of the physical machine;
In the communication information management step,
While the management device manages the placement priority indicating the degree of communication capacity that can be expected according to the placement between the plurality of virtual machines, the management device increases or decreases the communication capacity between the plurality of virtual machines measured at different times. Update the placement priority accordingly,
In the placement destination determining step,
The management apparatus accumulates a plurality of placement destination candidates of relocation target virtual machines among the plurality of virtual machines according to the communication condition information and the placement priority, and one placement from the plurality of placement search candidates The virtual machine management method according to claim 8, wherein a destination candidate is determined. In the communication information management step,
The management device manages an index value representing the current arrangement of the virtual machines to be relocated together with the communication capacity between the plurality of virtual machines,
In the placement destination determining step,
When the performance of the virtual component of the virtual machine to be relocated is within the range of the performance of the physical component of the physical machine, the management device performs relocation of the virtual machine to be relocated, The virtual machine management method according to claim 9, wherein an index value indicating a current arrangement of the virtual machine to be relocated managed in the communication information management step is updated. In the placement destination determining step,
When the management device rearranges the virtual machines to be rearranged, it updates each virtual component of the plurality of virtual machines in a virtual component management unit that manages each virtual component of the plurality of virtual machines. The virtual machine management method according to claim 10, wherein: The physical component is at least:
A central processing unit of the physical machine;
A memory used as a work area by the central processing unit;
An interface between the central processing unit and the outside;
9. The virtual machine management method according to claim 8, further comprising: The plurality of virtual machines are:
The virtual machine management method according to claim 12, wherein the virtual machine management method operates on a single physical machine having a plurality of nodes including the physical components. There are a plurality of the physical machines,
The virtual machine management method according to claim 12, wherein the plurality of virtual machines are operating on the plurality of physical machines each including the physical component.

Images