WO2017022008A1

WO2017022008A1 - Computer, control method and control program

Info

Publication number: WO2017022008A1
Application number: PCT/JP2015/071777
Authority: WO
Inventors: 翔一竹内; 周平松本
Original assignee: 株式会社日立製作所
Priority date: 2015-07-31
Filing date: 2015-07-31
Publication date: 2017-02-09

Abstract

Provided is a computer in which a virtual computer operates, the computer including: a storage device that stores a virtualization program which controls the virtual computer; a processor that executes the virtualization program; and an interface that transmits and receives data. The processor executes: an acquisition process for acquiring, from the interface, a message that includes destination information of either the computer or the virtual computer and the contents of a power source operation in respect to the destination identified by the destination information; and a control process whereby, if the destination information included in the message acquired by the acquisition process is not the destination information of the computer, the virtualization program is controlled and the virtual computer executes a process in accordance with the contents of the power source operation.

Description

Computer, control method, and control program

The present invention relates to a computer on which a virtual computer operates, a control method, and a control program.

In recent years, it is not uncommon for companies to rent business machines to build business systems. The cloud service provider not only lends a physical machine, but also creates a plurality of virtual machines by virtualizing the physical machine, and lends the virtual machine to a customer who does not need much performance. By making a physical machine into a plurality of virtual machines, the cloud service provider can reduce the number of physical machines and, in turn, can reduce electricity bills and place bills.

On the other hand, when using a physical machine remotely, a cloud user issues a power operation request to the physical machine and turns the power on or off. When using a virtual machine, a cloud user needs to make a power supply operation request to the hypervisor on the physical machine to start or turn off the virtual machine. In this situation, as the number of machines used increases, it becomes more complicated to manage whether the machine is a virtual machine or a physical machine.

There is also a virtual PC management system that reduces power consumption in a thin client system that uses a virtual PC (see, for example, Patent Document 1 below). The virtual PC management system disclosed in Patent Document 1 includes a unit that acquires a power state of a virtual machine from a computer via a network and stores it in a storage unit; a unit that acquires a power state of the computer from a computer via a network and stores the storage unit in a storage unit; Receiving a virtual machine use start request from the operation terminal, searching for stored computer storage data as a candidate for assignment to a computer that is powered on and unassigned by the virtual machine, and issuing a use start request to the assignment candidate computer Means for allocating a corresponding virtual machine, and means for notifying an allocation candidate computer of an instruction to turn on the virtual machine via the network.

Wake-on-LAN (WoL) is a method for starting a virtual machine remotely like a physical machine. However, WoL can only start a virtual machine and does not have a power-off interface (see, for example, Patent Document 2 below).

There is also a management virtual machine that can operate as a proxy for other virtual machines on the virtual machine host (see, for example, Patent Document 3 below). The management virtual machine may maintain a database of network management information associated with each virtual machine on the host. The advanced virtual machine manager on the host may provide an interface to the management virtual machine so that the management virtual machine can capture multiple management messages for multiple virtual machines on the host. The management virtual machine may respond to multiple messages based on information in the database and may issue queries to multiple virtual machines to obtain essential information. The management virtual machine may aggregate information from various virtual machines before responding to network management messages.

JP 2010-86423 A US Patent Application Publication No. 2009/0241113 Special table 2007-513405 gazette

However, in the above-described conventional technology, it is necessary to issue a command for operating the power of the virtual machine from the user to the hypervisor. There is no management server for each virtual machine. For this reason, the hypervisor itself manages a management server or a plurality of hypervisors together with a single management server. The user must select whether the machine to be used is a virtual machine or a physical machine, and if it is a physical machine, it must issue an instruction for the physical machine, and if it is a virtual machine, it issues an instruction for operating the management server that can operate the virtual machine. As the number of machines used increases, it is necessary to manage whether each machine is a physical machine or a virtual machine. An object of the present invention is to improve the convenience of power operation for a machine.

A computer according to an aspect of the invention disclosed in the present application is a computer on which a virtual computer operates, and the computer executes a storage device that stores a virtualization program that controls the virtual computer and the virtualization program A processor for transmitting and receiving data, and the processor receives destination information of either the computer or the virtual machine and power operation details for the destination specified by the destination information from the interface. An acquisition process for acquiring a message including, and if the destination information included in the message acquired by the acquisition process is not the destination information of the computer, the virtualization program is controlled to perform processing according to the power operation content And a control process executed by the virtual machine.

According to the representative embodiment of the present invention, it is possible to improve the convenience of power operation for a machine. Problems, configurations, and effects other than those described above will become apparent from the description of the following embodiments.

It is a block diagram which shows the system configuration example of the computer system concerning a present Example. It is a block diagram which shows the concrete hardware structural example of the computer system concerning a present Example. It is explanatory drawing which shows an example of the IP address table for IPMI. It is explanatory drawing which shows an example of a user information table. It is explanatory drawing which shows an example of a session table. It is explanatory drawing which shows an example of a temporary session table. It is explanatory drawing which shows the correspondence table of the number of Network Function Code defined beforehand, and its meaning. It is explanatory drawing which shows the correspondence table of the command number and meaning of Network Function defined beforehand. It is explanatory drawing which shows the correspondence table of the Completion Code number of the command defined beforehand, and its meaning. It is explanatory drawing which shows the corresponding | compatible table | surface of the number of Chassis Control previously defined, and its meaning. It is explanatory drawing which shows the correspondence table of the number of Authentication Type currently defined, and its meaning. It is a flowchart which shows the starting process of the IPMI process for virtual machines, and the example of a cutoff process procedure. 13 is a flowchart illustrating a detailed processing procedure example of virtual machine IPMI process activation processing (step S1201) illustrated in FIG. 12; 13 is a flowchart illustrating a detailed processing procedure example of a virtual machine IPMI process blocking process (step S1202) illustrated in FIG. 12; It is explanatory drawing which shows the example of a sequence between a remote management system and the IPMI process for virtual machines. It is a flowchart which shows the example of a classification | category process procedure of the IPMI message by the IPMI process for virtual machines. 12 is a flowchart (part 1) illustrating an example of a session establishment processing procedure by an IPMI process for a virtual machine. It is explanatory drawing which shows an example of the packet which satisfy | fills the conditions of step S1701. It is explanatory drawing which shows an example of the packet produced | generated by step S1702. It is explanatory drawing which shows an example of the packet produced | generated by step S1705. 12 is a flowchart (part 2) of a procedure example of session establishment processing by the virtual machine IPMI process. It is explanatory drawing which shows an example of the packet which satisfy | fills the conditions of step S2101. It is explanatory drawing which shows an example of the packet produced | generated by step S2106. FIG. 10 is a flowchart (part 3) illustrating a procedure example of session establishment processing by a virtual machine IPMI process. FIG. It is explanatory drawing which shows an example of the packet produced | generated by step S2401. FIG. 10 is a flowchart (part 4) illustrating an example of a session establishment processing procedure by the virtual machine IPMI process. FIG. It is explanatory drawing which shows an example of the packet produced | generated by step S2610 of FIG. FIG. 12 is a flowchart (part 5) illustrating an example of a session establishment processing procedure by the virtual machine IPMI process. It is explanatory drawing which shows an example of the packet produced | generated by step S2806 of FIG. FIG. 16 is a flowchart (part 6) illustrating an example of a session establishment processing procedure by the virtual machine IPMI process 053; FIG. It is explanatory drawing which shows an example of the packet used as the production | generation source of the hash value produced | generated by step S3001 of FIG. It is explanatory drawing which shows an example of the packet produced | generated by step S3007 of FIG. FIG. 16 is a flowchart (No. 7) illustrating an example of a session establishment processing procedure using the virtual machine IPMI process. FIG. It is explanatory drawing which shows an example of the packet produced | generated by step S3303 of FIG. It is a flowchart (the 8) which shows the example of a session establishment process sequence by the IPMI process for virtual machines. It is explanatory drawing which shows an example of the packet produced | generated by step S3502 of FIG. 12 is a flowchart (part 1) illustrating an example of an authentication data verification processing procedure by an IPMI process for a virtual machine. 12 is a flowchart (part 2) illustrating an example of the authentication data verification processing procedure by the virtual machine IPMI process. FIG. 12 is a flowchart (part 3) illustrating an example of an authentication data verification processing procedure by an IPMI process for virtual machines. FIG. 10 is a flowchart (part 4) illustrating an example of the authentication data verification processing procedure by the virtual machine IPMI process. FIG. It is explanatory drawing which shows an example of the packet produced | generated by step S4001 of FIG. FIG. 10 is a flowchart (part 5) illustrating an example of the authentication data verification processing procedure by the IPMI process for virtual machines. FIG. 43 is an explanatory diagram illustrating an example of a packet generated in step S4201 of FIG. 10 is a flowchart (part 1) illustrating an example of a virtual machine power supply operation request processing procedure by an IPMI process for virtual machines. FIG. 45 is an explanatory diagram illustrating an example of a received packet that triggers execution of step S4401 of FIG. 44. It is explanatory drawing which shows the example of the received packet used as the trigger of execution of step S4403 of FIG. It is explanatory drawing which shows the example of the packet produced | generated by step S4406 of FIG. FIG. 10 is a flowchart (part 2) illustrating an example of a virtual machine power supply operation request processing procedure by the virtual machine IPMI process. FIG. It is explanatory drawing which shows the example of the packet produced | generated by step S4801 of FIG. It is a flowchart which shows the example of a session interruption | blocking request | requirement processing procedure by the IPMI process for virtual machines. It is explanatory drawing which shows the example of the packet which shows a session interruption | blocking request | requirement. It is explanatory drawing which shows the example of the packet produced | generated by step S5003 of FIG. 12 is a flowchart (part 1) illustrating an example of a session cutoff processing procedure by the virtual machine IPMI process. 12 is a flowchart (part 2) illustrating an example of a session cutoff processing procedure by the virtual machine IPMI process. FIG. 57 is an explanatory diagram showing an example of packets generated in step S5306 in FIG. 53 and step S5406 in FIG. 54. 12 is a flowchart (part 1) illustrating an example of a termination process procedure of a virtual machine IPMI process. 12 is a flowchart (part 2) illustrating an example of a termination process procedure of the virtual machine IPMI process.

