Setup environment for z/VM Live Guest Relocation(LGR)

Single System Image(SSI)

SSI enhances the z/VM systems management, communications, disk management, device mapping, virtual machine definition management, installation, and service functions to enable multiple z/VM systems to share and coordinate resources within a Single System Image structure. This combination of enhanced functions provides the foundation that enables Live Guest Relocations (LGR), which is the ability for a Linux guest to be moved from one z/VM system to another within the SSI cluster. For more information, see z/VM Single System Image Overview.

Requirements of an SSI cluster for Live Guest Relocation

In the SSI cluster, make sure all resources used by the virtual machine are available on the destination SSI cluster member.

  • Devices and facilities

  • Capacity for the virtual machine's memory and processor requirements

  • Equivalency ids (EQIDs) are defined for OSAs, OSAs should be connected to the same LAN segment

  • If possible, use the same device numbers to refer to equivalent devices

  • Make sure the same VSWITCH is defined on the destination compute node (destination SSI cluster number) with the source compute node (source SSI cluster member) and the OSAs have been assigned EQIDs.

  • Ensure that each member of the SSI has the same name of the shared DASD group and use it to add the compute node because the IBM® Cloud Infrastructure Center uses the name of the shared DASD group as the part of the internal unique ID that is used to manage the shared storage of the SSI.

    The format of the internal ID of an SSI is: <SSI_NAME>:<DASD_GROUP_NAME> . Here, <SSI_NAME> is the ssi_name got from command smcli SSI_Query , <DASD_GROUP_NAME> is the name of the input DASD group when adding the compute node. An example of the internal ID of an SSI is:

    ICIC2SSI:ECKD:ICICPL
    

    Here ICIC2SSI is the ssi_name you receive from the sample smcli SSI_Query beneath:

    # smcli SSI_Query
    ssi_name = ICIC2SSI
    ssi_mode = Stable
    ... ...
    

Guest Configuration for Live Guest Relocation

In order to be eligible to relocate, a z/VM guest virtual machine must be defined as a single configuration virtual machine. That is to say: OPTION CHPIDVIRTUALIZATION ONE should be specified in a virtual machine's directory entry. For more information, refer to Planning for live guest relocation for z/VM