JP2015146148A - Virtual machine management device, virtual machine management method, and virtual machine management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent processing that is normally performed by a virtual machine from being affected when the virtual machine collects log information according to an instruction from another specific virtual machine.SOLUTION: A virtual machine management device 3 includes: an instruction unit 31 that operates using resources for executing information processing which are included in an information processing device, selects a second virtual machine 42 out of a plurality of virtual machines on the basis of a predetermined reference according to a log collection instruction from a first virtual machine 41 out of a plurality of virtual machines for collecting log information in response to the log collection instruction to collect a log, and inputs the log collection instruction to the second virtual machine 42; and an allocation unit 32 that additionally allocates part of the resources to the second virtual machines when the instruction unit 31 inputs the log collection instruction to the second virtual machine 42.

Description

  The present invention relates to a virtual machine management apparatus that collects log information about a virtual machine in an environment where a plurality of virtual machines are constructed.

  In recent years, as cloud services in various industries have become widespread, computer systems using virtual environments have increased. In addition, as the hardware performance of a computer system improves, a method in which a plurality of virtual machines in the virtual environment share resources such as a CPU (Central Processing Unit) or a memory of a physical server is becoming common. . In such a computer system, there is a problem that the virtual machine sharing the resources possessed by the physical server has a problem that the system performance deteriorates due to resource contention regarding the memory bus bandwidth or network I / O (Input / Output) bandwidth. There are things to do.

  When such a performance problem occurs, the user who uses the virtual machine logs necessary to analyze the problem using the log collection function of the guest OS (Operating System) operating in the virtual machine Collect information. However, for example, the guest OS cannot collect log information indicating a competition state at a hardware level for constructing a virtual environment. For this reason, there is a problem that the performance problem cannot be sufficiently analyzed only from the log information collected by the log collection function of the guest OS.

  In order to deal with such problems, a user using the virtual machine can collect log information that can be collected by a guest OS that operates in another virtual machine or a hypervisor that is software for constructing and managing a virtual environment. Obtain from outside. The user can analyze the performance problem by matching the acquired log information with the log information collected by the guest OS used by the user in time series.

  As a technique related to performing such problem analysis, Patent Document 1 discloses a problem that the hypervisor records performance information collected by each guest OS and a screen (drawing information) displayed by the virtual console. Discloses a technique for determining whether the problem is a problem specific to a virtual machine or a problem related to a guest OS.

  Patent Document 2 discloses a technique for monitoring changes related to performance information when resources allocated to a virtual machine change dynamically by associating performance information that can be collected by the guest OS with resource allocation information. Has been.

  Patent Document 3 discloses a technique in which statistical processing in a virtual machine is executed with a minimum overhead, and a user freely processes and outputs acquired statistical information. In such a technique, information related to the virtualization event is recorded in the trace buffer, and another process monitors the trace buffer. Such a technique provides an interface for allowing a user to freely process and output statistical information collected by the hypervisor in an environment where the guest OS operates.

  Furthermore, in Patent Document 4, information is collected in a virtual machine to be managed so that the collected information can be accessed without imposing a load on the management manager operating in the server that performs management. Have been disclosed.