The present embodiment is a computer system that applies Intelligent Platform Management Interface (hereinafter referred to as IPMI), which is an interface for operating a physical machine, to a virtual machine. As a result, the user can start or shut down the machine without being aware of whether the type of machine that is the target of power operation is a physical machine or a virtual machine. Improvements can be made.

In the following, each process in this embodiment will be described with “program” such as a hypervisor, an OS (Operating System), an application, and a virtual machine as examples of virtualization programs that realize virtualization control. However, since the program performs the process defined by being executed by the processor using the memory and the port, the description may be made with the processor as the subject.

In addition, when there are a plurality of the same type of constituent elements, a reference numeral is given to each, but when the plurality of the same type of constituent elements are not distinguished, the reference numerals may be combined. For example, when the

virtual machines

061 and 062 are not distinguished from each other, they may be simply represented as virtual machines 06. When the

guest OSs

081 and 082 are not distinguished from each other, they may be simply represented as guest OS08.

<System configuration example of computer system>
FIG. 1 is a block diagram illustrating a system configuration example of a computer system according to the present embodiment. FIG. 2 is a block diagram illustrating a specific hardware configuration example of the computer system according to the present embodiment. The computer system includes a physical machine 001 that is a computer (physical computer), a remote management system 020, and a hypervisor operation client 021. The physical machine 001 and the remote management system 020 are communicably connected via the network 010. The physical machine 001 and the hypervisor operation client 021 are communicably connected via the network 010. Examples of the network 010 include a LAN (Local Area Network), a WAN (Wide Area Network), and the Internet.

The hypervisor operation client 021 is a computer used by an administrator who manages the physical machine 001. The hypervisor operation client 021 sets values in the IPMI IP address table 100 and the user information table 110 in the hypervisor 030 via the network 010.

The remote management system 020 is an IPMI client in which a user who uses the physical machine 001 operates the power supply for the physical machine 001 that is the operation target machine and the virtual machine (virtual computer) 06 on the physical machine 001. The remote management system 020 transmits an IPMI message to the physical machine 001 via the network 010. The IPMI message includes a message related to a power supply operation request and a message related to user authentication. The message related to the power operation request includes, for example, identification information (eg, IP address) that uniquely identifies the operation target machine and power operation details (startup or shutdown). The message related to user authentication includes, for example, the user name and password of the remote management system 020 and identification information (eg, IP address) that uniquely identifies the operation target machine.

Briefly describing the present embodiment, (1) the remote management system 020 selects a power operation target machine from the screen of the remote management system 020 and transmits an IPMI message regarding the power operation request to the physical machine 001. The user of the remote management system 020 is not conscious of whether the power operation target machine is the physical machine 001 or the virtual machine 06.

The physical machine 001 receives an IPMI message related to the power operation request at a first NIC (Network Interface Card) 005. (2) When the identification information included in the received IPMI message is the IP address of the physical machine 001, the physical machine 001 executes processing according to the power operation content specified by the IPMI message. That is, the physical machine 001 is started if the power operation content is “startup”, and the physical machine 001 is shut down if it is “shutdown”.

(3) When the identification information included in the received IPMI message is not the IP address of the physical machine 001, the physical machine 001 passes the IPMI message to the management OS 040. If the virtual machine IPMI process 053 has not been generated for the virtual machine 06 that is the power operation target, the management OS 040 generates the virtual machine IPMI process 053. Then, the management OS 040 passes an IPMI message to the virtual machine IPMI process 053 for the virtual machine 06 that is the power operation target.

(4) The virtual machine IPMI process 053 controls the hypervisor 030 and responds to the power supply operation specified by the IPMI message via the hypervisor operation I / F 042 for the virtual machine specified by the IPMI message. Execute the process. That is, if the power operation content is power ON, the designated virtual machine 06 is started, and if the power operation is OFF, the designated virtual machine is shut down.

In this way, the user can start or shut down the machine without being aware of whether the type of machine that is the target of power operation is the physical machine 001 or the virtual machine 06. Convenience can be improved.

In order to explain the processes (1) to (4) in detail, each element in FIG. 1 will be explained. The physical machine 001 includes a CPU 002, a memory 003, a storage device 004, a first NIC 005, a timer 006, and an input / output device 007.

The CPU002 controls the physical machine 001. The CPU 002 loads the program stored in the storage device 004 into the memory 003 and executes the program. The memory 003 stores programs such as a hypervisor 030, a management OS 040,

virtual machines

061, 062,

guest OSs

081, 082, and an IPMI server application 050. The storage device 004 stores programs, data, and tables. The number of

virtual machines

061, 062 is not limited to two, and may be one or three or more. Similarly, the number of

guest OSs

081 and 082 is not limited to two, and may be one or three or more.

The first NIC 005 connects the remote management system 020 and the hypervisor operation client 021 via the network 010 so that they can communicate with each other. The first NIC 005 determines whether the identification information included in the received IPMI message is the IP address of the physical machine 001. If it is the IP address of the physical machine 001, the IPMI message is passed to the CPU 002. As a result, the CPU 002 executes processing according to the power operation content specified by the IPMI message.

Timer 006 is a device for measuring time. The input / output device 007 is a device that receives data input and outputs data. Examples of the input / output device 007 include a keyboard, a mouse, a touch panel, a numeric keypad, a scanner, a display, and a printer.

The hypervisor 030 is a program that controls the CPU 002, the memory 003, the storage device 004, the NIC 005, the timer 006, and the input / output device 007, which are hardware in the physical machine 001. The hypervisor 030 has setting information 031. The setting information 031 includes an IPMI IP address table 100 and a user information table 110. The IPMI IP address table 100 is information in which the virtual machine number of the virtual machine 06 and the IP address are associated with each other. The user information table 110 is information in which the user name and password of the remote management system 020 are associated with each other.

The hypervisor 030 receives an error notification, a power-off request for the virtual machine 06, and a startup request from the hypervisor operation interface (hereinafter referred to as I / F) 042 on the management OS 040. When the hypervisor 030 is notified of the error, the hypervisor 030 notifies the hypervisor operation client 021 of the error. When the hypervisor 030 receives a power-off request for the virtual machine 06, the hypervisor 030 stops the virtual machine 06 that is the target of the power-off request. When the hypervisor 030 receives a startup request for the virtual machine 06, the hypervisor 030 starts the virtual machine 06 that is the target of the startup request.

The management OS 040 is an OS that controls the hypervisor 030. The management OS 040 has a timer function 041, a hypervisor operation I / F 042, and a second NIC 043. The management OS 040 operates the IPMI server application 050 on the management OS 040.

The timer function 041 is a program that controls the timer 006 to measure time. The timer function 041 has already been registered by specifying the notification destination and time, specifying the notification destination after the specified time has elapsed, and specifying the setting release to the notification destination. And the function of canceling the notification.

The hypervisor operation I / F 042 writes information from the hypervisor operation client 021 in the setting information 031 of the hypervisor 030. When the management OS 040 detects that the same IP address has already been registered in the IPMI IP address table 052 when registering the IP address in the IPMI IP address table 052, the hypervisor operation I / F 042 The error is notified to the hypervisor 030. Further, when the power operation content included in the IPMI message is “startup”, the hypervisor operation I / F 042 sends a startup instruction for the virtual machine 06 from the management OS 040 to the hypervisor 030 and is included in the IPMI message. When the content of the power operation is “shutdown”, a shutdown instruction for the virtual machine from the management OS 040 is sent to the hypervisor 030.

The second NIC 043 is a virtual NIC set in the management OS 040. The second NIC 043 is assigned the IP address of the virtual machine IPMI process 053 corresponding to the virtual machine 06. The second NIC 043 receives the IPMI message from the first NIC 005.

The IPMI server application 050 includes a user information table 051 and an IPMI IP address table 052. The IPMI server application 050 copies the user information table 110 and the IPMI IP address table 100 from the hypervisor 030 via the management OS 040, and holds them as the user information table 051 and the IPMI IP address table 052. The IPMI server application 050 operates virtual machine IPMI processes 053 for the number of virtual machines 06 on the IPMI server application 050.

Each of the virtual machine IPMI processes 053 has a session table 120 and a temporary session table 130. The session table 120 is a table for managing a session by a user of the remote management system 020, and the temporary session table 130 is a table for temporarily managing a session by a user of the remote management system 020.

On the first virtual machine 061 and the second virtual machine 062, the first guest OS 081 and the second guest OS 082 in the memory 003 of the first virtual machine 061 and the second virtual machine 062 can be operated. In the example of FIG. 1, the first guest OS 081 is operating on the first virtual machine 061, and the second guest OS 082 is not yet operating on the second virtual machine 062.

In this embodiment, the IPMI server 053 that receives an IPMI message and performs processing according to the content is the IPMI process 053 for virtual machines. The remote management system 020, which is an IPMI client, sends an IPMI message to the IP address of the virtual machine IPMI process 053 corresponding to the virtual machine to be powered on. The remote management system 020 only sends an IPMI message to the IP address held in advance and the IPMI port of UDP (User Datagram Protocol). The remote management system 020 does not need to be aware of whether the type of machine to be operated by the IPMI message is a physical machine 001 or a virtual machine.

<Table configuration example>
Next, the various tables shown in FIG. 1 will be specifically described.

FIG. 3 is an explanatory diagram showing an example of the IPMI IP address tables 100 and 052. The IPMI IP address table 052 is a duplicate of the IPMI IP address table 100, and a description thereof will be omitted. The IPMI IP address table 100 is destination correspondence information for storing destination information for each virtual machine. Specifically, for example, the IPMI IP address table 100 is stored in advance in the setting information 031 of the hypervisor 030, and the second NIC 043 and the hypervisor operation I / F 042 of the management OS 040 are set by the operation from the hypervisor operation client 021. Entries can be added, changed, or deleted. The IPMI IP address table 100 has a virtual machine number 101 and an IP address 102 as fields. The virtual machine number 101 is an area for storing a number that uniquely identifies the virtual machine as a value. The IP address 102 is an area for storing the IP address of the virtual machine IPMI process 053 corresponding to the virtual machine.

