Abstract:
When a failure occurs in an LPAR on a physical computer under an SAN environment, a destination LPAR is set in another physical computer to enable migrating of the LPAR and setting change of a security function on the RAID apparatus side is not necessary. When a failure occurs in an LPAR generated on a physical computer under an SAN environment, configuration information including a unique ID (WWN) of the LPAR where the failure occurs is read, a destination LPAR is generated on another physical computer, and the read configuration information of the LPAR is set to the destination LPAR, thereby enabling migrating of the LPAR when the failure occurs, under the control of a management server.

Description:
CROSS-REFERENCES 
       [0001]    This application is a continuation application of U.S. Ser. No. 12/129,294, filed May 29, 2008, the entire disclosure of which is hereby incorporated by reference. 
     
    
     BACKGROUND OF THE INVENTION 
       [0002]    The present invention relates to a virtual computer system, and particularly to a virtual computer system and a control method of migrating a logical partition by which, when a failure occurs in the logical partition on a physical computer, a substitute for the logical partition is generated on another physical computer to migrate a process of the logical partition. 
         [0003]    There has been put to practical use a virtual computer system in which plural logical computers or logical partitions (hereinafter, referred to as LPARs) are established on a physical computer and OSs (operating systems) are allowed to operate on the respective logical computers, thereby allowing the unique OSs to operate on the plural logical computers. Further, as a recent example of the virtual computer system, the virtual computer system in which a logical FC (Fibre Channel) extension board or a logical FC port is mounted to each virtual computer is used under an SAN (Storage Area Network) environment including an RAID (Redundant Array of Inexpensive Disks) apparatus. 
         [0004]    In the computer system to realize booting under the SAN environment, in order to protect data of logical units in the RAID apparatus in which OSs are installed, a security function by which an access is permitted only from the respective computers is realized by the RAID apparatus. The security function generally utilizes a method in which, by using unique IDs (World Wide Names) assigned to the FC ports mounted on the respective computers, the logical units having the OSs installed are associated with the unique IDs (World Wide Names) assigned to the FC ports provided for the computers and an access is permitted only from the FC ports having the IDs (World Wide Names). Further, the IDs (World Wide Names) unique to the apparatuses are recorded in software including OSs in some cases. 
         [0005]    In a redundant configuration of the computer system to perform booting from the SAN, the unique IDs (World Wide Names) assigned to the FC ports are different depending on an actually-used computer and a standby computer. Accordingly, when the actually-used computer is migrated to the standby computer, a software image including an OS cannot be used as it is, and it is necessary to change setting of the security function on the RAID apparatus side by SAN management software or a system administrator. The setting change is required not only between the physical computers such as the actually-used computer and the standby computer, but also between the LPARs in the virtual computer system. Specifically, even when plural LPARs are allowed to operate on the physical computers in the virtual computer system and an actually-used LPAR is migrated to a standby LPAR, it is necessary to change the setting of the security function on the RAID apparatus side due to difference of the unique IDs (World Wide Names) assigned to the logical FC ports of the respective LPARs. 
         [0006]    For example, JP-A 2005-327279 and H10-283210 disclose a technique in which, in a virtual computer system where LPARs can be established on plural physical computers, configuration information of the LPAR is migrated from the LPAR of one physical computer to another physical computer to take over its operation. 
       SUMMARY OF THE INVENTION 
       [0007]    JP-A 2005-327279 and H10-283210 do not disclose migrating of the LPAR by which when a failure occurs in the LPAR of the physical computer, another LPAR generated in another physical computer is used as a standby LPAR. 
         [0008]    Further, JP-A 2005-327279 and H10-283210 do not disclose taking over of the unique ID (World Wide Name) assigned to the logical FC port of the LPAR because the setting change of the security function on the RAID apparatus side is unnecessary when one LPAR is migrated to another in the virtual computer system under the SAN environment. 
         [0009]    An object of the present invention is to provide a virtual computer system in which when a failure occurs in an LPAR on a physical computer under an SAN environment, a destination LPAR is set in another physical computer to enable migrating of the LPAR without necessity of setting change of a security function on the RAID apparatus side. 
         [0010]    According to the present invention, there is preferably provided a virtual computer system having plural physical computers including first and second physical computers and a management apparatus that is connected to the plural physical computers via a network to manage the physical computers and logical partitions, and allows OSs to operate by generating the logical partitions on the physical computers, wherein the first physical computer includes: failure detection means for detecting that a failure occurs in the first physical computer or a first logical partition formed in the first physical computer; and first management means for managing hardware configuration information of the first physical computer and unique configuration information assigned to the first logical partition, the management apparatus includes: means for accepting notification of the failure occurrence from the failure detection means to receive the hardware configuration information and the unique configuration information from the first management means; and means for determining the substitute second physical computer to transmit the hardware configuration information and the unique configuration information to the second physical computer, and the second physical computer includes: means for receiving the hardware configuration information and the unique configuration information transmitted from the management apparatus; means for determining whether or not a second logical partition can be generated on the second physical computer on the basis of the hardware configuration information and the unique configuration information; and means for generating the second logical partition on the basis of the unique configuration information when the determination means determines that the second logical partition can be generated. 
         [0011]    According to the present invention, when a failure occurs in the LPAR on the physical computer under the SAN environment, the destination LPAR is set in another physical computer so as to enable migrating of the LPAR without necessity of setting change of the security function on the RAID apparatus side. Further, configuration information and the like of the original LPAR are migrated to the destination LPAR under the control of the management server, so that even when a failure occurs in the original physical computer, migrating of the LPAR can be realized. 
     
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         [0012]      FIG. 1  is a view showing a configuration of a computer system according to an embodiment; 
           [0013]      FIG. 2  is a flowchart showing a process performed when a failure occurs; 
           [0014]      FIG. 3  is a flowchart showing a process performed when a failure occurs; 
           [0015]      FIG. 4  is a flowchart showing a process performed by a management server when a failure occurs; 
           [0016]      FIG. 5  is a flowchart showing a process performed by the management server when a failure occurs; 
           [0017]      FIG. 6  is a flowchart showing a process performed by a hypervisor when a failure occurs; 
           [0018]      FIG. 7  is a flowchart showing a process of a command in a Hypervisor-Agt; 
           [0019]      FIG. 8  is a flowchart showing a process of a command in the Hypervisor-Agt; 
           [0020]      FIG. 9  is a flowchart showing a transmission process performed by the Hypervisor-Agt; 
           [0021]      FIG. 10  is a flowchart showing a transmission process performed by the Hypervisor-Agt; 
           [0022]      FIG. 11  is a view showing contents of hardware configuration information  1101  of a server; 
           [0023]      FIG. 12  is a view showing contents of hypervisor configuration information  1111 ; and 
           [0024]      FIG. 13  is a view showing contents of management information  107  of the server. 
       
    
    
     DESCRIPTION OF PREFERRED EMBODIMENTS 
       [0025]    Hereinafter, an embodiment will be described with reference to the drawings. 
         [0026]    Referring to  FIG. 1 , a computer system according to an embodiment has a configuration of a blade server in which plural server modules (hereinafter, simply referred to as servers)  111  and  112  can be mounted in a server chassis  105 . A service processor (SVP)  106  is mounted in the server chassis  105 . 
         [0027]    The servers  111  and  112  are connected to a management server  101  through NICs (Network Interface Cards)  122  and  132  via a network SW  103 , respectively, and connected to a storage apparatus  137  through FC-HBAs (Fibre Channel Host Bus Adapters)  121  and  131  via a fibre channel switch (FC-SW)  135 , respectively. 
         [0028]    The servers  111  and  112  basically have the same configuration and include BMCs (Base Management Controllers)  120  and  130 , the FC-HBAs  121  and  131 , and the NICs  122  and  132 , respectively. Each of hypervisors  117  and  127  is a virtual mechanism by which physically one server logically appears to be plural servers. 
         [0029]    In the server  111 , two LPARs  113  and  114  simulated on the hypervisor  117  are established and operated. Each of Hypervisor-Agts  119  and  129  in the hypervisors  117  and  127  is an agent which detects a failure of the LPARs and notifies the management server  101  of the failure. 
         [0030]    An LPAR  123  is operated in the server  112  in the embodiment, and a destination LPAR 4  ( 124 ) of the LPAR 2  ( 114 ) in the server  111  is set later. 
         [0031]    In order to establish communications, each of the FC-HBAs  121  and  131  has one WWN for each FC connection port as an HBA address. The LPARs  113  and  114  are provided with logical HBA ports  115  and  116 , respectively, and the ports are given unique WWNs (World Wide Names) such as vfcWWN 1  ( 115 ) and vfcWWN 2  ( 116 ), respectively. Each logical HBA also has the same WWN as the physical HBA. It should be noted that the LPAR 3  ( 123 ) in the server  112  is also similarly given a unique WWN. 
         [0032]    The storage apparatus  137  has plural disk units  138  to  140  called LUs (logical units) which are logically specified. Connection information indicating association of the LUs with the servers is managed by a controller in the storage apparatus  137 . For example, the LU 10  ( 138 ) is connected to the LPAR  113  having the vfcWWN 1  ( 115 ) as the WWN, and the LU 11  ( 139 ) is connected to the LPAR  114  having the vfcWWN 2  ( 116 ) as the WWN. A function for setting the connection relation is called an LUN security setting function. 
         [0033]    The SPV  106  manages all the servers in the server chassis, and performs power source control and a failure process of the servers. In order to manage the servers, hardware configuration information  1101  (see  FIG. 11 ) of the server and hypervisor configuration information  1111  (see  FIG. 12 ) are stored into a nonvolatile memory (not shown) in the SVP for management. The configuration information  1101  and  1111  are managed for each server, and the SVP has two-screen configuration information  108 - 1  and  108 - 2  corresponding to the servers  111  and  112 , respectively, in the example illustrated in  FIG. 1 . Further, the hypervisor configuration information  1111  includes information corresponding to the hypervisors  117  and  127  of the servers  111  and  112 . 
         [0034]    The management server  101  manages the servers  111  and  112  and the LPARs formed in the servers. Therefore, management information  107  (see  FIG. 13 ) of the servers is stored into a memory (not shown) for management. In the embodiment, a function of managing migrating of the LPAR is also provided. 
         [0035]    Next, contents of the respective management information will be described with reference to  FIGS. 11 to 13 . 
         [0036]    As shown in  FIG. 11 , the hardware configuration information (occasionally referred to as server module/hardware configuration information)  1101  of the server holds physical server information such as boot setting information  1102 , HBA-BIOS information  1103 , addWWN information  1104 , OS-type information of physical server  1105 , designation of disabling hyper threading  1106 , an IP address of hypervisor stored by SVP  1107 , and an architecture  1108 . The hardware configuration information  1101  is present for each server module (partition). 
         [0037]    As shown in  FIG. 12 , the hypervisor configuration information  1111  is information managed for each LPAR in the partitions, and is present for each of the LPARs  113  and  114  (illustrated by using  1111 - 1  and  1111 - 2 ). Each hypervisor configuration information  1111  holds information such as vfcWWN information ( 1112 - 1 ), Active/NonActive ( 1113 - 1 ) indicating whether or not the LPAR is being active, CPU information ( 1114 - 1 ) including the number of CPUs and the like, a memory capacity ( 1115 - 1 ), and an I/O configuration ( 1116 - 1 ) including the HBA, NIC and the like. 
         [0038]    Although the hardware configuration information  1101  of the server and the hypervisor configuration information  1111  are set and managed by the SVP  106 , these pieces of information are held by each hypervisor operated on the servers. 
         [0039]    As shown in  FIG. 13 , the management information (occasionally referred to as server module management information)  107  of the servers managed by the management server  101  holds information such as a server module number  1201 , an architecture type of hardware  1202 , a mounted-memory capacity  1203 , a total memory utilization of active LPARs  1204 , a memory free space  1205 , a mounted-CPU performance  1206 , total performances of assigned-CPUs  1207 , an available CPU performance  1208 , the number of available NICs  1209 , and the number of available HBAs  1210 . 
         [0040]    According to the embodiment, when a failure occurs in the LPAR of the server  111 , the management server  101  that receives the failure notification sets the destination LPAR 4  ( 124 ) in the server  112  and controls to allow the LPAR 4  ( 124 ) to take over the configuration information unique to the LPAR where the failure occurs. 
         [0041]    Hereinafter, a setting process of the destination LPAR and a takeover process of the configuration information unique to the LPAR when a failure occurs in the LPAR in the server  111  will be described in detail with reference to  FIGS. 2 and 3 . The example illustrated in  FIGS. 2 and 3  shows processing operations performed by the management server  101 , the hypervisor  117  of the server  111 , and the hypervisor  127  of the server module  112  when a failure occurs in the LPAR 2  ( 114 ) of the server  111 . 
         [0042]    When a failure occurs in the LPAR 2  ( 114 ) and the hypervisor  117  operated in the server  111  detects the failure (S 201 ), the hypervisor  117  transmits a failure notification (Hypervisor-Agt alert) to the management server  101  (S 202 ). The management server  101  transmits a deactivate command so as to deactivate the LPAR 2  where the failure occurs (S 203 ). After receiving the LPAR deactivate command, the hypervisor  117  performs deactivation (a deactivate process) of the LPAR 2  (S 205 ). When the deactivate process is completed, the hypervisor  117  transmits the Hypervisor-Agt alert to the management server  101  to notify the same of the completion of deactivate (S 206 ). 
         [0043]    The management server  101  which receives the Hypervisor-Agt alert displays a deactivate status of the LPAR where the failure occurs on a display unit as management information (S 207 ), and transmits a configuration information reading command of the LPAR 2  (S 208 ). 
         [0044]    The hypervisor  117  which receives the command transmits the server module/hardware configuration information and the hypervisor configuration information of the LPAR 2  held by the hypervisor  117  to the management server  101  (S 209 ). 
         [0045]    When completing the reception of the data, the management server  101  displays the completion of reception (S 210 ). Thereafter, the management server  101  determines a destination server module (S 301 ). For example, the management server  101  instructs the hypervisor  127 , which is supposed to generate the LPAR on the destination server module  112 , to receive the server module/hardware configuration information of the server module  111  where the failure occurs and the hypervisor configuration information of the LPAR 2  (S 302 ). 
         [0046]    When receiving the configuration information relating to the LPAR 2  where the failure occurs (S 303 ), the hypervisor  127  determines whether or not the LPAR can be generated in the destination server module on the basis of the configuration information (S 305 ). The determination will be described later in detail. If the result of the determination satisfies predetermined conditions, the LPAR which takes over the configuration information relating to the LPAR 2  of the original server is generated in the destination server  112  (S 306 ). In this example, the LPAR 4  ( 124 ) serves as the LPAR of the destination server. When completing the generation of the LPAR 4  ( 124 ), the hypervisor  127  transmits the Hypervisor-Agt alert and notifies the completion of generation of the LPAR (S 307 ). 
         [0047]    When receiving the Hypervisor-Agt alert, the management server  101  transmits an activate command to the hypervisor  127  so as to activate the generated LPAR 4  (S 308 ). The hypervisor  127  which receives the activate command activates the generated LPAR  124  (S 309 ). Then, the hypervisor  127  transmits the Hypervisor-Agt alert and notifies the completion of activate of the LPAR  124  (S 310 ). The management server  101  which receives the Hypervisor-Agt alert displays an activate status of the LPAR  124  on the display unit (S 311 ). 
         [0048]    Next, a process performed by the management server  101  when a failure occurs in the LPAR 2  ( 114 ) will be described with reference to  FIGS. 4 and 5 . 
         [0049]    When receiving the Hypervisor-Agt alert which notifies that the failure occurs in the LPAR 2  from the hypervisor  117 , the management server  101  starts a process at the time of detecting the LPAR failure (S 401 ). 
         [0050]    First of all, the management server  101  transmits a deactivate command to the hypervisor  117  of the server module  111  in which the LPAR 2  where the failure occurs is operated so as to deactivate the operation of the LPAR 2  (S 402 ). Thereafter, the management server  101  waits until the deactivate process of the LPAR 2  is completed (S 403 ). When the deactivate process is properly completed, the management server  101  updates a display table of the LPAR 2  to “deactivate status” (S 404 ). On the other hand, when the deactivate process is not properly completed, the management server  101  displays a cold standby failure (S 411 ), and terminates the process (S 412 ). 
         [0051]    When the display table of the LPAR 2  is updated to “deactivate status” (S 404 ), the management server  101  transmits the configuration information reading command of the LPAR 2  (S 405 ). When receiving the configuration information of the LPAR 2  (S 406 ) and properly completing the reception (S 407 ), the management server  101  displays the completion of reception (S 408 ). On the other hand, when the reception is not properly completed, the management server  101  displays the cold standby failure (S 413 ) and terminates the process (S 414 ). 
         [0052]    After the management server  101  properly completes the reception (S 407 ) and displays the completion of reception (S 408 ), the management server  101  computes an effective CPU performance of the LPAR 2  and an effective CPU performance of the server module other than one that generates the LPAR 2 . 
         [0053]    Here, the effective CPU performance of the LPAR 2  is obtained by multiplying (the number of physical CPUs) by (a service ratio of the LPAR in the original server module). Further, the effective CPU performance of the server module other than one that generates the LPAR 2  is obtained by multiplying (the number of physical CPUs) by (100%−(service ratios of all LPARs that are being activated)). 
         [0054]    Next, the management server  101  determines the conditions of the server module for LPAR generation by using the server module management information  107  of the management server  101  (S 410 ). The conditions include, for example, the following determinations such as (a) whether the server module having the same architecture as the LPAR 2  is present, (b) whether the server module having an available memory equal to or larger than that of the LPAR 2  is present, (c) whether the server module having an effective CPU performance equal to or higher than that of the LPAR 2  is present, and (d) whether the server module having available NICs and HBAs equal to or larger in number than those used by the LPAR 2 . 
         [0055]    If these four conditions are all satisfied, the management server  101  selects one server module with the highest effective CPU performance as the destination server module among the server modules that satisfy the conditions (S 501 ). If any one of the four conditions is not satisfied, the management server  101  displays the cold standby failure (S 415 ) and terminates the process (S 416 ). 
         [0056]    When the destination server module (the server module  112  in this example) which satisfies the four conditions is selected, the management server  101  transfers the configuration information relating to the LPAR 2  where the failure occurs to the hypervisor  127  of the destination server module  112  and instructs to generate the LPAR (S 502 ). The management server  101  transmits the data (configuration information relating to the LPAR 2  where the failure occurs) received from the hypervisor  117  of the server module  111  where the failure occurs to the hypervisor  127  (S 503 ). When the data transmission is properly completed (S 504 ), the management server  101  displays the completion of transmission (S 505 ). On the other hand, when the data transmission is not properly completed (S 504 ), the management server  101  displays the cold standby failure (S 511 ) and terminates the process (S 512 ). 
         [0057]    Thereafter, the management sever  101  waits until the LPAR is generated in the destination server module  112  (S 506 ). The LPAR 4  to be generated has the same configuration as the LPAR 2  where the failure occurs. When the generation of the LPAR 4  is properly completed, the management server  101  transmits a command of activating the destination LPAR 4  ( 124 ) of the destination server module  112  (S 507 ). On the other hand, when the generation of the LPAR 4  is not properly completed, the management server  101  displays the cold standby failure (S 513 ) and terminates the process (S 514 ). 
         [0058]    When the generation of the destination LPAR 4  ( 124 ) is properly completed and the activate command is transmitted (S 507 ), the management server  101  awaits completion of activating the destination LPAR 4  ( 124 ) (S 508 ). When the destination LPAR 4  is properly activated, the management server  101  updates the status of the destination LPAR 4  ( 124 ) to “activate status” (S 509 ), and terminates the process (S 510 ). On the other hand, when the destination LPAR 4  ( 124 ) is not properly activated, the management server  101  displays the cold standby failure (S 515 ) and terminates the process (S 516 ). 
         [0059]    Due to the following reasons, the above-described control allows the destination LPAR 4  ( 124 ) to be activated as a substitute for the LPAR 2  ( 114 ) where the failure occurs. An access to the storage apparatus is controlled by using a WWN. The WWN is assigned to each port of the physical devices. However, the logical HBA is provided for each LPAR and the WWN is assigned to each port of the logical HBAs in the embodiment. The WWN of the logical HBA is hereinafter called vfcWWN. As described in  FIG. 1 , the connection relation between the LUNs and WWNs is set by the LUN security function. Since the logical WWN is not distinguished from the physical WWN from the storage apparatus side, it is possible to manage the access right to the LU on an LPAR basis (when the vfcWWN is used, the WWN of the physical device is set so as not to be recognized from the storage apparatus). By booting the destination LPAR using the same vfcWWN as that used by the LPAR where the failure occurs, the same system as that in the original server can be started. 
         [0060]    Next, a process performed by the hypervisor when a failure occurs in the LPAR 2  will be described with reference to  FIG. 6 . 
         [0061]    When a failure occurs in the LPAR 2 , the hypervisor  117  starts an LPAR failure detection process (S 601 ). In the failure detection process, the hypervisor  117  analyzes a factor of the failure occurrence to determine whether or not the factor is recoverable (S 602 ). If the result of the determination shows that the LPAR failure is caused by an unrecoverable factor, the hypervisor  117  requests transmission of the Hypervisor-Agt alert to notify the Hypervisor-Agt ( 118 ) of the LPAR failure (S 603 ), executes a failure process such as log acquisition at the time of LPAR failure (S 604 ), and terminates the process (S 605 ). 
         [0062]    On the other hand, when the LPAR failure is caused by a recoverable factor, the hypervisor  117  performs a recovery process (S 606 ) and terminates the process (S 607 ). 
         [0063]    Next, a command process in the Hypervisor-Agt ( 118 ) accompanied by a command execution request from the management server  101  will be described with reference to  FIGS. 7 and 8 . 
         [0064]    When receiving the command execution request transmitted from the management server  101 , the Hypervisor-Agt ( 118 ) performs a reception process (S 701 ). Since there are many kinds of commands to be requested, the Hypervisor-Agt ( 118 ) analyzes the types of the commands in the first place (S 702 ). In this example, the Hypervisor-Agt ( 118 ) performs a process of five commands of an LPAR deactivate command for deactivating the LPAR, an LPAR configuration information reading command, an LPAR configuration information writing command, an LPAR activate command for activating the LPAR, and an LPAR generating command. 
         [0065]    In the case of the LPAR deactivate command, it is determined whether the LPAR to be deactivated is appropriate (S 703 ). When it is determined that the LPAR is not appropriate, an error process is performed (S 707 ), and the process is terminated (S 708 ). When it is determined that the LPAR 2  to be deactivated is appropriate, a process for deactivating the target LPAR 2  is performed (S 704 ). Then, it is determined whether or not the deactivate process is successfully completed (S 705 ). When the deactivate process fails, an error process is performed (S 707 ), and the process is terminated (S 708 ). On the other hand, when the deactivate process is successfully completed, transmission of the Hypervisor-Agt alert is requested to notify the completion of deactivate of the LPAR 2 , and the process is terminated (S 708 ). 
         [0066]    In the case of the LPAR configuration information reading command, the configuration information of the target LPAR 2  is transferred to the management server  101 . Thereafter, it is determined whether or not the data transfer is successfully completed (S 710 ). When the data transfer is successfully completed, the process is terminated (S 712 ). On the other hand, when the data transfer fails, an error process is performed (S 711 ), and the process is terminated (S 712 ). 
         [0067]    In the case of the LPAR configuration information writing command, the configuration information of the target LPAR 2  is transferred from the management server  101  to the hypervisor  127 . Thereafter, it is determined whether or not the data transfer is successfully completed (S 714 ). When the data transfer is successfully completed, the process is terminated (S 716 ). On the other hand, when the data transfer fails, an error process is performed (S 714 ), and the process is terminated (S 716 ). 
         [0068]    Next, in the case of the LPAR activate command (see  FIG. 8 ), it is determined whether the LPAR to be activated is appropriate (S 801 ). When the result shows that the LPAR is not appropriate, an error process is performed (S 805 ), and the process is terminated (S 806 ). On the other hand, when it is determined that the LPAR 2  to be activated is appropriate, a process for activating the target LPAR 2  is performed (S 802 ). Then, it is determined whether the activate is successfully completed (S 803 ). When the activate process fails, an error process is performed (S 805 ), and the process is terminated (S 806 ). 
         [0069]    On the other hand, when the activate process is successfully completed, transmission of the Hypervisor-Agt alert is requested to notify the completion of activate of the LPAR (S 804 ), and the process is terminated (S 806 ). 
         [0070]    Next, in the case of the LPAR generating command, the effective CPU performances in the original and destination server modules are computed (S 807 ). The effective CPU performance in the original server module is obtained by multiplying (the number of physical CPUs) by (the service ratio of the LPAR in the original server module). The effective CPU performance in the destination server module is computed by multiplying (the number of physical CPUs) by (100%−(service ratios of all LPARs that are being activated)). 
         [0071]    Thereafter, there are determined the following three conditions (S 808 ), such as (1) the effective CPU performance in the destination server module is equal to or higher than that in the original server module by comparing the effective CPU performances with each other, (2) a memory in the destination server module is available, and (3) the NICs and HBAs equal to or larger in number than those used by the LPAR in the original server module are available in the destination server module. 
         [0072]    When any one of the three conditions is not satisfied, it is determined that it is impossible to generate the LPAR. Then, an error process is performed (S 812 ), and the process is terminated (S 813 ). 
         [0073]    On the other hand, when the three conditions are all satisfied, the target LPAR is generated (S 809 ). In this example, the LPAR 4  ( 124 ) is generated as a substitute for the LPAR 2 . 
         [0074]    Thereafter, it is determined whether or not the generation of the LPAR is successfully completed (S 810 ). When the generation of the LPAR is successfully completed, transmission of the Hypervisor-Agt alert is requested to notify the completion of LPAR generation (S 811 ), and the process is terminated (S 813 ). On the other hand, when the generation of the LPAR fails, an error process is performed (S 812 ), and the process is terminated (S 813 ). 
         [0075]    Next, a transmission process performed by the Hypervisor-Agt when transmission of the hypervisor alert is requested will be described with reference to  FIGS. 9 and 10 . 
         [0076]    When the transmission of the Hypervisor-Agt alert is requested, the Hypervisor-Agt ( 118 ) analyzes the type of the alert (S 902 ). 
         [0077]    The result shows that the alert type is the completion of LPAR activate, an LPAR activate completion alert is transmitted (S 903 ), and the process is terminated (S 906 ). 
         [0078]    The result shows that the alert type is the failure of LPAR activate, an LPAR activate failure alert is transmitted (S 904 ), and the process is terminated (S 906 ). 
         [0079]    The result shows that the alert type is the occurrence of LPAR failure, an LPAR failure occurrence alert is transmitted (S 905 ), and the process is terminated (S 906 ). 
         [0080]    The result shows that the alert type is the completion of LPAR deactivate, an LPAR deactivate completion alert is transmitted (S 1001 ), and the process is terminated (S 906 ). 
         [0081]    The result shows that the alert type is the failure of LPAR deactivate, an LPAR deactivate failure alert is transmitted (S 1002 ), and the process is terminated (S 906 ). 
         [0082]    The result shows that the alert type is the completion of LPAR generation, an LPAR generation completion alert is transmitted (S 1003 ), and the process is terminated (S 906 ). 
         [0083]    The result shows that the alert type is the failure of LPAR generation, an LPAR generation failure alert is transmitted (S 1004 ), and the process is terminated (S 906 ). 
         [0084]    In the above-described example, when a failure occurs in the LPAR of the server  111 , the LPAR is migrated to another while transmitting and receiving various information between the hypervisors in the original and destination server modules under the control of the management server  101 . 
         [0085]    Further, the failure of the server can be detected from the SVP. Accordingly, even at the time of hardware failure, the LPARs operated on the hardware can be migrated to different physical devices. 
         [0086]    As described above, according to the embodiment, when an LPAR failure occurs in the virtual computer system, the LPAR can be migrated to another while migrating detailed information. Accordingly, the embodiment can be applied to an operation using the virtual computer system in which efficiency is required. Further, when plural physical computers vary in performance, it is possible to easily migrate a specific LPAR among the physical computers.