JP5515889B2 - Virtual machine system, automatic migration method and automatic migration program - Google Patents

Description

  The present invention relates to a virtual machine system that performs migration of a virtual machine, an automatic migration method, and an automatic migration program.

  In recent years, the range of use of virtual machines (VMs) has been expanded, and opportunities for use when configuring non-stop systems and mission-critical systems are increasing. On the other hand, as the functions of virtual machines increase and are used in various cases, virtual machines are becoming more complex. As virtual machines become more complex, the difficulty of maintenance increases. As the maintenance difficulty level increases, the maintenance cost for the virtual machine host hardware, operating system (OS), and the like increases.

  When performing host maintenance, all virtual machines on the host are affected. In order to perform host maintenance without stopping services provided by virtual machines on the host, it is necessary to temporarily migrate (move) all virtual machines on the host.

  The method of manually migrating a virtual machine by an engineer increases the labor and cost as the number of virtual machines increases. Therefore, there is a need for a technique that facilitates migration of virtual machines in order to reduce management costs.

  Patent Document 1 describes a virtual machine system that determines a migration destination host of a virtual machine. In the virtual machine system described in Patent Document 1, the management server determines a migration destination host in consideration of the type of virtualization software, the time required for virtual machine migration, and the like.

JP 2008-217302 A (paragraphs 0014, 0069-0075)

  However, in the virtual machine system described in Patent Document 1, it is possible to reliably determine the migration destination host according to the evaluation value calculated based on the predetermined information. If it is in operation, the resource status used by the operating virtual machine is not taken into account, so there is a possibility of contention for resources (for example, CPU power) by the virtual machine when performing migration .

  SUMMARY An advantage of some aspects of the invention is that it provides a virtual machine system, an automatic migration method, and an automatic migration program that secure resources and execute migration of virtual machines.

A virtual machine system according to the present invention is a virtual machine system in which one or more virtual machines are constructed in a computer, and the computer collects virtual machine configuration information including system information for each virtual machine and An information collection unit that collects host configuration information including free capacity information of each computer from the computer, and another computer to which the virtual machine is migrated based on the virtual machine configuration information and host configuration information collected by the information collection unit a determination unit for determining a, the other computers of the migration destination determined by the decision unit, viewed including an execution unit for migrating a virtual machine, determining unit, and the collected virtual machine configuration information and host configuration information Based on this, a simulation is performed when the amount of memory used and the number of CPU cores allocated to the virtual machine are modified The migration destination computer that can execute the migration is determined, and the execution unit uses the same amount of used memory and the same number of CPU cores as those used in the simulation when the other computer of the migration destination is determined by the determination unit. It is characterized by migrating a machine to another determined computer .

An automatic migration method according to the present invention is an automatic migration method in a virtual machine system in which one or more virtual machines are constructed on a computer, collecting virtual machine configuration information including system information for each virtual machine, and When collecting host configuration information including free capacity information of each computer from the computers and modifying the amount of used memory and the number of CPU cores allocated to the virtual machine based on the collected virtual machine configuration information and host configuration information The migration destination computer that can execute the migration is determined, and the virtual machine is determined using the same amount of used memory and the same number of CPU cores as the simulation when the other migration destination computer is determined. this migrating to the determined other computers The features.

The automatic migration program according to the present invention includes a process of collecting virtual machine configuration information including system information for each virtual machine in a virtual machine system in which one or more virtual machines are constructed on the computer, and a plurality of other computers. Simulation when correcting the amount of used memory and the number of CPU cores allocated to a virtual machine based on the process of collecting host configuration information including free capacity information of the computer, and the collected virtual machine configuration information and host configuration information Using the same amount of used memory and the same number of CPU cores as those used in the simulation to determine other migration destination computers that can perform migration, and when the other migration destination computers are determined. migrate to the determined another computer process and the actual Characterized in that to.

  According to the present invention, it is possible to reliably secure resources and automatically execute virtual machine migration.