The IPMI server application 050 generates the virtual machine IPMI process 053 corresponding to the number of entries in the copied IPMI IP address table 052. The generated virtual machine IPMI process 053 receives the IPMI message addressed to the corresponding IP address, and performs processing according to the content included in the IPMI message.

FIG. 4 is an explanatory diagram showing an example of the user information tables 110 and 051. The user information table 051 is a duplicate of the user information table 110, and thus description thereof is omitted. The user information table 110 is stored in advance in the setting information 031 of the hypervisor 030, and an entry is added, changed, or deleted via the second NIC 043 of the management OS 040 and the hypervisor operation I / F 042 by an operation from the hypervisor operation client 021. Is possible. The user information table 110 has a user name 111 and a password 112 as fields. The user name 111 is an area for storing the identification information of the user of the remote management system 020 as a value. The password 112 is an area for storing a password used for user authentication for establishing a session between the remote management system 020 and the virtual machine IPMI process 053 as a value.

FIG. 5 is an explanatory diagram showing an example of the session table 120. The session table 120 is a table for managing a session established between the remote management system 020 and the virtual machine IPMI process 053. The session table 120 has a session ID 121, a user name 122, and a password 123 as fields.

Session ID 121 is an area for storing identification information (session ID) that uniquely identifies an established session as a value. The value of the session ID 121 is given to the user name 122 and password 123 that have been authenticated. The value of the session ID 121 is a serial number from “0”. In the initial state, session IDs 121 of the session table 120 are stored for the number of sessions supported by the IPMI server application 050. In the example of FIG. 5, since the number of sessions supported by the IPMI server application 050 is “4”, four session IDs “0” to “3” are stored as the value of the session ID 121.

The user name 122 is an area for storing the identification information of the user of the remote management system 020 as a value. The password 123 is an area for storing a password used for user authentication for establishing a session between the remote management system 020 and the virtual machine IPMI process 053 as a value. That is, the user name 122 and the password 123 are empty in the initial state. When the remote management system 020 and the virtual machine IPMI process 053 are user-authenticated for session establishment, in the entry of the session ID 121 to be established, the user name 111 and the user name 111 and The value of the password 112 is stored.

FIG. 6 is an explanatory diagram showing an example of the temporary session table 130. The temporary session table 130 is a table for managing a temporarily generated session in user authentication before establishing a session. The temporary session table 130 includes a session ID 131, a user name 132, a password 133, and a challenge string 134 as fields. In the initial state, the entry in the temporary session table 130 is empty.

Session ID 131 is an area for storing a temporary session ID as a value. The user name 132 is an area for storing identification information of the user of the remote management system 020 as a value. The password 133 is an area for storing a password used for user authentication for establishing a session between the remote management system 020 and the virtual machine IPMI process 053 as a value. The challenge string 134 is an area for storing a randomly generated character string (challenge string) as a value. The challenge string is used when a session is established.

<Description of code and command>
Next, the meanings of codes and commands used in this embodiment will be described with reference to FIGS. Note that “Chassis” means the physical machine 001, and “Application” means the IPMI server application 050.

FIG. 7 is an explanatory diagram showing a correspondence table between predefined Network Function Code numbers and their meanings. Network Function Code 600 is an identification code of the network function. A meaning (Network Function) 601 is a definition of a network function corresponding to the identification code. Note that the value obtained by adding 1 to the request of the network function code 600 is the response.

FIG. 8 is an explanatory diagram showing a correspondence table between predefined Network Function command numbers and meanings. The Network Function Code 610 corresponds to the meaning (Network Function) 601 in FIG. The command number 611 is an identification code related to a network function command. The meaning (command) 612 is a definition of a command corresponding to the identification code.

FIG. 9 is an explanatory diagram showing a correspondence table between the Completion Code numbers of commands defined in advance and their meanings. The command 620 corresponds to the meaning (command) 612 in FIG. Completion Code 621 is a value returned from the virtual machine IPMI process 053 when the command 620 is executed. The meaning 622 is the definition of Completion Code 621.

FIG. 10 is an explanatory diagram showing a correspondence table between previously defined Chassis Control numbers and their meanings. The Chassis Control 630 is a code indicating the power operation content included in the IPMI message. The meaning 631 is the definition of the code. “Power down” is power OFF (power cutoff, shutdown), and “Power up” is power ON (startup). The Chassis Control 630 is the power operation content of the IPMI message for the physical machine 001, but the remote management system 020 that issues the IPMI message does not matter what type of machine is the power operation target. On the other hand, the physical machine 001 determines whether the power operation target is the physical machine 001 or the virtual machine 06 based on the IP address included in the IPMI message.

FIG. 11 is an explanatory diagram showing a correspondence table between predefined Authentication Type numbers and their meanings. The Authentication Type 640 is an identification code indicating an authentication method. The meaning 641 is the definition of the identification code. “None” means no hashing, and “MD2” and “MD5” mean that hashing is performed using the same hash method. A packet for which “None” is specified in the Authentication Type has an Authentication Code value of “0”. Note that a method that can be processed by the virtual machine IPMI process 053 in the authentication method is defined in advance.

<Virtual Machine IPMI Process 053 Startup Process and Blocking Process Example>
FIG. 12 is a flowchart illustrating an example of a procedure for starting and blocking the virtual machine IPMI process 053. The IPMI server application 050 executes a startup process for starting the virtual machine IPMI process 053 (step S1201), and thereafter executes a blocking process for blocking the virtual machine IPMI process 053 (step S1202).

FIG. 13 is a flowchart showing a detailed processing procedure example of the activation process (step S1201) of the virtual machine IPMI process 053 shown in FIG. FIG. 13 shows an example in which the IPMI server application 050 executes processing for starting virtual machine IPMI processes 053 by the number of virtual machines.

First, when the IPMI server application 050 is activated, the IPMI server application 050 uses the hypervisor operation I / F 042 in the management OS 040 to set the IPMI IP address table 100 and the user from the setting information 031 in the memory area of the hypervisor 030. The information table 110 is read (step S1301).

Next, the IPMI server application 050 sets the first (first) entry in the read IPMI IP address table 052 as a target entry (step S1302). The IPMI server application 050 determines whether the IP address in the current target entry has already been assigned to the second NIC 043 of the management OS 040 (step S1303).

If it has been assigned (step S1303: Yes), the IP address in the IPMI IP address table 052 is duplicated. Therefore, the IPMI server application 050 notifies the hypervisor 030 of an error using the hypervisor operation I / F 042 of the management OS 040 (step S1304), and the IPMI server application 050 ends the startup process.

On the other hand, when the IP address in the current target entry is not assigned to the second NIC 043 of the management OS 040 (step S1303: No), the IPMI server application 050 assigns the IP address corresponding to the virtual machine 06 of the target entry to the management OS 040. It assigns to 2nd NIC043 (step S1305). Then, the IPMI server application 050 passes the virtual machine number to the virtual machine IPMI process 053 corresponding to the virtual machine 06, and starts the virtual machine IPMI process 053 (step S1306).

After the activation, the IPMI server application 050 checks whether the current target entry is the last entry in the IPMI IP address table 052 (step S1307). If it is not the last entry (step S1307: No), the virtual machine IPMI process 053 sets the next entry as the target entry (step S1308), and returns to step S1303.

In step S1307, when the current entry is the last entry in the IPMI IP address table 052 (step S1307: Yes), the IPMI server application 050 ends the activation process. Thereby, the assignment of the IP address to the second NIC 043 by the management OS 040 and the activation of the virtual machine IPMI process 053 are completed.

FIG. 14 is a flowchart showing a detailed processing procedure example of the blocking process (step S1202) of the virtual machine IPMI process 053 shown in FIG. In FIG. 14, the IPMI server application 050 waits for a shutdown signal from the management OS 040 (step S1401: No). When the management OS 040 receives a shutdown instruction from the hypervisor operation client 021, it issues a shutdown signal. When the shutdown signal is received (step S1401: Yes), the IPMI server application 050 sets the first (first) entry of the IPMI IP address table 052 as a target entry (step S1402). The IPMI server application 050 sends a shutdown signal to the virtual machine IPMI process in the target entry (step S1403). As a result, the virtual machine IPMI process 053 that has received the shutdown signal shuts itself down.

Then, the IPMI server application 050 waits for the end of the virtual machine IPMI process 053 of the target entry (step S1404: No), and when it ends (step S1404: Yes), the current target entry is the IPMI IP address table 052. It is determined whether it is the last entry (step S1405). If it is not the last entry (step S1405: No), the IPMI server application 050 sets the next entry as the target entry (step S1406) and returns to step S1403. On the other hand, if it is the last entry (step S1405: Yes), the IPMI server application 050 ends the blocking process.

<Example of sequence between remote management system 020 and virtual machine IPMI process 053>
FIG. 15 is an explanatory diagram showing a sequence example between the remote management system 020 and the virtual machine IPMI process 053. (A) is a phase in which a session is not established, (B) is a phase in which a session establishment is being requested, and (C) is a phase in which a session has been established. In the phases (A) to (C), after the startup process (step S1201) of the virtual machine IPMI process 053 shown in FIG. 13 ends, the shutdown process (step S1201) of the virtual machine IPMI process 053 shown in FIG. This is a sequence executed until step S1202) starts.

The remote management system 020 transmits a request for “Get Channel Authentication Capability” (see FIG. 18) to the IPMI process 053 for virtual machines (step S1501).

The virtual machine IPMI process 053 returns a response “Get Channel Authentication Capability” to the remote management system 020 (see FIG. 19) (step S1502). The response includes an authentication type.

The remote management system 020 transmits a “Get Session Challenge” request (see FIG. 22) to the virtual machine IPMI process 053 (step S1503). The request includes the user name of the remote management system 020 and the hash information received in step S1502.

The virtual machine IPMI process 053 returns a response (see FIG. 23) of “Get Session Challenge” to the remote management system 020 (step S1504). The response includes a randomly generated challenge string and a temporary session ID.