JP 2009-176228 A JP 2012-108956 A JP 2010-204972 A JP 2011-159249 A

  When a user using a specific virtual machine obtains log information collected by another virtual machine in order to analyze performance problems, the other virtual machine uses a part of the allocated resources. To collect log information. Therefore, in such other virtual machines, the resources for executing the processing that should be originally performed are temporarily reduced, so that there is a problem that the processing that the other virtual machines should perform is affected. The techniques disclosed in Patent Documents 1 to 4 cannot solve this problem.

  The main object of the present invention is to provide a virtual machine management apparatus, a virtual machine management method, and a virtual machine management program that solve this problem.

  The virtual machine management device according to the present invention operates using resources for executing information processing that the information processing device has, and includes a plurality of virtual machines that collect log information in response to a log collection command instructing log collection. In accordance with the log collection command from the first virtual machine, a second virtual machine is selected from the plurality of virtual machines based on a predetermined criterion, and the log is collected for the second virtual machine An instruction unit for inputting an instruction, and an allocation in which the resource is added and allocated to the second virtual machine when the instruction unit inputs the log collection instruction to the second virtual machine. And means.

  In another aspect of achieving the above object, the virtual machine management method of the present invention provides a resource for executing information processing by the first information processing apparatus, which the first information processing apparatus or the second information processing apparatus has. In accordance with the log collection command from the first virtual machine of the plurality of virtual machines that collect log information in response to the log collection command for instructing log collection based on a predetermined criterion When a second virtual machine is selected from a plurality of virtual machines, the log collection command is input to the second virtual machine, and the log collection command is input to the second virtual machine In addition, the resource is added and allocated to the second virtual machine.

  Further, in a further aspect of achieving the above object, the virtual machine management program according to the present invention operates using a resource that the information processing apparatus has to execute information processing, and issues a log collection command that instructs log collection. In accordance with the log collection command from the first virtual machine among the plurality of virtual machines receiving and collecting log information, a second virtual machine is selected from the plurality of virtual machines based on a predetermined criterion, An instruction process for inputting the log collection instruction to the second virtual machine, and the second virtual machine when the instruction process inputs the log collection instruction to the second virtual machine. On the other hand, it is characterized by causing a computer to execute allocation processing for adding and allocating the resource.

  Furthermore, the present invention can be realized by a computer-readable non-volatile storage medium in which the virtual machine management program (computer program) is stored.

  The present invention makes it possible to prevent the process originally performed by another virtual machine from affecting the process when the other virtual machine collects log information in accordance with an instruction from a specific virtual machine.

It is a block diagram which shows the structure of the virtual machine management apparatus which concerns on 1st Embodiment of this invention. It is a block diagram which shows the hardware constitutions of the virtual machine management apparatus which concerns on 1st Embodiment of this invention. It is a flowchart (1/2) which shows operation | movement of the virtual machine management apparatus which concerns on 1st Embodiment of this invention. It is a flowchart (2/2) which shows operation | movement of the virtual machine management apparatus which concerns on 1st Embodiment of this invention. It is a figure which shows the structural example of the resource allocation information which concerns on 1st Embodiment of this invention. It is a figure which shows the structural example of the competition resource management information which concerns on 1st Embodiment of this invention. It is a figure which shows the structural example of the collection log management information which concerns on 1st Embodiment of this invention. It is a block diagram which shows the structure of the virtual machine management apparatus which concerns on 2nd Embodiment of this invention.

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