It is a block diagram which shows the structural example of the host which is one Embodiment of the virtual machine system by this invention. FIG. 2 is a block diagram illustrating a configuration example of a host illustrated in FIG. 1 when a virtual machine is migrated. FIG. 3 is a UML activity diagram illustrating an operation of the host illustrated in FIG. 1 when a virtual machine is migrated. FIG. 10 is a UML activity diagram showing processing for determining a migration destination of a virtual machine. FIG. 12 is a UML activity diagram showing a simulation process for assigning a virtual machine to a host without modifying the parameters of the virtual machine. FIG. 11 is a UML activity diagram showing a simulation process for modifying a virtual machine parameter and allocating a virtual machine to a host. It is a block diagram which shows the principal part of the virtual machine system by this invention.

  FIG. 1 is a block diagram showing a configuration example of a host which is an embodiment of a virtual machine system according to the present invention. With reference to FIG. 1, a configuration of a host 10 which is an embodiment of a virtual machine system according to the present invention will be described.

  The hosts 10, 20, and 30 can allocate and allocate each resource to one or more virtual machines, and construct and operate one or more virtual machines on each host. Assume that the hosts 10, 20, and 30 are operating virtual machines, respectively. The hosts 10, 20, and 30 are connected by a network line 50 and can communicate with each other.

  The host 10 includes virtual machines 11a, 11b, and 11c. In the host 10, the virtual machine management software 12 is operating, and a control unit (not shown) of the host 10 controls the virtual machines 11a, 11b, and 11c in accordance with the program of the virtual machine management software 12 (hereinafter, simply (The host 10 manages the virtual machines 11a, 11b, and 11c.)

  The host 10 collects hardware information of the host 10, configuration information of the virtual machines 11a, 11b, and 11c, and the like by the operation of the virtual machine management software 12. For example, the host 10 has the number of CPU cores of the host 10, the number of CPUs of the host 10, the IP address of the host 10, the total memory capacity of the host 10, the CPU usage rate of the host 10, and the CPU usage of each of the virtual machines 11a, 11b, and 11c. It is assumed that the rate and the memory capacity of each of the virtual machines 11a, 11b, and 11c are collected. The virtual machine management software 12 has a function of constructing a virtual machine and a function of determining a migration destination of the virtual machine.

  The virtual machines 11a, 11b, and 11c store the disk images of the respective OSs in the shared storage 40.

  The host 20 includes one or more virtual machines (not shown). In the host 20, virtual machine management software 22 is operating. The host 20 manages virtual machines on the host 20. The host 20 collects hardware information of the host 20 and configuration information of each virtual machine on the host 20 by the operation of the virtual machine management software 22. The virtual machine on the host 20 stores the disk image of each OS in the shared storage 40.

  The host 30 includes one or more virtual machines (not shown). On the host 30, virtual machine management software 32 is operating. The host 30 manages virtual machines on the host 30. The host 30 collects hardware information of the host 30 and configuration information of each virtual machine on the host 30 by the operation of the virtual machine management software 32. The virtual machine on the host 30 stores the disk image of each OS in the shared storage 40.

  Each host can acquire the configuration information collected by other hosts through the operation of the virtual machine management software via the network line 50. Specifically, for example, the host 10 determines the total number of CPU cores, the number of CPUs, the IP address, the memory usage, the CPU usage rate, the CPU usage rate and the memory capacity of each virtual machine on the host 20, etc. Can be acquired. The host 10 can acquire the same information from the host 30.

  The shared storage 40 is a storage device connected to the hosts 10, 20, and 30 by storage network lines 51, 52, and 53, respectively. The shared storage 40 can be accessed from the hosts 10, 20, and 30.

  Further, it is assumed that the disk image of the OS of the virtual machine stored in the shared storage 40 can be accessed from a host other than the host including the virtual machine. That is, for example, the OS disk image of the virtual machine 11 a stored in the shared storage 40 can be accessed not only from the host 10 but also from the host 20 and the host 30.

  FIG. 2 is a block diagram illustrating a configuration example of the host illustrated in FIG. 1 when a virtual machine is migrated. With reference to FIG. 2, the configuration of the hosts 10, 20, and 30 when migration is performed on the virtual machines 11a, 11b, and 11c on the host 10 shown in FIG.

  For example, it is assumed that migration is performed on the virtual machines 11a, 11b, and 11c on the host 10 in order to perform maintenance of the host 10. First, migration destinations of the virtual machines 11a, 11b, and 11c are determined. A method for determining the migration destination of the virtual machine will be described later with reference to FIGS. Here, it is assumed that the virtual machine 11 a is assigned to the host 20, and the virtual machines 11 b and 11 c are assigned to the host 30.

  Next, in accordance with the determined migration destination, the virtual machines 11a, 11b, and 11c are moved to the respective assignment destination hosts. As a result, as shown in FIG. 2, the virtual machine 11a becomes the virtual machine 21a on the host 20, the virtual machine 11b becomes the virtual machine 31b on the host 30, and the virtual machine 11c becomes the virtual machine 31c on the host 30.

  FIG. 3 is a UML (Unified Modeling Language) activity diagram showing the operation of the host shown in FIG. 1 when virtual machine migration is performed. Referring to FIG. 3, the operations of the hosts 10, 20, and 30 shown in FIG. 1 when the virtual machines 11a, 11b, and 11c on the host 10 are migrated to perform maintenance of the host 10 are described. An outline will be described.

  First, a virtual machine to be migrated in the host 10 is designated (step S11). For example, the virtual machines 11a, 11b, and 11c are designated as virtual machines to be migrated.

  Next, the host 10 communicates with other hosts (for example, hosts 20 and 30) via the network line 50. The host 10 acquires the operation status such as the hardware information of the host in each of the hosts 20 and 30 and the configuration information of the virtual machine on the host from the host 20 and the host 30 (step S12).

  Based on the operation status in the other host acquired in step S12, the host 10 determines the respective migration destinations of the virtual machines 11a, 11b, and 11c (step S13). Detailed processing for determining the migration destination will be described later with reference to FIGS.

  The host 10 performs migration of each virtual machine to the migration destination determined in step S13 (step S14). Before performing the migration, the host 10 stores information indicating the setting of the virtual machine on the host 10 among the data collected by the virtual machine management software 12, for example, a storage unit (not shown) of the host 10. Or stored in the shared storage 40.

  The host 10 and the migration destination hosts 20 and 30 hold information indicating that migration has been performed from the host 10 to the hosts 20 and 30 in step S14 (step S15). Each host has an identifiable ID such as an IP address. Each host can hold information by, for example, associating the ID of each host with the implementation status of migration.

  Since the migration of the virtual machines 11a, 11b, and 11c from the host 10 has been completed, maintenance can be performed on the host 10 (step S16).

  When it is desired to return the virtual machine environment to the environment before the migration after the maintenance of the host 10 is completed in step S16, the host 10 stores information indicating the setting of the virtual machine on the host 10 stored in step S14. Refer to Then, according to the setting of the virtual machine of the host 10 before migration, the migration destination hosts 20 and 30 are notified to return the migrated virtual machine to the host 10 (step S17).

  The migration destination hosts 20 and 30 that received the notification in step S17 return the virtual machines 11a, 11b, and 11c to which migration has been performed to the host 10 (step S18). As a result, the virtual machines 11a, 11b, and 11c are operated on the host 10 again. Note that after the virtual machine is returned to the host 10, the host 10 may delete information indicating the setting of the virtual machine before migration.

  In such a virtual machine system, the migration of the virtual machine can be automatically executed only by the user specifying the virtual machine to be migrated. Therefore, the implementation of the migration is convenient because the processing can be automated as compared with the conventional method that was manually performed by an engineer.

  Further, in such a virtual machine system, if it is desired to temporarily migrate the virtual machine for host maintenance or the like, the operation of steps S16 to S18 is performed to migrate the configuration of the virtual machine system. It is possible to restore to the configuration before implementation.

  FIG. 4 is a UML activity diagram showing processing for determining a migration destination of a virtual machine. With reference to FIG. 4, the migration destination determination process shown in step S13 of FIG. 3 will be described in detail. For example, it is assumed that virtual machines 11a, 11b, and 11c on the host 10 shown in FIG. In addition, the number of CPU cores, the CPU usage rate, and the memory capacity related to the host and the virtual machine are used to calculate the parameters that serve as an index for virtual machine allocation.

  First, the host 10 calculates the total number of cores (total number of cores) allocated to all virtual machines (virtual machines 11a, 11b, and 11c) on the host 10 (step S21). Next, the host 10 calculates the total memory (total memory capacity) allocated to all virtual machines on the host 10 (step S22).

  The host 10 calculates the maximum amount of physical capacity required for all virtual machines on the host 10 based on the total number of cores and the total memory capacity of the host 10 calculated in steps S21 and S22, and calculates the calculated physical The capacity is compared with the total free capacity (total free capacity) of the memory of another host (step S23). Hereinafter, for the sake of omission, expressions such as “comparing the total number of cores and the total memory capacity of the host 10 with the total free capacity of other hosts” are used.

  If the total number of cores and the total memory capacity of the host 10 are smaller than the total free capacity of the other host in step S23, the host 10 modifies the parameters of the virtual machine on the host 10 to the other host. It is simulated whether or not it can be assigned as it is without doing (step S24). Details of the simulation in step S24 will be described later with reference to FIG.

  In the simulation of step S24, if a virtual machine can be assigned, the assigned host is set as the migration destination of the virtual machine of the host 10.

  If the total number of cores and the total memory capacity of the host 10 are greater than or equal to the total free capacity of other hosts in step S23, or if the virtual machine allocation destination is not found in step S24, the host 10 Then, the total average memory usage is calculated for all virtual machines on the host 10 (step S25).

  Then, the host 10 compares the total average memory usage calculated in step S25 with the total free capacity of other hosts (step S26).

  In step S <b> 26, when the total free capacity of the other hosts of the host 10 is equal to or greater than the total of the average memory usage of all the virtual machines on the host 10, the host 10 determines all the virtual machines on the host 10. Then, the total CPU usage rate is calculated (step S27). Here, the “CPU usage rate” is a value obtained by “average CPU usage rate × number of cores”, and may be a value exceeding 100. For example, the CPU usage rate of a virtual machine having an average CPU usage rate of 60% and four cores assigned is 240.

  Then, the host 10 compares the total CPU usage rate calculated in step S27 with a value obtained by multiplying the total number of free cores of other hosts by 100 (step S28).

  If the total free capacity of other hosts in the host 10 is less than the total average memory usage of all virtual machines on the host 10 in step S26, or the total number of free cores is multiplied by 100 in step S28. If this is less than the sum of the CPU usage rates of all virtual machines on the host 10, the processing is terminated as out of allocation.

  In step S28, if the total number of free cores multiplied by 100 is equal to or greater than the total CPU usage rate of all virtual machines on the host 10, the parameters of the virtual machine on the host 10 are corrected, and the virtual It is simulated whether the system configuration of the machine can be changed and assigned to the other host (step S29). Details of the simulation in step S29 will be described later with reference to FIG.

  In the simulation of step S29, when a virtual machine can be allocated, the allocated host is set as a migration destination of the virtual machine of the host 10. In the simulation of step S24, when the virtual machine cannot be allocated, the process is terminated as being excluded from allocation.

  In the process of FIG. 4, if it is determined that “not eligible for allocation”, it is determined that the migration will affect the performance of other hosts operating another virtual machine. means. The virtual machine system according to the present invention is intended to perform migration without affecting the performance of the migration destination host as much as possible. In such a case, the virtual machine system is determined not to be assigned.

  FIG. 5 is a UML activity diagram showing a simulation process for allocating a virtual machine to a host without modifying the parameters of the virtual machine. With reference to FIG. 5, the simulation process in step S24 of FIG. 4 will be described in detail.

  First, the host 10 sorts virtual machines to be migrated, that is, all virtual machines on the host 10 in descending order using the first key as the number of cores and the second key as the memory capacity (step S31). As a result, all virtual machines on the host 10 are arranged in descending order of the maximum physical capacity required for each virtual machine. The host 10 stores the virtual machine sort result sorted in step S31 in the storage unit of the host 10 in the form of a table or the like.

  Next, the host 10 uses the first key as the number of free cores and the second key as the free memory capacity, and hosts that are migration destination candidates, that is, all hosts other than the host 10 connected by the network line 50. Sort in descending order (step S32). As a result, all hosts other than the host 10 are arranged in descending order of physical capacity that can be allocated to the virtual memory. The host 10 stores the host sort result sorted in step S32 in the storage unit of the host 10 in the form of a table or the like.

  The host 10 defines the virtual machine number m and the host number n in the sorting results in step S31 and step S32 (step S33). For example, if there are M virtual machines on the host 10, an integer from 0 to M-1 is assigned to the virtual machine number m in order. Assuming that there are N hosts other than the host 10, the host number n is assigned an integer from 0 to N-1, in order. The virtual machine number m and host number n are set to 0 as initial values. A virtual machine assigned the virtual machine number m is called a virtual machine m, and a host assigned the host number n is called a host n.

  The host 10 performs the processing shown in steps S35 to S39 described later on all the virtual machines (step S34). That is, the processes shown in steps S35 to S39 are repeated while the virtual machine number m is between 0 and M-1. However, depending on the case, the processes shown in steps S40 to S43 are also repeatedly executed.

  Processing in steps S35 to S43 will be described. First, the host 10 performs the processing shown in steps S36 to S37 described later on all the hosts other than the host 10 until a host that can migrate the virtual machine m is found while the virtual machine number m is fixed ( Step S35). That is, for the virtual machine number m, the processing shown in steps S36 to S37 is repeated while the host number n is between 0 and N-1.

  If the processing for all the hosts other than the host 10 is not completed for the virtual machine m in step S35, the host 10 determines whether the virtual machine m can be migrated to the host n (step S36). Whether or not the virtual machine m can be migrated to the host n is determined by whether or not the number of cores and the memory capacity allocated to the virtual machine m are within the free capacity of the host n.

  If it is determined in step S36 that the virtual machine m cannot be migrated to the host n, the host 10 sets the host number to n + 1 (step S37), returns to step S35, and performs processing for the next host.

  If it is determined in step S36 that the virtual machine m can be migrated to the host n, the host 10 records assignment of the virtual machine m to the host n as assignment data (step S38). The recorded allocation data is stored in the storage unit. Further, the host 10 reflects the recorded assignment on the host sort result stored in the storage unit. Specifically, for example, the physical capacity required by the virtual machine m is subtracted from the data of the host n as a result of the host sort, and the result is stored again in the storage unit.

  Then, the host 10 sets the virtual machine number to m + 1 and the host number to 0 (step S39), returns to step S34, and performs processing for the next virtual machine.

  If the processing shown in S36 to S39 is repeated and processing for all the hosts other than the host 10 is completed for the virtual machine m in step S35, it means that the migration destination host of the virtual machine m was not found. To do. At that time, the host 10 checks whether or not the virtual machine number m is 0, and determines whether or not it is the first virtual machine as a result of the virtual machine sort in step S31 (step S40).

  If it is determined in step S40 that the virtual machine number m is 0 and it is the first virtual machine, the host 10 determines that no allocation example has been found and ends the simulation.

  If it is determined in step S40 that the virtual machine number is other than 0 and it is not the first virtual machine, the host 10 sets the virtual machine number to m-1 and returns to the previous virtual machine (step S40). S41). At this time, a host that can be migrated has been found in the previous virtual machine, and the host to be assigned (for example, host number n1) is recorded in the process shown in step S38.

  When the virtual machine number is set to m−1 in step S41, the host 10 sets the host number to (n1 + 1) and becomes the host next to the host n1 recorded as the allocation destination of the virtual machine (m−1) (step S41). S42).

  The host 10 deletes the records of the virtual machine (m−1) and the host n1 for the allocation data stored in the storage unit. Further, the host 10 reflects the deleted assignment on the host sort result stored in the storage unit (step S43). Specifically, for example, the physical capacity subtracted when recording the allocation of the virtual machine (m−1) to the data of the host n1 as the host sort result is returned and stored again in the storage unit.

  Then, the process returns to step S34, and the process for the host with the host number (n1 + 1) is performed for the virtual machine with the virtual machine number (m-1).

  In step S34, when the virtual machine number becomes M, it indicates that a host that can be migrated has been found for all virtual machines on the host 10, so the simulation is terminated assuming that an allocation example has been found. At this time, migration can be executed for each host in which assignments are recorded without modifying parameters for all virtual machines on the host 10.

  FIG. 6 is a UML activity diagram showing a simulation process for modifying a virtual machine parameter and allocating a virtual machine to a host. With reference to FIG. 6, the simulation process in step S29 of FIG. 4 will be described in detail.

  First, the host 10 calculates a virtual machine allocation index P (step S51). For example, the allocation index P is calculated by a calculation formula represented by P = (total CPU usage rate of all virtual machines on the host 10 / number of free CPU cores of all hosts other than the host 10 × 100). The host 10 stores the calculated allocation index P in the storage unit.

  Next, the host 10 sorts all virtual machines on the host 10 (step S52), stores virtual machine sort results, and sorts all hosts other than the host 10, similar to the processing shown in steps S31 to S33 of FIG. (Step S53), storage of the host sort result, and definition and assignment of the virtual machine number m and host number n (Step S54). A virtual machine assigned the virtual machine number m is called a virtual machine m, and a host assigned the host number n is called a host n.

  The host 10 performs the processing shown in steps S56 to S62 described later on all virtual machines (step S55). That is, the process shown in steps S56 to S62 is repeated while the virtual machine number m is between 0 and M-1. However, depending on the case, the processes shown in steps S63 to S66 are also repeatedly executed.

  Processing in steps S56 to S66 will be described. First, the host 10 performs the processing shown in steps S57 to S59 described later on all the hosts other than the host 10 until a host capable of migrating the virtual machine m is found while the virtual machine number m is fixed ( Step S56). That is, for the virtual machine number m, the processing shown in steps S57 to S59 is repeated while the host number n is between 0 and N-1.

  In step S56, when the processing for all the hosts other than the host 10 is not completed for the virtual machine m, the host 10 compares the resource status of the host n with the allocation index P (step S57). Specifically, it is compared whether or not the value (host n resource index) calculated by (total CPU usage rate of host n / number of free CPU cores of host n × 100) is larger than the allocation index P. To do.

  In step S57, if the resource index of the host n is larger than the allocation index P, the host 10 determines that the virtual machine m cannot be migrated to the host n, sets the host number to n + 1 (step S58), and step Returning to S56, processing for the next host is performed.

  If the resource index of the host n is equal to or less than the allocation index P in step S57, the host 10 determines the used memory amount Xm allocated to the virtual machine m after migration (step S59). Specifically, the used memory amount Xm is calculated by a calculation formula represented by Xm = ((average memory used amount of virtual machine m / Q) +1) × M. Q is a constant indicating the minimum unit of the allocated memory.

  When the used memory amount of the virtual machine m determined in step S59 exceeds the free memory capacity of the host n, the capacity is over, so the host 10 determines that the virtual machine m cannot be migrated to the host n, and In step S58, processing for the next host is performed.

  If the used memory amount of the virtual machine m determined in step S59 is within the free memory capacity of the host n, the host 10 determines that the virtual machine m can be migrated to the host n. The host 10 determines the number of used cores Ym to be allocated to the migrated virtual machine m (step S60). Specifically, the number of used cores Ym is calculated by a calculation formula represented by Ym = (CPU usage rate of virtual machine m / 100) +1 (the calculation result of “/” represents a quotient of division). The remainder of the division is rounded down.)

  The host 10 records the assignment of the virtual machine m to the host n as assignment data (step S61). The recorded allocation data is stored in the storage unit. Further, the host 10 reflects the recorded assignment on the host sort result stored in the storage unit. Specifically, for example, the physical capacity that needs to be reserved for the virtual machine m is subtracted from the data of the host n as a result of the host sort based on the used memory Xm and the used core number Ym, and is stored in the storage unit. Store again.

  Then, the host 10 sets the virtual machine number to m + 1 and the host number to 0 (step S62), returns to step S55, and performs processing for the next virtual machine.

  If the processing shown in S57 to S62 is repeated and the processing for all the hosts other than the host 10 is completed for the virtual machine m in step S56, it means that the migration destination host of the virtual machine m was not found. To do. At that time, the host 10 checks whether or not the virtual machine number is 0, and determines whether or not it is the first virtual machine as a result of the virtual machine sort in step S52 (step S63).

  If it is determined in step S63 that the virtual machine number is 0 and it is the first virtual machine, the host 10 determines that no allocation example has been found and ends the simulation.

  If it is determined in step S63 that the virtual machine number is other than 0 and it is not the first virtual machine, the host 10 sets the virtual machine number to m-1 and returns to the previous virtual machine (step S63). S64). At this time, a host that can be migrated is found in the previous virtual machine, and the host to be allocated (for example, host number n2) is recorded in the process shown in step S61.

  When the virtual machine number is set to m-1 in step S64, the host 10 sets the host number to (n2 + 1) and becomes the host next to the host n2 recorded as the allocation destination of the virtual machine (m-1) (step S64). S65).

  The host 10 deletes the record of the virtual machine (m−1) and the host n2 for the allocation data stored in the storage unit. Further, the host 10 reflects the deleted assignment on the host sort result stored in the storage unit (step S66). Specifically, for example, the physical capacity subtracted when recording the allocation of the virtual machine (m−1) to the data of the host n2 as the host sort result is returned and stored again in the storage unit.

  Then, the process returns to step S55, and the process for the host with the host number (n2 + 1) is performed for the virtual machine with the virtual machine number (m-1).

  If the virtual machine number is M in step S55, it indicates that a migratable host has been found for all virtual machines on the host 10, and the simulation is terminated assuming that an allocation example has been found. At this time, the migration can be executed to each host in which the assignment is recorded after correcting the parameters for all the virtual machines on the host 10.

  In FIGS. 5 and 6, in the simulation of the host to which the virtual machine is allocated, the number of CPU cores, the CPU usage rate, and the memory capacity related to the host and the virtual machine are used, but the CPU type and frequency are taken into consideration. Thus, the host to which the virtual machine is allocated may be simulated.

  As described above, when migrating without changing the parameters of the virtual machine, the host 10 that is a virtual machine system is not a resource allocated to another virtual machine that is already operating on the migration destination host. Therefore, when migration is performed, it is possible to suppress adverse effects such as competing resources with other virtual machines in operation.

  If the host 10 cannot perform migration without changing the virtual machine parameters because the migration destination candidate host has insufficient free space, change the virtual machine parameters. You can change the system configuration and search for the migration destination. Even when migrating by changing virtual machine parameters, resources that are not being used can be changed without changing resources assigned to other virtual machines that are already operating on the migration destination host. Since it is assigned to a virtual machine, adverse effects such as competing resources with other operating virtual machines can be suppressed when migration is performed.

  According to such a virtual machine system, maintenance of the virtual machine system can be performed online without interrupting the operation of the virtual machine without preparing standby hardware. .

  Furthermore, since such virtual machine systems can automatically migrate virtual machines, it is possible to reduce the time and effort of engineers, and to prevent the occurrence of failures due to human error during migration. You can also.

  In FIG. 6, the virtual machine allocation index P is used in the simulation of the host to which the virtual machine is allocated. For example, an allocation index P ′ calculated by multiplying the allocation index P by a coefficient of 0 or more is used. May be. By using such an allocation index P ′, the virtual machine system may execute a simulation in which the load applied to the virtual machine system is arbitrarily adjusted (for example, a simulation in a case where migration is desired even when a little load is applied). it can.

  FIG. 7 is a block diagram showing a main part of the virtual machine system according to the present invention. As shown in FIG. 7, the virtual machine system corresponds to the computer 1 (for example, equivalent to the host 10 shown in FIG. 1) and one or more virtual machines 2 and 3 (for example, equivalent to the virtual machines 11a and 11b shown in FIG. 1). ) Is constructed, and the computer includes virtual machine configuration information including system information for each virtual machine (for example, hardware information of the host 10 collected by the operation of the virtual machine management software 12 in the embodiment). Or the virtual machines 11a, 11b, and 11c), and a host including free capacity information of each computer from a plurality of other computers 4 and 5 (for example, corresponding to the hosts 20 and 30 shown in FIG. 1). An information collection unit 6 (for example, FIG. 1) that collects configuration information (for example, corresponding to each piece of configuration information that the host 10 can acquire from the host 20 in the embodiment) The other computer 4 to which the virtual machines 2 and 3 are migrated, based on the virtual machine configuration information and the host configuration information collected by the information collection unit 6. , 5 (for example, corresponding to a control unit that operates according to the program of the management software 12 shown in FIG. 1), and other computers 4 and 5 of the migration destination determined by the determination unit 7 include virtual machines. 2 and 3 (for example, a control unit that operates according to the program of the management software 12 shown in FIG. 1).

  Further, in the above-described host described as one embodiment of the virtual machine system, virtual machine systems as shown in the following (1) to (5) are also disclosed.