The remote management system 020 transmits a request for “Activate Session” (see FIG. 31) to the IPMI process 053 for virtual machines (step S1505). The remote management system 020 gives a character string obtained by concatenating the user name and password of the remote management system 020 and the challenge string received in step S1504 to the hash function specified by the authentication method (Authentication Type). The remote management system 020 transmits the hash value obtained from the hash function and the temporary session ID to the virtual machine IPMI process 053 as a request for “Activate Session”.

The virtual machine IPMI process 053 refers to the temporary session table 130 from the temporary session ID included in the request of “Activate Session”, identifies and concatenates the user name, password, and challenge string. The virtual machine IPMI process 053 generates a hash value by giving the concatenated character string to a hash function specified by an authentication method. The virtual machine IPMI process 053 authenticates the user when the hash value included in the received “Activate Session” request matches the generated hash value. If the user is authenticated, the virtual machine IPMI process 053 sends a response of “Activate Session” (see FIG. 34) to the remote management system 020 (step S1506). The response includes a new session ID. As a result, a session is established between the remote management system 020 and the virtual machine IPMI process 053.

Thereafter, the remote management system 020 transmits a request for “Chassis Control” (see FIG. 45 or FIG. 46) to the IPMI process 053 for virtual machines (step S1507). The virtual machine IPMI process 053 performs control according to the request, and returns a response (see FIG. 47) of “Chassis Control” to the remote management system 020 (step S1507).

<Processing Example of IPMI Process 053 for Virtual Machine>
Next, detailed processing and packets (IPMI messages) executed by each virtual machine IPMI process 053 started in the virtual machine IPMI process 053 start processing (step S1201) shown in FIG. This will be described with reference to FIG.

<Classification of IPMI messages>
FIG. 16 is a flowchart illustrating an example of an IPMI message classification processing procedure by the virtual machine IPMI process 053. When the virtual machine IPMI process 053 is activated, the virtual machine IPMI process 053 has session IDs 121 (serial numbers from “0”) corresponding to the maximum number of sessions that can be held in the own process, and the user name 122 and the password. A session table 120 having an entry for which 123 is empty and a temporary session table 130 for which the entry is empty are generated (step S1601).

Next, the virtual machine IPMI process 053 waits for arrival of a packet addressed to the IP address corresponding to the virtual machine number (step S1306) passed at the time of starting the process and addressed to the UDP port for the IPMI server ( Step S1602). If the packet does not arrive (step S1603: NO), the process returns to step S1602. On the other hand, when the packet arrives (step S1603: Yes), the virtual machine IPMI process 053 checks whether or not the session ID in the packet is “0” (step S1604).

If the session ID in the packet is “0” (step S1604: YES), the process proceeds to step S1201 in FIG. On the other hand, if it is not “0” (step S1604: No), the virtual machine IPMI process 053 determines whether the Authentication Type in the packet is an authentication method supported by the virtual machine IPMI process 053. (Step S1605). If not supported (step S1605: NO), the process proceeds to step S2401 in FIG.

On the other hand, if it is supported (step S1605: Yes), the IPMI process for virtual machine 053 means that the Network Function Code in the packet is “6h” that means Application request, and the command number means Activate Session. It is determined whether it is “3Ah” (step S1606). If “6h” and “3Ah” (step S1606: Yes), the process proceeds to step S2801 in FIG. If “6h” and not “3Ah” (step S1606: No), the process proceeds to step S3701 in FIG. This completes the classification of the IPMI message.

<Processing until session establishment by user authentication>
Next, processing and packets (IPMI messages) until the virtual machine IPMI process 053 and the remote management system 020 establish a session through user authentication will be described with reference to FIGS.

FIG. 17 is a flowchart (part 1) illustrating an example of a session establishment processing procedure by the virtual machine IPMI process 053. When the session ID of the packet received in step S1604 of FIG. 16 is “0” (step S1604: Yes), the virtual machine IPMI process 053 indicates that “Network Function Code in the received packet indicates“ application request ”“ 6h ”. ”And whether the command number is“ 38h ”meaning“ Get Channel Authentication Capability ”(step S1701).

If it is “6h” and “38h” (step S1701: Yes), the virtual machine IPMI process 053 generates a packet storing the following information (step S1702).

・ Network Function Code: 7h
・ Session ID: 0
・ Command number: 38h
-Completion Code: "0h" (normal termination of command)
-Bitmap indicating the supported Authentication Type

Then, the virtual machine IPMI process 053 returns the packet generated in step S1704 from the virtual machine IPMI process 053 which is the transmission destination to the remote management system 020 which is the transmission source of the received packet (step S1703). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

The processes in step S1701 and step S1702 are processes for transmitting and receiving IPMI session information before establishing an IPMI session. The packet that satisfies the condition of step S1701 and the packet that is generated and transmitted in step S1702 are shown below.

FIG. 18 is an explanatory diagram showing an example of a packet that satisfies the condition of step S1701. FIG. 19 is an explanatory diagram illustrating an example of the packet generated in step S1702. In FIG. 19, “Supported Authentication Type Bitmap” has a bit position corresponding to the number of “Authentication Type” supported by counting from the least significant bit in the predefined “Authentication Type” number. A value in which only “1” is set is stored.

Returning to FIG. 17, if “6h” and not “38h” (step S1701: No), the virtual machine IPMI process 053 is “6h” in which the Network Function Code in the received packet means Application request. In addition, it is determined whether or not the command number is “39h” which means “Get Session Challenge” (step S1704). If “6h” and “39h” (step S1704: YES), the process proceeds to step S2101 in FIG.

On the other hand, if “6h” and not “39h” (step S1704: No), the session ID is “0”, but the Network Function Code is not “6h”, or the Network Function Code is “6h”. This corresponds to the case where the command number is neither “38h” nor “39h”. In this case, the virtual machine IPMI process 053 generates a packet indicating an invalid command designation (step S1705). The generated packet including an invalid command specification includes the following information.

• Network Function Code: Value obtained by adding 1 to the value of Network Function Code of the received packet • Command number: Same value as the command number of the received packet • Session ID: Same value as the session ID of the received packet • Completion Code: “C1h” (invalid Command)

The virtual machine IPMI process 053 returns the packet generated in step S1705 from the virtual machine IPMI process 053, which is the transmission destination, to the remote management system 020, which is the transmission source of the received packet (step S1706). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 20 is an explanatory diagram showing an example of the packet generated in step S1705. Next, processing in the case of step S1704: Yes in FIG. 17 will be described.

FIG. 21 is a flowchart (part 2) illustrating an example of a session establishment processing procedure performed by the virtual machine IPMI process 053. Step S2101 in FIG. 21 is executed when a packet satisfying step S1704 in FIG. 17 is received (step S1704: Yes). In step S2101, the virtual machine IPMI process 053 determines whether or not the Authentication Type in the received packet specifies an authentication method supported by the virtual machine IPMI process 053 (step S2101). If not supported (step S2101: No), the process proceeds to step S2401 in FIG. On the other hand, if it is supported (step S2101: Yes), the virtual machine IPMI process 053 sets the first (first) entry of the user information table 051 as the target entry (step S2102), and It is determined whether or not the user name matches the user name of the target entry (step S2103).

If they match (step S2103: YES), the process proceeds to step S2601 in FIG. On the other hand, if they do not match (step S2103: NO), the virtual machine IPMI process 053 determines whether or not the current target entry is the last entry in the user information table 051 (step S2104). If it is not the last entry (step S2104: No), the virtual machine IPMI process 053 sets the next entry as the target entry (step S2105), and returns to step S2103.

In step S2104, if the current target entry is the last entry in the user information table 051 (step S2104: Yes), the user name specified in the received packet is invalid. Therefore, the virtual machine IPMI process 053 generates a packet storing the following information (step S2106).

・ Network Function Code: “7h”
・ Session ID: 0
Command number: “39h”
-Completion Code: "81h" (user name is invalid)

The virtual machine IPMI process 053 returns the packet generated in step S2106 from the virtual machine IPMI process 053 that is the transmission destination to the remote management system 020 that is the transmission source of the received packet (step S2107). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 22 is an explanatory diagram showing an example of a packet that satisfies the condition of step S2101. FIG. 23 is an explanatory diagram showing an example of the packet generated in step S2106. The packet shown in FIG. 23 is an IPMI message that returns a user name error.

FIG. 24 is a flowchart (part 3) illustrating an example of a session establishment processing procedure performed by the virtual machine IPMI process 053. In step S2401 of FIG. 24, in step S1605 of FIG. 16, the virtual machine IPMI process 053 does not have the authentication type supported by the virtual machine IPMI process 053 in the packet (step S1605: No). To be executed. In step S2401, the virtual machine IPMI process 053 generates a packet including the following information (step S2401).

-Network Function Code: Value obtained by adding 1 to the value of the Network Function Code of the received packet-Command number: Same value as the command number of the received packet-Session ID: Same value as the session ID of the received packet-Completion Code: "5h" (Support The command cannot be executed due to outside)

Then, the virtual machine IPMI process 053 returns the packet generated in step S2401 from the virtual machine IPMI process 053 which is the transmission destination to the remote management system 020 which is the transmission source of the received packet (step S2402). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 25 is an explanatory diagram showing an example of the packet generated in step S2401. The packet shown in FIG. 25 is an IPMI message that conveys that an unsupported command option or authentication method has been designated from the virtual machine IPMI process 053 to the remote management system 020 before the session is established.

FIG. 26 is a flowchart (part 4) illustrating an example of a session establishment processing procedure by the virtual machine IPMI process 053. Step S2601 in FIG. 26 is executed when the user name in the received packet exists in the target entry in step S2103 in FIG. 21 (step S2103: Yes).

In step S2601, the virtual machine IPMI process 053 randomly generates a temporary session ID (step S2601). Next, the virtual machine IPMI process 053 sets the first (first) entry of the temporary session table 130 as the target entry (step S2602), and whether the generated temporary session ID matches the session ID 131 of the target entry. It is determined whether or not (step S2603).