<First Embodiment>
FIG. 1 is a block diagram conceptually showing the structure of the virtual machine management apparatus 1 according to the first embodiment. The virtual machine management apparatus 1 according to the present embodiment is an information processing apparatus such as a server apparatus, and builds a virtual environment. The virtual machine management device 1 according to the present embodiment executes a hypervisor 10 and guest OSs 20-1 to 20-n. The hypervisor 10 is software that constructs a virtual environment and manages the constructed virtual machine. The guest OSs 20-1 to 20-n are OSes that operate in each constructed virtual machine.

  FIG. 2 illustrates a hardware configuration of the virtual machine management apparatus 1 according to the present embodiment. The execution environment described below can be adopted not only in this embodiment but also in each embodiment described later.

  As shown in FIG. 2, the virtual machine management apparatus 1 includes a CPU (Central_Processing_Unit) 901, a ROM (Read_Only_Memory) 902, a RAM (Random_Access_Memory) 903, a hard disk 904 (storage device), and a communication interface 905 (Interface: hereinafter referred to as “Interface”). A reader / writer 908 capable of reading and writing data stored in a storage medium 907 such as a CD-ROM (Compact_Disc_Read_Only_Memory), and an input / output interface 909, and the configuration thereof is a bus 906 (communication A general computer connected via a line). The input / output interface 909 includes, for example, an input device such as a keyboard and an output device such as a monitor. FIG. 2 shows an example in which the virtual machine management device 1 includes one of these components, but the virtual machine management device 1 may include a plurality of these components.

  Then, the virtual machine management device 1 is provided with the hypervisor 10 and the guest OSs 20-1 to 20-n as computer programs, and then reads the computer programs into the CPU 901 of the hardware, interprets them, and executes them. The computer program may be stored in a volatile storage memory (RAM 903) that can be read and written or a nonvolatile storage device such as the hard disk 904.

  In the above-described case, the computer program can be supplied to the hardware by a method of installing in the apparatus via various storage media 907 such as a CD-ROM, or an external method via a communication line such as the Internet. A general procedure can be adopted at present, such as a method of downloading more. In such a case, it can be understood that the present invention is configured by a code constituting the computer program or a storage medium 907 in which the code is stored.

  The guest OSs 20-1 to 20-n execute collection log setting processing 21-1 to n, log collection processing 22-1 to n, and log reading processing 23-1 to n, respectively.

  The collection log setting process 21-i (i is an integer from 1 to n) presents list information regarding the types of logs that can be collected to the user using the guest OS 20-i through a monitor screen or the like. . Such list information includes, for example, a list of command names for collecting predetermined logs. The collection log setting process 21-i inputs a log collection instruction, which is information for instructing collection of a log of the type selected by the user, from the list information regarding the type of the log to the hypervisor 10. The log collection command includes an identifier that can identify the type of log to be collected, and an identifier that identifies the guest OS 20-i that issued the log collection command.

  The log collection process 22-i collects a log that can be collected by the guest OS 20-i based on the user using the guest OS 20-i or the content instructed by the hypervisor 10. Logs that can be collected in the guest OS 20-i include logs collected by various performance tools such as “ps”, “top”, and “sar” commands that can be used in a UNIX (registered trademark) OS, and “procs”, There is a log related to a pseudo file system such as “sysfs”.

  The log collection process 22-i stores the collected log in the shared buffer generated by the hypervisor 10. The shared buffer is a buffer accessible from the guest OSs 20-1 to 20-n and the hypervisor 10, and uses, for example, a partial area of the RAM 903 in the virtual machine management apparatus 1 shown in FIG.

  The log reading process 23-i reads the collected log from the shared buffer, and outputs the content of the log to an output device such as a monitor that outputs information related to the guest OS 20-i.

  The hypervisor 10 executes an instruction process 11, an allocation process 12, a calculation process 13, a collection log management information generation process 14, and a log collection process 18. The instruction process 11, the allocation process 12, the calculation process 13, the collection log management information generation process 14, and the log collection process 18 can be realized by a dedicated HW (hardware) (electronic circuit). . That is, the hypervisor 10 may be an HW having a function equivalent to these processes, and including an instruction unit, an allocation unit, a calculation unit, a collection log management information generation unit, and a log collection unit. .

  The hypervisor 10 stores the competing resource management information 150 in the competing resource management information storage unit 15 included in the virtual machine management device 1. The hypervisor 10 stores the resource allocation information 160 in the resource allocation information storage unit 16 included in the virtual machine management device 1. The hypervisor 10 stores the collection log management information 170 in the collection log management information storage unit 17 included in the virtual machine management apparatus 1. The virtual machine management device 1 includes the competing resource management information storage unit 15, the resource allocation information storage unit 16, and the collection log management information storage unit 17 in the RAM 903 or the hard disk 904 shown in FIG.

  The allocation process 12 allocates the resources included in the virtual machine management apparatus 1 to each virtual machine that executes the guest OSs 20-1 to 20-n. Specifically, the resource is a component included in the virtual machine management apparatus 1 illustrated in FIG. The assignment process 12 stores the result of assigning resources to each virtual machine in the resource assignment information storage unit 16 as resource assignment information 160. The allocation process 12 updates the resource allocation information 160 as necessary when a change related to the system configuration or the like occurs in the virtual machine management apparatus 1.

  An example of the configuration of the resource allocation information 160 according to this embodiment is illustrated in FIG. As shown in FIG. 4, the resource allocation information 160 includes a record in which a guest ID 161, a resource type 162, a virtual resource 163, a physical resource 164, and a resource allocation amount 165 are associated.

  The guest ID 161 is an identifier that can identify the guest OSs 20-1 to 20-n. In the example illustrated in FIG. 4, Guest 1 to 3 indicated by the guest ID 161 are identifiers that can identify the guest OSs 20-1 to 20-3, respectively.

  The resource type 162 is information indicating what kind of resource the record is, for example, “Cpu” when it is information about the CPU, “Mem” when it is information about the memory, and information about the disk. If it is information, it is “Disk”. Note that FIG. 4 shows only records related to the CPU, memory, and disk for convenience, but the resource allocation information 160 actually includes records related to resources such as input / output interfaces and network interfaces. Yes.

  The virtual resource 163 is an identifier that can identify the virtual resources allocated to the guest OSs 20-1 to 20-n. In the case of the example shown in FIG. 4, each virtual machine is executing one guest OS, and different virtual resources are assigned to the guest OS for the CPU, memory, and disk.

  The physical resource 164 is an identifier that can identify the physical resource allocated to the guest OSs 20-1 to 20-n. In the case of the example shown in FIG. 4, regarding the CPU, the guest OS 20-1 and the guest OS 20-3 are assigned the same physical resource Cpu0. As for the memory, Mem0, which is the same physical resource, is allocated to the guest OS 20-1 and the guest OS 20-2.

  The resource allocation amount 165 indicates an allocation amount related to physical resources allocated to the guest OSs 20-1 to 20-n. The resource allocation amount 165 indicates the allocation amount based on the CPU usage rate for the CPU and the storage capacity for the memory and the disk. In the case of the example shown in FIG. 4, a 50% CPU usage rate for Cpu0, a 2 GB (gigabyte) storage area for Mem0, and a 20 GB storage area for Sda are allocated to the guest OS 20-1. Note that the resource allocation information 160 may indicate the resource allocation amount 165 using a standard different from the CPU usage rate and the storage capacity.

  The allocation process 12 generates contention resource management information 150 based on the resource allocation information 160 and stores the contention resource management information 150 in the contention resource management information storage unit 15.

  An example of the configuration of the contention resource management information 150 according to this embodiment is illustrated in FIG. As shown in FIG. 5, the conflicting resource management information 150 includes a record in which a conflicting resource type 151 and a resource conflicting guest ID 152 are associated with each other.

  Similar to the resource type 162 in the resource allocation information 160, the contention resource type 151 is information indicating what resource the record is related to.

  The resource conflict guest ID 152 is information indicating whether any of the guest OSs 20-1 to 20-n is competing for the resource indicated by the conflict resource type 151. As the resource allocation information 160 in FIG. 4 indicates, the guest OS 20-1 and the guest OS 20-3 are allocated the same physical resource Cpu0. Therefore, since the guest OS 20-1 and the guest OS 20-3 compete for the CPU, the resource competition relation guest ID 152 in the record whose value indicated by the contention resource type 151 is “Cpu” is “Guest1, Guest3”. Show. Similarly, the conflicting resource management information 150 indicates that the guest OS 20-1 and the guest OS 20-2 compete for the memory, and the guest OSs 20-1 to 20-3 compete for the disk.

  The allocation process 12 obtains the log collection command input to the hypervisor 10 by the guest OS 20-i via the instruction process 11. The allocation process 12 can identify the guest OS 20-j (j is an integer of at least one of 1 to n) determined as a request destination to request log collection based on the information indicated by the log collection command related to the instruction process 11 A unique identifier is obtained from the instruction process 11. The allocation process 12 obtains a value indicating the amount of resources required when the guest OS 20-j executes the log collection command from the calculation process 13. The allocation process 11 cuts out the resources corresponding to the value indicated by the amount of resources obtained from the calculation unit 13 from the resources allocated to the guest OS 20-i that issued the log collection command. Then, the assignment process 12 assigns a resource cut out from the resource assigned to the guest OS 20-i to the guest OS 20-j.

  The calculation process 13 obtains the log collection command input to the hypervisor 10 by the guest OS 20-i via the instruction process 11. The calculation process 13 collates the type of log to be collected included in the log collection command with the collection log management information 170 stored in the collection log management information storage unit 17.

  A configuration example of the collection log management information 170 according to this embodiment is illustrated in FIG. As illustrated in FIG. 6, the collection log management information 170 includes a record that associates the collection log 171, the log collection cost 172, the resource type 173, and the log collection target 174.

  The collection log 171 is an identifier that can identify the contents of the collected log. The collection log management information 170 according to the present embodiment indicates, as the collection log 171, “sar”, “iostat”, “netstat”, and the like, which are names of commands for collecting logs in the UNIX OS.

  The log collection cost 172 is information indicating the amount of resources used when the guest OS 20-1 to n or the hypervisor 10 collects the log indicated by the collection log 171 in the record. In the case of the example illustrated in FIG. 6, for example, the “sar” command indicates that a resource corresponding to a CPU usage rate of 1% and a memory usage amount of 5 MB (megabytes) is used.

  The resource type 173 is information indicating what kind of resource the log indicated by the collection log 171 is. For example, since the “sar” command is a command for collecting performance information related to the entire system, the resource type 173 in the record whose collection log 171 is “sar” is indicated as “System”. Further, since the “iostat” command is a command for collecting performance information about the disk, the resource type 173 in the record whose collection log 171 is “iostat” is indicated as “Disk”.

  The log collection target 174 is information indicating whether the log indicated by the collection log 171 is collected by the guest OSs 20-1 to 20-n or by the hypervisor 10.

  For example, when the log collection instruction instructs to collect a log by the “sar” command, the calculation processing 13 indicates the information indicated by the log collection cost 172 in the record in which the collection log 171 is “sar”. Input to the allocation process 12. Therefore, in this case, the calculation process 13 uses resources corresponding to the CPU usage rate of 1% and the memory usage amount of 5 MB (megabytes) when collecting the log instructed by the log collection command related to the guest OS 20-j. Is input to the allocation process 12.

  The instruction process 11 collates an identifier that can identify the type of log to be collected included in the log collection command input to the hypervisor 10 from the guest OS 20-i with the collection log 171 in the collection log management information 170. The instruction processing 11 uses the value indicated by the resource type 173 in the record including the collection log 171 whose value is equal to the identifier that can identify the type of log to be collected included in the log collection command, as the contention resource in the contention resource management information 150. Match with type 151. The instruction process 11 is a request destination for requesting log collection based on the value indicated by the resource competition guest ID 152 in the record in which the value indicated by the conflict resource type 151 is a value related to the value indicated by the resource type 173. The guest OS 20-j is determined. The instruction process 11 also includes the value “Hypervisor” as the value indicated by the log collection target 174 in the record including the collection log 171 whose value is equal to the identifier that can identify the type of log to be collected included in the log collection command. In this case, the hypervisor 10 is the request destination for requesting log collection.

  For example, consider a case where the type of log to be collected included in the log collection command input to the hypervisor 10 from the guest OS 20-1 is a log collected by the “sar” command. In this case, the instruction process 11 refers to the collection log management information 170, the value indicated by the resource type 173 in the record whose value indicated by the collection log 171 is “sar” is “System”, and the log collection target 174 indicates Confirm that the value is “Guest OS”.

  In the instruction processing 11, since the value indicated by the resource type 173 is “System”, the value indicated by the contention resource type 151 in the contention resource management information 150 is “Cpu”, “Mem”, and “Disk”. The value indicated by the resource competition guest ID 152 is confirmed. In this case, since the guest OSs whose resources compete with the guest OS 20-1 are the guest OSs 20-2 to 3, the instruction process 11 determines the guest OSs 20-2 to 3 as request destinations for requesting log collection.

  The instruction process 11 inputs an identifier that can identify the guest OS 20-j determined as a request destination for log collection and a log collection command issued by the guest OS 20-i to the allocation process 12 and the calculation process 13. To do. Then, the instruction process 11 instructs the guest OS 20-j to collect a log specified by the log collection command.

  The collection log management information generation process 14 measures the amount of resources used when any one of the guest OSs 20-1 to 20-n or the hypervisor 10 collects a specific log. The measurement result related to the amount of the resource includes the CPU usage rate required for collecting the log or the memory capacity required for storing the collected log in the memory. The collection log management information generation process 14 sets the measurement result to a value indicated by the log collection cost 172. The collection log management information generation process 14 uses, as a record in the collection log management information 170, a record in which the collection log 171 related to the specific log, the resource type type 173, and the log collection target 174 are associated with the log collection cost 172. And stored in the collection log management information storage unit 17.

  The log collection process 18 collects logs that can be collected by the hypervisor 10 based on the contents of the user using the guest OS 20-i or the instruction from the hypervisor 10. Examples of logs that can be collected in the hypervisor 10 include logs related to virtualization-related events that occur in the hypervisor 10. The log collection process 18 stores the collected log in the shared buffer generated by the hypervisor 10.

  Next, the operation (processing) of the virtual machine management apparatus 1 according to the present embodiment will be described in detail with reference to the flowcharts of FIGS. 2A to 2B.

  The collection log setting process 21-i accepts a log collection instruction specifying the type of log to be collected, which is input by the user, in the guest OS 20-i, and inputs the log collection instruction to the hypervisor 10 (step S101). ). The instruction processing 11 determines the guest OS 20-j that requests log collection by comparing the log collection command with the conflicting resource management information 150 and the collection log management information 170, and can identify the guest OS 20-j. The log collection command is input to the allocation process 12 and the calculation process 13 (step S102).

  The calculation process 13 inputs the value indicated by the log collection cost to the allocation process 12. The value indicated by the log collection cost is a value calculated by the calculation process 13 by collating the type of log to be collected included in the log collection command with the collection log management information 170 (step S103). The allocation process 12 cuts out the resource indicated by the value indicated by the log collection cost input from the calculation process 13 from the resources allocated to the guest OS 20-i (step S104). The allocation process 12 allocates the resource cut out from the guest OS 20-i to the guest OS 20-j to which the identifier is input from the instruction process 11 (step S105).

  The instruction process 11 instructs the guest OS 20-j to collect a log specified by the log collection command (step S106). The log collection process 22-j collects the designated log in the guest OS 20-j and stores the collected log in the shared buffer generated by the hypervisor 10 (step S107). The log reading process 23-i reads the collected log from the shared buffer and outputs the contents of the log to an output device such as a monitor that outputs information on the guest OS 20-i (step S108). The process ends.

  The virtual machine management device 1 according to the present embodiment does not affect processing originally performed by another virtual machine when the other virtual machine collects log information in accordance with an instruction from the specific virtual machine. Can be. The reason is that the allocation process 12 is necessary for the instruction processing 11 to perform log collection for the guest OS 20-j determined as a request destination for requesting log collection based on a request from the guest OS 20-i. This is because a resource to be added is allocated.

  In a system in which a plurality of virtual machines are constructed, performance problems may occur by sharing resources such as a CPU or memory between virtual machines. In this case, a user who uses a specific virtual machine cannot fully analyze performance problems from log information that can be collected from the virtual machine that he or she uses. Request collection. Other virtual machines requested to collect log information collect log information using a part of the allocated resources in accordance with the request. Therefore, at this time, the resource for executing the process that should be originally performed by the other virtual machine is temporarily reduced, and thus the process that should be performed by the other virtual machine is affected.

  On the other hand, when the virtual machine management device 1 according to the present embodiment requests the guest OS 20-j to collect logs based on a request from the guest OS 20-i, Allocate additional resources that are necessary to perform such log collection. Therefore, when the guest OS 20-j performs log collection using the additionally allocated resource, the virtual machine management apparatus 1 can avoid affecting the processing that the guest OS 20-j should originally perform. .

  In this embodiment, the allocation process 12 cuts out the resources allocated to the guest OS 20-j from the resources allocated to the guest OS 20-i, but there are resources that are not in use. In this case, at least a part of the resource that is not in use may be cut out. Thereby, the virtual machine management apparatus 1 can cause the guest OS 20-j to collect logs without affecting the guest OS 20-i in addition to the guest OS 20-j.

  In addition, the allocation processing 12 according to the present embodiment associates the guest OSs in a competition state with respect to a specific resource among the guest OSs 20-1 to 20 -n based on the resource allocation information 160, so 150 is generated. Therefore, in the virtual machine management device 1 according to the present embodiment, the user does not need to create the competing resource management information 150, so the burden on the user can be reduced.

  Further, the instruction processing 11 according to the present embodiment collates the log collection command input from the guest OS 20-i with the conflicting resource management information 150 and the collection log management information 170. As a result, the instruction process 11 can select the guest OS 20-j whose resource competes with the guest OS 20-i in relation to the log information instructed by the log collection command. Therefore, in the virtual machine management device 1 according to the present embodiment, the user using the guest OS 20-i does not need to specify the guest OS 20-j, so the burden on the user can be reduced.

  Furthermore, the calculation processing 13 according to the present embodiment calculates in detail the amount of resources required for the guest OS 20-j to perform log collection instructed by the log collection command based on the collection log management information 170, The calculated result is input to the assignment process 12. Therefore, the virtual machine management apparatus 1 according to the present embodiment can efficiently allocate resources necessary for log collection to the guest OS 20-j. In the present embodiment, the calculation process 13 calculates the amount of the resource based on the collection log management information 170. However, the calculation process 13 calculates the amount of the resource using another criterion. Also good. For example, the calculation process 13 may calculate the amount of the resource by using a predetermined calculation formula from information indicating the system state related to the virtual machine management device 1 or the like.

  In addition, the collection log management information generation process 14 according to the present embodiment measures the amount of resources used when any of the guest OSs 20-1 to n or the hypervisor 10 collects a specific log. Collection log management information 170 is generated based on the measurement result. Therefore, the virtual machine management device 1 according to the present embodiment can set the reference value when the calculation process 13 calculates the amount of resources more accurately. Further, in the virtual machine management device 1, since the user does not need to create the collection log management information 170, the burden on the user can be reduced.

  Note that the log information that the virtual machine management apparatus 1 according to the present embodiment instructs the guest OS 20-j to collect is not limited to the log information related to the performance information. For example, even when a guest OS-i in which a failure has occurred requests another guest OS to collect a failure log, the virtual machine management device 1 according to the present embodiment performs the same processing as described above. be able to.