(1) A storage unit (e.g., equivalent to the storage unit (not shown) of the embodiment) that stores virtual machine configuration information before migration is provided, and the execution unit includes other migration destinations determined by the determination unit. After migrating the virtual machine to the other computer and completing the predetermined processing (for example, host maintenance), refer to the virtual machine configuration information stored in the storage unit and migrate the other computers to the migration destination. A virtual machine system that notifies the virtual machine to return to the previous arrangement state (for example, realized by the operation shown in step S17 of FIG. 3).

(2) The determination unit performs a simulation when a predetermined parameter constituting the virtual machine system is modified based on the virtual machine configuration information and the host configuration information (for example, realized by the simulation operation illustrated in FIG. 6). The migration destination computer that can execute the migration is determined, and the execution unit uses the same correction parameters as the simulation when the migration destination other computer is determined by the determination unit, and the virtual machine A virtual machine system that migrates to other computers.

(3) The determining unit uses an allocation index (for example, equivalent to the allocation index P in the embodiment) calculated based on the total CPU usage rate of the computer and the number of free CPU cores as one of the determination criteria. A virtual machine system that performs simulation when a predetermined parameter constituting the machine system is corrected (for example, realized by the simulation operation shown in FIG. 6).

(4) The information collection unit is a virtual machine system that collects virtual machine configuration information including the number of CPU cores, CPU usage rate, and memory usage.