If they match (step S2603: YES), the process proceeds to step S2607. On the other hand, if they do not match (step S2603: NO), the virtual machine IPMI process 053 determines whether or not the current target entry is the last entry in the temporary session table 130 (step S2604). If it is not the last entry (step S2605: No), the virtual machine IPMI process 053 sets the next entry as the target entry (step S2605) and returns to step S2603.

In step S2604, when the current target entry is the last entry in the temporary session table 130 (step S2604: Yes), the virtual machine IPMI process 053 generates a challenge string which is a random character string, and the following information: Is registered as a new entry in the temporary session table 130 (step S2606), and the process proceeds to step S2609.

-Temporary session ID generated in step S2601
In the user name in the packet received in step S1603 In the user information table 051, the value of the password 112 corresponding to the user name 111 matched in step S2103 The challenge string generated

If they match in step S2603 (step S2603: Yes), the temporary session ID generated in step S2601 has been generated before and the temporary session ID is unused for session establishment. The IPMI process 053 generates a challenge string that is a random character string, overwrites and registers an entry including the following information in the target entry of the temporary session table 130 (step S2607), and proceeds to step S2608.

In the user name in the packet received in step S1603 In the user information table 051, the value of the password 112 corresponding to the user name 111 matched in step S2103 The challenge string generated

Thereafter, if there is a temporary session ID set in the timer function 041 of the management OS 040 in step S2609 described later, the virtual machine IPMI process 053 cancels the timer setting for the temporary session ID (step S2608). The process moves to S2609.

In step S2609, the virtual machine IPMI process 053 sets a timer so that the timer function 041 of the management OS 040 is notified to the temporary session ID after 60 seconds (step S2609). The reason for setting the timer is that if the temporary session ID registered at the time of setting the timer is not used, a timeout occurs after 60 seconds (step S2606), and the temporary session ID is released in the processing of FIGS. 53 and 54. It is.

Thereafter, the virtual machine IPMI process 053 generates a packet including the following information (step S2610).

・ Network Function Code: “7h” (Application Response)
・ Session ID: 0
Command number: “39h” (Get Session Challenge)
-Completion Code: "0h" (command normal termination)
-Temporary session ID generated in step S2601
Challenge string generated in step S2606 or step S2607

Then, the virtual machine IPMI process 053 returns the packet generated in step S2610 from the virtual machine IPMI process 053 which is the transmission destination to the remote management system 020 which is the transmission source of the received packet (step S2611). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

As described above, the processes of FIGS. 21, 24, and 26 support the authentication method, and if the user name is correct, the temporary session ID used for the session establishment request for performing user authentication, the challenge string for user authentication, And a process of returning an error packet if the authentication method is not supported or the user name is invalid.

FIG. 27 is an explanatory diagram showing an example of the packet generated in step S2610 of FIG. The packet shown in FIG. 27 is an IPMI message that returns a temporary session ID and a challenge string for user authentication.

In addition, the remote management system 020 after receiving the packet in step S2610 uses the password stored in advance in the remote management system 020 and the challenge string for authentication in the received packet, as an authentication code that is authentication information. Is generated. The Authentication Code combines the internal password of the remote management system 020, the temporary session ID extracted from the received packet, and the challenge string extracted from the received packet as a character string, and the remote management system 020 specifies the combined character string. This is a hash value generated by giving to a hash function that is an Authentication Type (authentication method). The remote management system 020 returns a packet including the temporary session ID extracted from the received packet and the generated hash value as an IPMI message indicating a session establishment request to the virtual machine IPMI process 053 in order to establish a session. It will be.

FIG. 28 is a flowchart (part 5) illustrating an example of a session establishment processing procedure by the virtual machine IPMI process 053. Step S2801 in FIG. 28 is the case where the network function code in the received packet is “6h” meaning Application request and the command number is “3Ah” meaning Activate Session in step S2805 in FIG. 16 (step S2801). (S2805: Yes). That is, step S2801 is executed when the received packet is an IPMI message indicating a session establishment request.

In step S2801, the virtual machine IPMI process 053 determines whether or not the temporary session table 130 is empty (step S2801). If it is empty (step S2801: YES), the process proceeds to step S2806. On the other hand, if it is not empty (step S2801: NO), the virtual machine IPMI process 053 sets the first (first) entry of the temporary session table 130 as the target entry (step S2802), and the temporary session in the received packet. It is determined whether or not the ID matches the session ID 131 of the target entry (step S2803).

If they match (step S2803: YES), the process proceeds to step S1702 in FIG. On the other hand, if they do not match (step S2603: NO), the virtual machine IPMI process 053 determines whether or not the current target entry is the last entry in the temporary session table 130 (step S2804). If it is not the last entry (step S2805: NO), the virtual machine IPMI process 053 sets the next entry as the target entry (step S2805), and returns to step S2803.

In step S2804, when the current target entry is the last entry in the temporary session table 130 (step S2804: Yes), the process proceeds to step S2806.

In step S2806, the virtual machine IPMI process 053 generates a packet including the following information (step S2806).

・ Network Function Code: “7h” (Application Response)
Session ID: Temporary session ID in the received packet
Command number: “3Ah” (Activate Session)
-Completion Code: “085” (session ID invalid)

Then, the virtual machine IPMI process 053 returns the packet generated in step S2806 from the virtual machine IPMI process 053, which is the transmission destination, to the remote management system 020, which is the transmission source of the received packet (step S2807). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 29 is an explanatory diagram showing an example of the packet generated in step S2806 of FIG. The packet shown in FIG. 29 is an IPMI message indicating that the temporary session ID is invalid because the session ID of the received packet from the remote management system 020 is invalid.

FIG. 30 is a flowchart (part 6) illustrating an example of a session establishment processing procedure by the virtual machine IPMI process 053. Step S3001 in FIG. 30 is executed when the temporary session ID in the received packet matches the session ID 131 of the target entry in step S2803 in FIG. 28 (step S2803: Yes).

In step S3001, the virtual machine IPMI process 053 generates a character string concatenating the values of the session ID 131, password 133, and challenge string 134 of the target entry of the temporary session table 130 set in step S2802 of FIG. The virtual machine IPMI process 053 generates the hash value of the character string by giving the generated character string to the hash function that is the Authentication Type (authentication method) in the received packet (step S3001).

Next, the virtual machine IPMI process 053 determines whether or not the generated hash value matches the Authentication Code in the received packet (step S3002). The Authentication Code combines the password held by the remote management system 020, the temporary session ID extracted from the received packet from the virtual machine IPMI process 053, and the challenge string extracted from the received packet as a character string. The hash value generated by giving the combined character string to a hash function which is an Authentication Type (authentication method) designated by the remote management system 020.

If they do not match (step S3002: No), this means that the authentication has failed, so the virtual machine IPMI process 053 generates a packet including the following information (step S3007).

・ Network Function Code: “7h” (Application Response)
Session ID: Temporary session ID in the received packet
Command number: “3Ah” (Activate Session)
-Completion Code: "CDh" (command invalid because authentication is invalid)

Then, the virtual machine IPMI process 053 returns the packet generated in step S3007 from the virtual machine IPMI process 053 which is the transmission destination to the remote management system 020 which is the transmission source of the received packet (step S3008). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

On the other hand, if they match in step S3002 (step S3002: Yes), the virtual machine IPMI process 053 sets the first (first) entry of the session table 120 as the target entry (step S3003), and the user of the target entry It is determined whether the name 122 is empty (step S3004). If the user name 122 is empty (step S3004: YES), it indicates that the session ID 121 of the target entry has not yet been used for session establishment, and the process proceeds to step S3301 in FIG.

On the other hand, when the user name 122 is not empty (step S3004: No), the session ID 121 of the target entry has already been established. The virtual machine IPMI process 053 determines whether or not the target entry is the last entry (step S3005). If it is not the last entry (step S3005: No), the virtual machine IPMI process 053 sets the next entry as the target entry (step S3006) and returns to step S3004. On the other hand, if it is the last entry (step S3005: Yes), the process proceeds to step S3501 in FIG.

FIG. 31 is an explanatory diagram showing an example of a packet that is a generation source of the hash value generated in step S3001 of FIG. The packet shown in FIG. 31 is an IPMI message indicating a session establishment request including authentication information (Authentication Type and Authentication Code).

FIG. 32 is an explanatory diagram showing an example of the packet generated in step S3007 of FIG. The packet shown in FIG. 32 is an IPMI message indicating authentication failure.

FIG. 33 is a flowchart (part 7) illustrating an example of a session establishment processing procedure by the virtual machine IPMI process 053. Step S3301 in FIG. 33 is executed when the user name 122 of the target entry is empty in step S3004 in FIG. 30 (step S3004: Yes). That is, it means that the session ID 121 of the target entry in the session table 120 is not used for session establishment.

In step S3301, the virtual machine IPMI process 053 adds the user name 132 of the target entry that matches the session ID in the received packet in the target entry of the temporary session table 130 to the target entry of the session table 120 in the process of step S2803. The value of the password 133 is registered (step S3301).

After registration, the virtual machine IPMI process 053 releases the timer setting for the temporary session ID in the received packet set in the timer function 041 of the management OS 040 (step S3302), and generates a packet including the following information (step S3302). S3303).

・ Network Function Code: “7h” Application Response
Session ID: Temporary session ID in the received packet
Command number: “3Ah” (Activate Session)
-Completion Code: "0h" (command normal termination)
New session ID: value of the session ID 121 of the entry in the session table 120 operated in step S3301. Authentication Type: Authentication Type in the received packet
Authentication Code: Combines the session ID 131, password 133, and challenge string 134 values of the target entry that match the session ID in the received packet in the temporary session table 130 as a character string, and the character string is the Authentication Type in the received packet. Hash value generated by giving to the hash function (authentication method)

Then, the virtual machine IPMI process 053 returns the packet generated in step S1804 from the virtual machine IPMI process 053 which is the transmission destination to the remote management system 020 which is the transmission source of the received packet (step S3304).