<Second Embodiment>
FIG. 7 is a block diagram conceptually showing the structure of the virtual machine management device 3 of the second embodiment.

  The virtual machine management device 3 of this embodiment includes an instruction unit 31 and an allocation unit 32.

  The instruction unit 31 operates using a resource that the information processing apparatus has to execute information processing, receives a log collection instruction that instructs log collection, and collects log information in a first virtual machine among a plurality of virtual machines The log collection command is received from the virtual machine 41. The instruction unit 31 selects the second virtual machine 42 from among the plurality of virtual machines based on a predetermined criterion according to the log collection command, and issues the log collection command to the second virtual machine 42. input.

  The allocation unit 32 adds and allocates the resource to the second virtual machine 42 when the instruction unit 31 inputs the log collection command to the second virtual machine 42.

  The virtual machine management apparatus 3 according to the present embodiment does not affect processing originally performed by another virtual machine when the other virtual machine collects log information in accordance with an instruction from the specific virtual machine. Can be. The reason is that the allocating unit 32 performs the log collection for the second virtual machine 42 that is determined as the request destination from which the instruction unit 31 requests log collection based on the request from the first virtual machine 41. This is because the resources necessary for this are added and allocated.

  The instruction unit 31 and the assigning unit 32 can be regarded as a function (processing) unit (software module) of the software program. The hardware environment in this case is the same as that of the virtual machine management apparatus 1 shown in FIG.

  The present invention has been described above using the above-described embodiment as an exemplary example. However, the present invention is not limited to the above-described embodiment. That is, the present invention can apply various modes that can be understood by those skilled in the art within the scope of the present invention.