(5) The information collection unit is a virtual machine system that collects host configuration information including the number of free CPU cores and free memory capacity of a computer.

DESCRIPTION OF SYMBOLS 1 Computer 2, 3 Virtual machine 4, 5 (Other) computer 6 Information collection part 7 Determination part 8 Execution part 10, 20, 30 Host 11a, 11b, 11c, 21a, 31b, 31c Virtual machine 12, 22, 32 Virtual Machine management software 40 Shared storage 50 Network line 51, 52, 53 Storage network line

Claims (6)

A virtual machine system in which one or more virtual machines are built on a computer,
The calculator is
An information collection unit that collects virtual machine configuration information including system information for each virtual machine, and collects host configuration information including free capacity information of each computer from a plurality of other computers;
A determination unit that determines another computer to which the virtual machine is migrated based on the virtual machine configuration information and the host configuration information collected by the information collection unit;
Other computer migration destination determined by said determining unit, viewed including an execution unit for migrating the virtual machines,
Based on the collected virtual machine configuration information and the host configuration information, the determination unit performs a simulation when the amount of used memory and the number of used CPU cores allocated to the virtual machine are corrected, and can execute migration Determine other computers to migrate to
The execution unit migrates the virtual machine to the determined other computer using the same used memory amount and the same number of used CPU cores as in the simulation when the determining unit determines another migration destination computer. A virtual machine system characterized by this. The determination unit allocates a virtual machine using an allocation index calculated based on the total CPU usage rate of the computer in which the virtual machine is constructed and the number of free CPU cores of a plurality of other computers as one of the determination criteria. virtual machine system according to claim 1, wherein performing the simulation in the case of modifying the number of used memory capacity and used CPU cores. Information collection unit, CPU cores, according to claim 1 or claim 2 virtual machine system according to collect virtual machine configuration information including CPU usage and memory usage. The virtual machine system according to any one of claims 1 to 3 , wherein the information collection unit collects host configuration information including a number of free CPU cores and a free memory capacity of a plurality of other computers. An automatic migration method in a virtual machine system in which one or more virtual machines are built on a computer,
Collect virtual machine configuration information including system information for each virtual machine,
Collect host configuration information including free space information for each computer from multiple other computers.
Based on the collected virtual machine configuration information and the host configuration information, a simulation is performed when the amount of used memory and the number of used CPU cores allocated to the virtual machine are corrected, and other migration destinations that can execute migration Determine the calculator,
An automatic migration method characterized in that the virtual machine is migrated to the determined other computer using the same used memory amount and the same number of used CPU cores as the simulation when the other computer of the migration destination is determined. . In a virtual machine system in which one or more virtual machines are built on a computer,
A process of collecting virtual machine configuration information including system information for each virtual machine;
A process of collecting host configuration information including free capacity information of each computer from a plurality of other computers;
Based on the collected virtual machine configuration information and the host configuration information, a simulation is performed when the amount of used memory and the number of used CPU cores allocated to the virtual machine are corrected, and other migration destinations that can execute migration Processing to determine the computer;
Automatic processing for executing the process of migrating the virtual machine to the determined other computer using the same used memory amount and the same number of used CPU cores as the simulation when the other computer of the migration destination is determined Migration program.

Images