Since the temporary session ID, which is the session ID in the received packet, is not used later in the session, the virtual machine IPMI process 053 causes the value of the session ID 131 that matches the session ID in the received packet in the temporary session table 130 (temporary session ID). ) Is deleted (step S3305). The virtual machine IPMI process 053 sets the timer 006 so that the notification is received 60 seconds later to the session ID 121 in the target entry of the session table 120 by the timer function 041 of the management OS 040 (step S3306). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 34 is an explanatory diagram showing an example of the packet generated in step S3303 of FIG. The packet shown in FIG. 34 is a packet that returns a new session ID for officially establishing a session without any problem.

FIG. 35 is a flowchart (No. 8) showing an example of the session establishment processing procedure by the virtual machine IPMI process 053. Step S3501 in FIG. 35 is executed when the target entry is the last entry in step S3005 in FIG. 30 (step S3005: Yes). In other words, it indicates that a session ID that is not used for establishing a session does not exist in the session table 120. This situation means that there is no free session for establishing a session.

In step S3501, the virtual machine IPMI process 053 cancels the setting of the timer 006 for the temporary session ID in the received packet set by the timer function 041 of the management OS 040 (step S3501), and generates a packet including the following information: (Step S3502).

・ Network Function Code: “7h” (Application Response)
Session ID: Temporary session ID in the received packet
Command number: “3Ah” (Activate Session)
Completion Code: “81h” (no session ID available)
・ Authentication Type: Authentication Type in the received packet
Authentication Code: Combines the session ID 131, password 133, and challenge string 134 values of the target entry that match the session ID in the received packet in the temporary session table 130 as a character string, and the character string is the Authentication Type in the received packet. Hash value generated by giving to the hash function (authentication method)

Then, the virtual machine IPMI process 053 returns the packet generated in step S1804 from the virtual machine IPMI process 053 which is the transmission destination to the remote management system 020 which is the transmission source of the received packet (step S3503).

Since the temporary session ID, which is the session ID in the received packet, is not used later in the session, the virtual machine IPMI process 053 causes the value of the session ID 131 that matches the session ID in the received packet in the temporary session table 130 (temporary session ID). ) Is deleted (step S3504). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 36 is an explanatory diagram showing an example of the packet generated in step S3502 of FIG. The packet shown in FIG. 36 is a packet indicating that a session ID for officially establishing a session is insufficient.

As described above, in FIGS. 28 to 36, when a session establishment request packet based on authentication information arrives from the remote management system 020 to the virtual machine IPMI process 053, the session ID in the packet is temporarily assigned. When the packet ID matches, the authentication of the packet is successful, and the session ID of the session to be officially established is free, the virtual machine IPMI process 053 sends a packet including a new session ID for formal session establishment. (FIG. 34) is returned. If the session ID in the received packet is invalid (FIG. 29), if authentication fails (FIG. 32), or if there is no available session ID (FIG. 36), the virtual machine IPMI process 053 Performs processing to return an error.

When the authentication is successful and the session is established, the remote management system 020 uses the new session ID received from the virtual machine IPMI process 053 to transmit the packet including the packet authentication information and the command execution request to the virtual machine IPMI process. 053.

The authentication information of this packet includes the authentication type specified by the remote management system 020, the password corresponding to the user name authenticated at the time of session establishment, the new session ID received from the virtual machine IPMI process 053, and the received packet. Is a hash value (Authentication Code) generated by combining the partial information with a hash function that is an Authentication Type specified by the remote management system 020.

In addition, the partial information of the received packet is information obtained by combining the network function code, the command number, and the chassis control as a character string when the packet is an IPMI message indicating a startup request or a power-off request. When the packet is an IPMI message indicating a session disconnection request, it is information obtained by combining a network function code and a command number as a character string. Thus, the process up to session establishment by user authentication is completed.

<Authentication data verification processing for packets after session establishment>
Next, an authentication data verification process for a packet after session establishment will be described with reference to FIGS.

FIG. 37 is a flowchart (part 1) illustrating an example of the authentication data verification processing procedure by the virtual machine IPMI process 053. Step S3701 in FIG. 37 is executed when the network function code and the command number in the received packet are “6h” and not “3Ah” in step S1606 in FIG. 16 (step S1606: No).

In step S3701, the virtual machine IPMI process 053 sets the first (first) entry of the session table 120 as the target entry (step S3701), and the session ID in the received packet matches the session ID of the target entry. It is determined whether or not to perform (step S3702).

If they match (step S3702: YES), the process proceeds to step S3801 in FIG. On the other hand, if they do not match (step S3702: NO), the virtual machine IPMI process 053 determines whether or not the current target entry in the session table 120 is the last entry (step S3703). If it is not the last entry (step S3703: NO), the virtual machine IPMI process 053 sets the next entry as the target entry (step S2105), and returns to step S3702. On the other hand, if it is the last entry (step S3703: YES), it means that no entry with the matching session ID was found from the session table 120, and the process proceeds to step S4001 in FIG.

FIG. 38 is a flowchart (part 2) of the authentication data verification processing procedure example by the virtual machine IPMI process 053. Step S3801 in FIG. 38 is executed when the session IDs match in step S3702 in FIG. 37 (step S3702: Yes).

In step S3801, the virtual machine IPMI process 053 sets the first (first) entry of the user information table 051 as a target entry (step S3801), and the user name 122 in the target entry of the session table 120 and step S3801. It is determined whether or not the user name 111 in the target entry of the user information table 051 set in step S1 matches (step S3802).

If they match (step S3802: YES), the process proceeds to step S2302 in FIG. On the other hand, if they do not match (step S3802: No), the virtual machine IPMI process 053 determines whether or not the current target entry of the user information table 051 is the last entry (step S3803). If it is not the last entry (step S3803: NO), the virtual machine IPMI process 053 sets the next entry as the target entry (step S3804), and returns to step S3802. On the other hand, if it is the last entry (step S3803: YES), the entry having the same user name is not found from the user information table 051, and the process proceeds to step S4001 in FIG.

FIG. 39 is a flowchart (part 3) illustrating an example of the authentication data verification processing procedure by the virtual machine IPMI process 053. Step S3901 in FIG. 39 is executed when the user names match in step S3802 in FIG. 38 (step S3802: Yes).

The virtual machine IPMI process 053 is a character string obtained by combining the hash ID, which is the authentication type authentication method in the received packet, with the session ID 121 of the target entry of the session table 120, the password 123, and some information of the received packet. To generate a hash value (step S3901). The partial information of the received packet is a character string obtained by combining the network function code and the command number in the received packet. However, when the received packet has a chassis control, a character string in which the network function code, the command number, and the chassis control in the received packet are combined is used instead of the character string.

The virtual machine IPMI process 053 determines whether or not the generated hash value matches the Authentication Code in the received packet (step S3902). If they do not match (step S3902: NO), the process proceeds to step S4001 in FIG. On the other hand, if they match (step S3902: Yes), whether or not the Network Function Code in the received packet is “0h” meaning the Chassis Request, and the command number is “2h” meaning the Chassis Control. Is determined (step S3903).

If it is “0h” and “2h” (step S3903: YES), the process proceeds to step S4401 in FIG. On the other hand, if it is not “0h” and “2h” (step S3903: No), the IPMI process for virtual machine 053 has “6h” in which the Network Function Code in the received packet means “Application Request” and the command number is “6h”. It is determined whether or not “3Ch” which is the meaning of the Close Session (step S3904). When it is “6h” and “3Ch” (step S3904: Yes), the process proceeds to step S5001 in FIG. On the other hand, if it is not “6h” and “3Ch” (step S3904: No), the process proceeds to step S4201 in FIG.

FIG. 40 is a flowchart (part 4) illustrating an example of the authentication data verification processing procedure performed by the virtual machine IPMI process 053. Step S4001 in FIG. 40 is executed when any of the following applies.

When the session ID of the received packet does not exist in the session table 120 in step S3703 of FIG. 37, that is, when the session ID of the received packet is invalid (step S3703: Yes).
If the user name in the session table 120 does not exist in the user information table 051 in step S3803 in FIG. 38, that is, if the authenticated user name is invalid (step S3803: Yes).
When authentication fails in step S3902 of FIG. 39 (step S3902: No)

In step S4001, the virtual machine IPMI process 053 generates a packet including the following information (step S4001).

-Network Function Code: Value obtained by adding 1 to the value of Network Function Code in the received packet-Command number: Same value as received packet-Session ID: Same value as received packet-Completion Code: "CDh" (command is invalid)

Then, the virtual machine IPMI process 053 returns the packet generated in step S4001 from the virtual machine IPMI process 053 which is the transmission destination to the remote management system 020 which is the transmission source of the received packet (step S4002). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 41 is an explanatory diagram showing an example of the packet generated in step S4001 of FIG. The packet shown in FIG. 41 is an IPMI message that conveys that user authentication has failed from the virtual machine IPMI process 053 to the remote management system 020 after the session is established.

FIG. 42 is a flowchart (part 5) illustrating an example of the authentication data verification processing procedure performed by the virtual machine IPMI process 053. Step S4201 of FIG. 42 is executed when it is not “6h” and “3Ch” in Step S3904 of FIG. 39 (Step S3904: No). That is, FIG. 42 shows an example of error processing by the virtual machine IPMI process 053.

In step S4201, the virtual machine IPMI process 053 generates a packet including the following information (step S4201).

• Network Function Code: Value obtained by adding 1 to the value of Network Function Code of the received packet • Command number: Same value as the received packet • Session ID: Same value as the received packet • Completion Code: “C1h” (invalid command)
・ Authentication Type: Authentication Type in the received packet
Authentication Code: Session ID, password, and partial information of the received packet in the session ID entry matched in step S3702 of FIG. 37 in the session table 120 are added to the hash function that is the authentication method of Authentication Type in the received packet. A hash value generated by giving the combined string

The partial information of the received packet is a character string obtained by combining the network function code and the command number.

Then, the virtual machine IPMI process 053 returns the packet generated in step S4201 from the virtual machine IPMI process 053, which is the transmission destination, to the remote management system 020, which is the transmission source of the received packet (step S4202). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 43 is an explanatory diagram showing an example of the packet generated in step S4201 of FIG. The packet shown in FIG. 43 is an IPMI message that conveys that the command number is invalid from the virtual machine IPMI process 053 to the remote management system 020 after the session is established. Thus, the authentication data verification process for the packet after the session is established is completed.