DESCRIPTION OF SYMBOLS 1 Virtual machine management apparatus 10 Hypervisor 11 Instruction process 12 Assignment process 13 Calculation process 14 Collection log management information generation process 15 Competing resource management information storage part 150 Competing resource management information 151 Competing resource type 152 Resource competition relation guest ID
16 Resource allocation information storage unit 160 Resource allocation information 161 Guest ID
162 Resource type 163 Virtual resource 164 Physical resource 165 Resource allocation 17 Collection log management information storage 170 Collection log management information 171 Collection log 172 Log collection cost 173 Resource type 174 Log collection target 18 Log collection processing 20-1 to n Guest OS
21-1 to n Collection log setting processing 22-1 to n Log collection processing 23-1 to n Log read processing 3 Virtual machine management device 31 Instruction unit 32 Allocation unit 41 First virtual machine 42 Second virtual machine 901 CPU
902 ROM
903 RAM
904 Hard disk 905 Communication interface 906 Bus 907 Storage medium 908 Reader / writer 909 Input / output interface

Claims (10)

The information processing apparatus operates using a resource for executing information processing, receives the log collection command for instructing log collection, and collects log information from the first virtual machine among the plurality of virtual machines. In accordance with a log collection instruction, an instruction means for selecting a second virtual machine from the plurality of virtual machines based on a predetermined criterion and inputting the log collection instruction to the second virtual machine;
When the instruction means inputs the log collection command to the second virtual machine, an assigning means for additionally assigning the resource to the second virtual machine;
A virtual machine management device. The assigning means assigns a part of the resource assigned to the first virtual machine to the second virtual machine,
The virtual machine management apparatus according to claim 1. A calculation means for calculating an allocation amount related to the resource necessary for the second virtual machine to collect the log information in response to the log collection command based on a predetermined criterion;
The allocation unit allocates the resource indicated by the allocation amount calculated by the calculation unit to the second virtual machine.
The virtual machine management apparatus according to claim 1 or 2. A collection log management information storage unit for storing collection log management information in which an identifier that can identify the content of the log information to be collected and the allocated amount necessary to collect the log information are associated with each other;
The calculation means calculates the allocated amount by comparing information indicating the content of the log information to be collected included in the log collection instruction with the collection log management information.
The virtual machine management apparatus according to claim 3. The virtual machine further includes a collection log management information generation unit that measures the amount of the resource used when collecting the log information and generates the collection log management information using the measurement result as the allocated amount.
The virtual machine management apparatus according to claim 4. Comprising resource management information storage means for storing contention resource management information in which identifiers capable of identifying two or more virtual machines sharing the same resource are associated with each other;
The instruction means sets the virtual machine identified by the identifier associated with the identifier capable of identifying the first virtual machine in the contention resource management information as the second virtual machine.
The virtual machine management apparatus according to claim 1. The contention resource management information storage unit stores the contention resource management information in which an identifier capable of identifying the type of the resource shared by two or more virtual machines is further associated with an identifier capable of identifying the virtual machine. ,
The instruction means selects the second virtual machine based on information indicating the content of the log information to be collected included in the log collection command and the contention resource management information.
The virtual machine management apparatus according to claim 6. The allocation unit generates resource allocation information in which an identifier capable of identifying the virtual machine and an identifier capable of identifying the resource allocated to the virtual machine are generated, and based on the resource allocation information, the contention resource Generate management information,
The virtual machine management apparatus according to claim 6 or 7. By the first information processing device
A plurality of virtual machines that operate using resources for executing information processing, and that collect log information in response to a log collection command for instructing log collection of the first information processing apparatus or the second information processing apparatus A second virtual machine is selected from the plurality of virtual machines based on a predetermined criterion in accordance with the log collection command from the first virtual machine in the first virtual machine, and the log for the second virtual machine is selected. Enter the collection command,
When the log collection command is input to the second virtual machine, the resource is added and allocated to the second virtual machine.
Virtual machine management method. The information processing apparatus operates using a resource for executing information processing, receives the log collection command for instructing log collection, and collects log information from the first virtual machine among the plurality of virtual machines. In accordance with a log collection instruction, an instruction process for selecting a second virtual machine from the plurality of virtual machines based on a predetermined criterion and inputting the log collection instruction to the second virtual machine;
When the instruction process inputs the log collection command to the second virtual machine, an allocation process for adding and allocating the resource to the second virtual machine;
A virtual machine management program that causes a computer to execute.

Images