<Virtual machine startup processing>
Next, a virtual machine activation process for activating the virtual machine 06 with the same IPMI as that of the physical machine 001 will be described with reference to FIGS.

FIG. 44 is a flowchart (part 1) illustrating an example of a virtual machine power supply operation request processing procedure by the virtual machine IPMI process 053. Step S4401 of FIG. 44 is executed when the network function code “0h” in the received packet and the command number are “2h” in step S3903 of FIG. That is, step S4401 is executed when the received packet is an IPMI message indicating a power operation request.

In step S4401, the virtual machine IPMI process 053 determines whether or not the Chassis Control in the received packet is “0” indicating Power down (step S4401). When it is “0” (step S4401: YES), the virtual machine IPMI process 053 uses the hypervisor operation I / F 042 of the management OS 040 to match the virtual machine number that was passed when the process was generated. Is blocked by the hypervisor 030 (step S4402), and the process proceeds to step S4405.

On the other hand, if it is not “0” (step S4401: No), the virtual machine IPMI process 053 determines whether or not the Chassis Control in the received packet is “1” meaning “Power up” (step S4403). If it is not “1” (step S4403: NO), the process proceeds to step S2702 in FIG.

On the other hand, if it is “1” (step S4403: Yes), the virtual machine IPMI process 053 matches the virtual machine number passed when the own process was generated using the hypervisor operation I / F 042 of the management OS 040. The virtual machine is activated by the hypervisor 030 (step S4404), and the process proceeds to step S4405.

In step S4405, the virtual machine IPMI process 053 cancels the timer setting in the session ID in the received packet set by the timer function 041 of the management OS 040, and sets the timer so that notification is sent to the session ID again after 60 seconds. Setting is performed (step S4405).

Thereafter, the virtual machine IPMI process 053 generates a packet including the following information (step S4406).

・ Network Function Code: “1h” (Chassis Response)
-Session ID: Equivalent to received packet-Command number: "2h" (Chassis Control)
-Completion Code: "0h" (normal termination of command)
・ Authentication Type: Authentication Type in the received packet
Authentication Code: Combined with the hash function that is the authentication method of Authentication Type in the received packet, the session ID, password, and partial information of the received packet in the session ID entry found in step S3702 in the session table 120 Hash value generated by giving a string

The partial information of the received packet is a character string obtained by combining the network function code, the command number, and the chassis control.

Then, the virtual machine IPMI process 053 returns the packet generated in step S4406 from the virtual machine IPMI process 053 which is the transmission destination to the remote management system 020 which is the transmission source of the received packet (step S4407). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

44, the remote management system 020 can start and block the virtual machine 06 by IPMI without being aware of the existence of the hypervisor 030.

FIG. 45 is an explanatory diagram showing an example of a received packet that triggers execution of step S4401 in FIG. The packet shown in FIG. 45 is an IPMI message indicating a blocking request sent from the remote management system 020 to the virtual machine IPMI process 053. That is, since the packet shown in FIG. 45 is “0” indicating that the Chassis Control is “Power down”, Step S4402 is executed.

FIG. 46 is an explanatory diagram showing an example of a received packet that triggers execution of step S4403 in FIG. The packet shown in FIG. 46 is an IPMI message indicating an activation request sent from the remote management system 020 to the virtual machine IPMI process 053. Since the packet shown in FIG. 45 is “1” indicating that the Chassis Control is “Power up”, Step S4404 is executed.

FIG. 47 is an explanatory diagram showing an example of the packet generated in step S4406 of FIG. The packet shown in FIG. 47 is an IPMI message that returns from the virtual machine IPMI process 053 to the remote management system 020 that the virtual machine has been successfully shut down or started.

FIG. 48 is a flowchart (part 2) illustrating an example of a virtual machine power supply operation request processing procedure in the virtual machine IPMI process 053. Step S4801 of FIG. 48 is executed when the Chassis Control in the received packet is neither “0” nor “1” in Step S4403 of FIG. 44 (Step S4403: No). That is, the received packet in this case is an IPMI message that is not supported.

In step S4801, the virtual machine IPMI process 053 generates a packet including the following information (step S4801).

・ Network Function Code: “1h” (Chassis Response)
-Session ID: Equivalent to received packet-Command number: "2h" (Chassis Control)
-Completion Code: "D5h" (command cannot be executed due to specification of unsupported command information)
・ Authentication Type: Authentication Type in the received packet
Authentication Code: Generated by giving a character string that combines the password, session ID, and partial packet information in the entry of the session table 120 found in step S3702 to the hash function that is the authentication method of Authentication Type in the received packet. Hash value

Then, the virtual machine IPMI process 053 returns the packet generated in step S4801 from the virtual machine IPMI process 053 which is the transmission destination to the remote management system 020 which is the transmission source of the received packet (step S4802). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 49 is an explanatory diagram showing an example of the packet generated in step S4801 of FIG. In the packet shown in FIG. 49, an unsupported command option or authentication method is designated from the virtual machine IPMI process 053 to the remote management system 020 after the session is established (the value of the Chassis Control in the received packet is not supported). Is an IPMI message that conveys. Thus, the virtual machine activation process is completed.

<Session blocking request processing>
Next, session blocking request processing will be described with reference to FIGS.

FIG. 50 is a flowchart illustrating an example of a session cutoff request processing procedure performed by the virtual machine IPMI process 053. Step S5001 in FIG. 50 is processing executed when the network function code in the received packet is “6h” and the command number is “3Ch” in step S3904 in FIG. 39 (step S3904: Yes). is there. That is, the received packet in this case is an IPMI message indicating a session cutoff request.

The virtual machine IPMI process 053 cancels the setting of the timer 006 in the session ID in the received packet set by the timer function 041 of the management OS 040 (step S5001). Next, the virtual machine IPMI process 053 empties items other than the session ID 121 in the entry of the session table 120 that matches the session ID in the received packet found in step S3702 of FIG. 37 (step S5002).

Then, the virtual machine IPMI process 053 generates a packet including the following information (step S5003).

・ Network Function Code: “7h” (Application Response)
Session ID: Session ID of the received packet (IPMI message indicating a session cutoff request)
Command number: “3Ch” (Close Session)
-Completion Code; "0h" (command normal termination)
・ Authentication Type: Authentication Type in the received packet
Authentication Code: By giving the hash function, which is the authentication method of Authentication Type in the received packet, a character string that combines the password, session ID, and partial information of the received packet in the entry of the session table 120 found in step S3702 The generated hash value

Then, the virtual machine IPMI process 053 returns the packet generated in step S4801 from the virtual machine IPMI process 053 which is the transmission destination to the remote management system 020 which is the transmission source of the received packet (step S4805). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 51 is an explanatory diagram showing an example of a packet indicating a session cutoff request. FIG. 52 is an explanatory diagram showing an example of the packet generated in step S5003 of FIG. The packet shown in FIG. 52 is a response IPMI message in which the session has been normally blocked. Thus, the session cutoff request process is completed.

<Session blocking process>
Next, a session blocking process after detecting a connection timeout will be described with reference to FIGS.

FIG. 53 is a flowchart (part 1) illustrating an example of a session blocking process procedure by the virtual machine IPMI process 053. Step S5301 of FIG. 53 is executed when the virtual machine IPMI process 053 interrupts the current processing when the notification is received by the timer function 041 of the management OS 040 (connection timeout detection). Is done.

The virtual machine IPMI process 053 sets the first (first) entry of the temporary session table 130 as a target entry (step S5301). Next, the virtual machine IPMI process 053 determines whether or not the session ID 131 in the target entry matches the temporary session ID notified by the timer (step S5302).

If they do not match (step S5302: NO), the virtual machine IPMI process 053 determines whether or not the current target entry is the last entry (step S5303). If it is not the last entry (step S5303: NO), the virtual machine IPMI process 053 sets the next entry as the target entry (step S5304) and returns to step S5302. On the other hand, if it is the last entry (step S5303: YES), the process proceeds to step S5401 in FIG.

In step S5302, if the session ID 131 in the target entry matches the temporary session ID notified by the timer (step S5302: Yes), the virtual machine IPMI process 053 generates the temporary session ID notified by the timer. It is determined whether or not the original received packet is being processed (step S5305).

If it is being processed (step S5305: Yes), the process proceeds to step S5306. If it is not being processed (step S5305: No), the process proceeds to step S5308.

In step S5306, the virtual machine IPMI process 053 generates a packet including the following information (step S5306).

-Network Function Code: Value of Network Function Code of received packet plus 1-Command number: Equivalent to received packet-Session ID: Equivalent to received packet-Completion Code: "C3h" (session timeout)

Then, the virtual machine IPMI process 053 returns the packet generated in step S5306 from the virtual machine IPMI process 053, which is the transmission destination, to the remote management system 020, which is the transmission source of the received packet (step S5307).

In step S5308, the virtual machine IPMI process 053 deletes the target entry in the temporary session table 130 found in step S5302 (step S5308). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 54 is a flowchart (part 2) illustrating an example of a session cutoff processing procedure by the virtual machine IPMI process 053. Step S5401 of FIG. 54 is executed when it is the last entry (step S5303: Yes), that is, when the session ID of the timer notification is not in the temporary session table 130.

The virtual machine IPMI process 053 sets the first (first) entry of the session table 120 as a target entry (step S5401). Next, the virtual machine IPMI process 053 determines whether or not the session ID 121 in the target entry matches the temporary session ID notified by the timer (step S5402).

If they do not match (step S5402: NO), the virtual machine IPMI process 053 determines whether or not the current target entry is the last entry (step S5403). If it is not the last entry (step S5403: NO), the virtual machine IPMI process 053 sets the next entry as the target entry (step S5404) and returns to step S5402. On the other hand, if it is the last entry (step S5403: YES), the process returns to step S1602 in FIG.

On the other hand, when the session ID 121 in the target entry matches the temporary session ID notified by the timer in step S5402 (step S5402: Yes), the virtual machine IPMI process 053 determines the session ID notified by the timer function 041. It is determined whether or not the received packet that is the generation source is being processed (step S5405).

If it is being processed (step S5405: Yes), the process proceeds to step S5406. If it is not being processed (step S5405: No), the process proceeds to step S5408.

In step S5406, the virtual machine IPMI process 053 generates a packet including the following information (step S5406).

Then, the virtual machine IPMI process 053 returns the packet generated in step S5406 to the remote management system 020 that is the transmission source of the received packet from the virtual machine IPMI process 053 that is the transmission destination (step S5407).

In step S5408, the virtual machine IPMI process 053 deletes the target entry in the temporary session table 130 found in step S5302 (step S5408). Thereafter, the process returns to step S1602 in FIG. 16 to wait for a packet again.

FIG. 55 is an explanatory diagram showing an example of packets generated in step S5306 in FIG. 53 and step S5406 in FIG. The packet shown in FIG. 55 is an IPMI message for transmitting that the session has timed out from the virtual machine IPMI process 053 to the remote management system 020. Thus, the session blocking process is completed.

<End processing>
Next, with reference to FIG. 56 and FIG. 57, a termination process when a shutdown signal is received from the IPMI server application 050 will be described.

FIG. 56 is a flowchart (No. 1) illustrating an example of a termination process procedure of the virtual machine IPMI process 053. The termination process is a process executed when a shutdown signal is sent from the IPMI server application 050 to the virtual machine IPMI process 053. Immediately after receiving the shutdown, the virtual machine IPMI process 053 interrupts the current processing and executes step S5601.

The virtual machine IPMI process 053 sets the first (first) entry of the temporary session table 130 as a target entry (step S5601). The virtual machine IPMI process 053 cancels the setting of the timer 006 in the session ID in the received packet set by the timer function 041 of the management OS 040 (step S5602).

The virtual machine IPMI process 053 then cancels the session ID timer setting and deletes the entry for each entry in the temporary session table 130 (step S5603). The virtual machine IPMI process 053 determines whether or not the current entry is the last entry (step S5604). If it is not the last entry (step S5604: NO), the virtual machine IPMI process 053 sets the next entry as the target entry (step 5605), and returns to step S5602. On the other hand, if it is the last entry (step S5604: YES), the process proceeds to step S5701 in FIG.

FIG. 57 is a flowchart (part 2) illustrating an example of a termination process procedure of the virtual machine IPMI process 053. The virtual machine IPMI process 053 sets the first (first) entry of the session table 120 as the target entry (step S5701). The virtual machine IPMI process 053 determines whether or not the user name 122 in the target entry is empty (step S5702).

If the user name 122 is not empty (step S5702: NO), the virtual machine IPMI process 053 cancels the setting of the timer 006 in the session ID in the received packet set by the timer function 041 of the management OS 040 (step S5705). . Then, the virtual machine IPMI process 053 cancels the session ID timer setting and deletes the entry for all entries in the temporary session table 130 (step S5706), and proceeds to step S5703.

On the other hand, if the user name 122 is empty (step S5702: YES), the virtual machine IPMI process 053 determines whether or not the current entry is the last entry (step S5703). If it is not the last entry (step S5703: No), the virtual machine IPMI process 053 sets the next entry as the target entry (step S5704), and returns to step S3603. On the other hand, if it is the last entry (step S5703: YES), the virtual machine IPMI process 053 ends.

Through the above processing, the remote management system 020 can realize activation and shutdown of the corresponding virtual machine 06 with the IP address of the virtual machine IPMI process 053 without directly requesting the hypervisor 030 to perform processing. Accordingly, the remote management system 020 and the user can start and shut down the power operation target machine without being aware of whether the power operation target machine is the physical machine 001 or the virtual machine 06. The convenience of operation can be improved. Further, by generating the virtual machine IPMI process 053 for each virtual machine 06, the virtual machine IPMI process 053 corresponding to the power operation target machine takes charge of the power operation. Therefore, it is not necessary to access an unstarted or started virtual machine 06 that is a non-power source operation target machine, and therefore, the processing load can be reduced.

The present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the scope of the appended claims. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and the present invention is not necessarily limited to those having all the configurations described. A part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Moreover, you may add the structure of another Example to the structure of a certain Example. Moreover, you may add, delete, or replace another structure about a part of structure of each Example.

In addition, each of the above-described configurations, functions, processing units, processing means, etc. may be realized in hardware by designing a part or all of them, for example, with an integrated circuit, and the processor realizes each function. It may be realized by software by interpreting and executing the program to be executed.

Information such as programs, tables, and files that realize each function can be stored in a storage device such as a memory, a hard disk, and an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, and a DVD.

Also, the control lines and information lines indicate what is considered necessary for the explanation, and do not necessarily indicate all control lines and information lines necessary for mounting. In practice, it can be considered that almost all the components are connected to each other.

Claims

A computer on which a virtual machine operates,
The computer includes a storage device that stores a virtualization program that controls the virtual computer, a processor that executes the virtualization program, and an interface that transmits and receives data.
The processor is
An acquisition process for acquiring a first message including destination information of either the computer or the virtual computer and the power operation content for the destination specified by the destination information from the interface;
When the destination information included in the first message acquired by the acquisition process is not the destination information of the computer, the virtual computer executes the process according to the power operation details by controlling the virtualization program Control processing to
A computer characterized by executing.
The processor is
If the destination information included in the first message is the destination information of the computer, start the computer, and execute a generation process for generating a control process for controlling the virtual computer,
In the acquisition process, the processor acquires a second message including destination information of either the computer or the virtual machine and a power operation content for a destination specified by the destination information;
In the control process, when the destination information included in the second message acquired by the acquisition process is not the destination information of the computer, the processor controls the virtualization program by the control process, and The computer according to claim 1, wherein the virtual computer executes processing according to the power operation content.
The storage device stores destination correspondence information for storing destination information for each virtual machine,
In the generation process, the processor generates the control process for each virtual machine,
In the control process, when the destination information included in the second message is not destination information of the computer, the processor refers to the destination correspondence information and searches for a specific virtual machine corresponding to the destination information. 3. The virtualization program is controlled by a specific control process corresponding to the specific virtual machine, and the specific virtual machine executes processing according to the power operation content. Listed calculator.
In the control process, the processor executes the process of starting the virtual machine by controlling the virtualization program when the power operation content is a content for instructing activation of the destination. The computer according to any one of claims 1 to 3.
In the control process, the processor executes the process of controlling the virtualization program and shutting down the virtual computer when the power operation content is a content for instructing shutdown of the destination. The computer according to any one of claims 1 to 3.
A control method by a physical computer on which a virtual computer operates,
The physical computer includes a storage device that stores a virtualization program that controls the virtual computer, a processor that executes the virtualization program, and an interface that transmits and receives data.
The control method is:
The processor is
An acquisition process for acquiring a message including the destination information of either the physical computer or the virtual machine and the power operation content for the destination specified by the destination information from the interface;
Control in which when the destination information included in the message acquired by the acquisition process is not the destination information of the physical computer, the virtual computer executes the process according to the power operation content by controlling the virtualization program Processing,
The control method characterized by performing.
The processor is
When the destination information included in the first message is the destination information of the physical computer, start the physical computer and execute a generation process for generating a control process for controlling the virtual computer,
In the acquisition process, the processor acquires a second message including destination information of either the physical computer or the virtual computer and a power operation content for a destination specified by the destination information;
In the control process, when the destination information included in the second message acquired by the acquisition process is not destination information of the physical computer, the processor controls the virtualization program by the control process, The control method according to claim 6, wherein the virtual computer executes processing according to the power operation content.
The storage device stores destination correspondence information for storing destination information for each virtual machine,
In the generation process, the processor generates the control process for each virtual machine,
In the control process, when the destination information included in the second message is not the destination information of the physical computer, the processor refers to the destination correspondence information and selects a specific virtual computer corresponding to the destination information. 8. The search is performed, the virtualization program is controlled by a specific control process corresponding to the specific virtual machine, and the specific virtual machine executes a process according to the power operation content. The control method described in 1.
In the control process, the processor executes the process of starting the virtual machine by controlling the virtualization program when the power operation content is a content for instructing activation of the destination. The control method according to any one of claims 6 to 8.
In the control process, the processor executes the process of controlling the virtualization program and shutting down the virtual computer when the power operation content is a content for instructing shutdown of the destination. The control method according to any one of claims 6 to 8.
A control program for causing a processor to control a virtual computer and a physical computer on which the virtual computer operates,
The physical computer includes a storage device that stores a virtualization program that controls the virtual computer, and an interface that transmits and receives data.
In the processor,
An acquisition process for acquiring a message including the destination information of either the physical computer or the virtual machine and the power operation content for the destination specified by the destination information from the interface;
Control in which when the destination information included in the message acquired by the acquisition process is not the destination information of the physical computer, the virtual computer executes the process according to the power operation content by controlling the virtualization program Processing,
A control program characterized by causing
In the processor,
When the destination information included in the first message is the destination information of the physical computer, the physical computer is started, and a generation process for generating a control process for controlling the virtual computer is executed.
In the acquisition process, the processor is caused to acquire a second message including destination information of either the physical computer or the virtual machine and a power operation content for a destination specified by the destination information,
In the control process, if the destination information included in the second message acquired by the acquisition process is not the destination information of the physical computer, the control process controls the virtualization program to the processor, The control program according to claim 11, wherein the virtual computer executes processing according to the power operation content.
The storage device stores destination correspondence information for storing destination information for each virtual machine,
In the generation process, the processor is caused to generate the control process for each virtual machine,
In the control process, when the destination information included in the second message is not the destination information of the physical computer, the control unit refers to the destination correspondence information and determines a specific virtual machine corresponding to the destination information. 13. The search is performed, and the virtualization program is controlled by a specific control process corresponding to the specific virtual machine, and the specific virtual machine executes processing corresponding to the power operation content. The control program described in 1.
The control process causes the processor to execute the process of starting the virtual machine by controlling the virtualization program when the power operation contents are contents for instructing activation of the destination. The control program according to any one of claims 11 to 13.
The control process causes the processor to execute a process of controlling the virtualization program to shut down the virtual machine when the power operation content is a content for instructing shutdown of the destination. The control program according to any one of claims 11 to 13.