Abstract: In a Virtual Input/Output (I/O) Server (VIOS) partition, a method comprises a cluster aware (CA) operating system (OS) of a VIOS partition performing the functions of: responsive to a restore command: retrieving a configuration backup file from storage; comparing a DRC name from the retrieved file with a DRC name of the current VIOS partition performing the restore operation; in response to an occurrence of a DRC name mismatch: retrieving an initial UUID of the VIOS from the configuration backup file; accessing a UUID table within a management tool; locating a matching UUID to the initial UUID within the UUID table; and in response to locating the matching UUID: verifying that the configuration data file belongs to the current VIOS initiating the restore operation; and performing the restore operation to restore the configurations of the hardware, logical and virtual devices of the first VIOS to an earlier configuration state.

Abstract: In a data processing system including a virtual I/O server (VIOS) cluster and multiple logical partitions (LPARs), at least one VIOS of the VIOS cluster performs functions of: receiving first registration information from one or more entities within the VIOS cluster; registering, based on the first registration information, a handler associated with a first message type; responsive to receiving second registration information, registering, based on the second registration information, a listener associated with a second message type; receiving a first message associated with a first alert event of the cluster; determining, based on the first message, that the handler is associated with the first message type; and calling the handler. In one embodiment, the handler is associated with a pointer to a subroutine, and registering the handler includes storing the pointer in a data structure that associates the handler with the first message type.

Abstract: A method, system, and computer program product utilizes cluster-awareness to effectively maintain and update Persistent Reserve (PR) state data and provide nodes with notification of changes to PR state data within a Virtual Input/Output (I/O) Server (VIOS) cluster. A Persistent Reserve (PR) utility identifies a database that is accessible to other VIOSes in the cluster, in which database information about the current state of the Persistent Reservation is maintained. The PR utility checks the current Persistent Reserve state in the database to verify whether an initiator of a PR command is allowed to perform the command. If the initiator is allowed to perform the command, the PR utility modifies/updates the Persistent Reserve state in the database to reflect the received Persistent Reserve command. The PR utility updates the initiator's local copy of the modified PR state data and sends a corresponding notification message to other VIOSes in the cluster.

Abstract: In a Virtual Input/Output (I/O) Server (VIOS) partition within a data processing system that comprises cluster-aware VIOSes, a method includes: performing, via a backup/restore utility of a cluster aware (CA) operating system (OS) executing on a processor resource of the first VIOS partition, a backup operation on the first VIOS partition, which creates a first configuration backup file having configuration information about the hardware, logical and virtual devices of the VIOS partition; storing the configuration backup file within local storage; and responsive to receipt of a VIOS restore command: retrieving the configuration backup file from the local storage; and restoring the configuration of the hardware, logical and virtual devices of the first VIOS to a state that existed at a time at which the backup operation creating the configuration backup file was performed.

Abstract: A method enables cluster-level backup and restore functionality of all Virtual Input/Output Server (VIOS) configuration data within a VIOS cluster and the data of a shared VIOS cluster database. The method comprises: performing, via a backup/restore utility of a VIOS partition, a cluster level backup, which creates a first VIOS cluster configuration backup file having configuration information about hardware, logical and virtual devices of each VIOS partition within a VIOS cluster and all cluster data from the shared VIOS database of the VIOS cluster; storing the VIOS cluster configuration backup file within a storage location; and responsive to receipt of a VIOS restore command at a VIOS partition: retrieving the configuration backup file from the storage location; restoring a configuration of the hardware, logical and virtual devices of each VIOS within the VIOS cluster to prior state; and restoring the shared VIOS database with the backed-up cluster data.

Abstract: A method, system, and computer usable program product for migrating memory data between partitions are provided in the illustrative embodiments. All or a portion of a memory data of the source partition is written to a data storage unit, which may be a shared paging space, or a shared area of a data storage unit other than a paging space. The writing uses a first data communication path configured for paging the memory data. The portion of the memory data from the data storage unit is read at a destination partition. The reading uses a second data communication path configured for paging a second memory data. The read portion of the memory data may be used for executing a migrated application. The writing and reading may use a third and a fourth data communication paths respectively that may be configured for paging memory data to the shared area.

Abstract: Automated paging device management is provided for a shared memory partition data processing system. The automated approach includes managing a paging storage pool defined within one or more storage devices for holding logical memory pages external to physical memory managed by a hypervisor of the processing system. The managing includes: responsive to creation of a logical partition within the processing system, automatically defining a logical volume in the paging storage pool for use as a paging device for the new logical partition, the automatically defining occurring absent use of a filesystem, with the resultant paging device being other than a file in a filesystem; and automatically specifying the logical volume as a paging space device for the new logical partition and binding the paging space device to the new logical partition, wherein the logical volume is sized to accommodate a defined maximum memory size of the new logical partition.

Abstract: A method, system, and computer program product provide a shared virtual memory space via a cluster-aware virtual input/output (I/O) server (VIOS). The VIOS receives a paging file request from a first LPAR and thin-provisions a logical unit (LU) within the virtual memory space as a shared paging file of the same storage amount as the minimum required capacity. The VIOS also autonomously maintains a logical redundancy LU (redundant LU) as a real-time copy of the provisioned/allocated LU, where the redundant LU is a dynamic copy of the allocated LU that is autonomously updated responsive to any changes within the allocated LU. Responsive to a second VIOS attempting to read a LU currently utilized by a first VIOS, the read request is autonomously redirected to the logical redundancy LU. The redundant LU can be utilized to facilitate migration of a client LPAR to a different computing electronic complex (CEC).

Abstract: With N_Port ID Virtualization (NPIV), a managed system can be configured so that multiple logical partitions (LPARs) can access independent physical storage through the same physical fibre channel adapter. An NPIV client recovery component of a virtualization management component, such as a Power Hypervisor (pHYP), provides the emulation mapping between server and client virtual fibre channel adapters. The pHYP also provides a mechanism that prevents client partition crashes when the NPIV server (e.g., a VIOS logical partition) goes down. When the NPIV server is rebooted or powers down, the pHYP handles the client LPARs to avoid a crash by removing processing resources from the client logical partition. Thereby, the client logical partition is prevented from attempting to access a root volume group in physical storage via the NPIV server. The pHYP allocates processor resources to the client LPAR when the NPIV server is again available for UO processing.

Abstract: Mechanisms for dynamic reallocation of memory to an application, the memory being from a pool of virtual real memory allocated to a virtual client that executes the application, are disclosed. In one embodiment, a virtual client is allocated a pool of virtual real memory. A subset of this pool of virtual real memory is a block of memory allocated for use by an application. The allocation may be stated as a range of allocated memory with an upper and lower limit. The application calls a kernel service when it thinks it needs a new allocation of memory. The new allocation is established by a power hypervisor connected to the virtual client. Memory is exported by way of a Paging Space Partition.

Abstract: Mechanisms are provided for an I/O virtualization management partition (IMP) to control the shared functionality of an I/O virtualization (IOV) enabled I/O adapter (IDA) through a physical function (PF) of the IOA while the virtual functions (VFs) are assigned to client partitions for normal I/O operations directly. A hypervisor provides device-independent facilities to the code running in the IMP and client partitions. The IMP may include device specific code without the hypervisor needing to sacrifice its size, robustness, and upgradeability. The hypervisor provides the virtual intermediary functionally for the sharing and control of the IOA's control functions.

Abstract: In a data processing system having a plurality of virtualized operating system (OS) partitions, a first cluster-aware virtual input/output server (VIOS) is provided within an OS partition by execution of a cluster-aware (CA) OS on a virtual processor resource of the first VIOS. The CA OS establishes the VIOS as a cluster-aware VIOS by registering the first VIOS with a VIOS cluster comprising a second VIOS. Registering the first VIOS to the VIOS cluster enables the first VIOS to receive VIOS cluster configuration data and status data, which provides the first VIOS with information about the other VIOSes within the VIOS cluster. The first VIOS is thus able to communicate with other VIOSes within the VIOS cluster and share I/O resources with the other VIOSes within the VIOS cluster. Relevant cluster information is stored within a local storage of the first VIOS.

Abstract: A method provides input/output (I/O) redundancy within a data processing system having (a) a client logical partition (LPAR) that generates and consumes I/O requests, (b) a plurality of virtual input/output servers (VIOS) that are communicatively inter-connected with each other to form a VIOS cluster and which include virtual I/O adapters for connecting to a fabric that provides access to a block storage. In one embodiment, a first VIOS receives an I/O request from the client LPAR. The first VIOS detects that a problem exists with a fabric connection to the block storage, and the first VIOS responds to the detected connection problem by autonomously propagating the I/O request to a second VIOS to which the first VIOS is connected. Forwarding of the I/O request to the block storage is subsequently completed by the second VIOS.

Abstract: Automated paging device management is provided for a shared memory partition data processing system. The automated approach includes managing a paging storage pool defined within one or more storage devices for holding logical memory pages external to physical memory managed by a hypervisor of the processing system. The managing includes: responsive to creation of a logical partition within the processing system, automatically defining a logical volume in the paging storage pool for use as a paging device for the new logical partition, the automatically defining occurring absent use of a filesystem, with the resultant paging device being other than a file in a filesystem; and automatically specifying the logical volume as a paging space device for the new logical partition and binding the paging space device to the new logical partition, wherein the logical volume is sized to accommodate a defined maximum memory size of the new logical partition.

Abstract: A “LUN Table” enables Logical Unit Number (LUN) mapping/masking within an Input/Output Virtualization IOV adapter included in a Serial Attached Small Computer System Interface (“SAS” or “Serial Attached SCSI”). A plurality of System Images (“SI”) share block storage through the SAS. The IOV adapter includes one or more Virtual Functions (VF), a Physical Function (PF), and a LUN Table within the PF. The VF allows each SI to communicate I/0 requests with a storage device through the PF. The LUN Table maps the I/0 requests to unique locations within the storage device. Each SI is isolated from all other SIs. Interference between each SI is avoided. A VIOS or a LUN mapping/masking SAN are not required. I/0 latency, processor overhead and storage cost are improved over prior LUN mapping/masking solutions.

Abstract: Methods, systems, and products are disclosed for implementing a generic kernel extension framework that operate generally to allow one kernel extension to register a function callable by other kernel extensions. A kernel extension can be loaded even if a function it potentially could need is not available. If in fact the running kernel extension does eventually request a function that no other kernel extension has registered to provide, it is failed gracefully with a return error code. The client kernel extension can still function normally, assuming the desired service is non-critical. Example services in the non-critical category may include, for example, advanced error handling functions, statistical functions, reporting functions, and so on, including many others as will occur to those of skill in the art.

Abstract: An alternative migration of an LPAR from one server system to another when either or both of the server systems cannot access a Storage Area Network (SAN) or like external storage network. If said source and destination server system do not have access to the same SAN, then a mirror image of said all data storage supporting the transferred LPAR is created and transmitted to local storage supporting the destination server system and then the logical partition (LPAR) is transmitted over the connecting network from the source server system to the destination server system.

Abstract: A method for controlling input and output of a virtualized computing platform is disclosed. The method can include creating a device interface definition, assigning an identifier to a paging device and configuring commands useable by a virtual input output server. The commands can be sent to the input output server and can be converted by the input output server into paging device commands. A hypervisor can assist in facilitating the communication configuration. Other embodiments are also disclosed.

Abstract: In virtualized environments, storage may be managed dynamically due to the changing data storage requirements. In such environments, logical storage unit identifiers (LUN IDs) may be modified as a result of deleting an existing mapping between physical storage and a virtualization server and recreating the mapping. This can result in I/O request failure. Techniques for resolving errors resulting from LUN ID modifications can be time-intensive and labor-intensive and can disrupt a communication path between a host device and the physical storage. Functionality can be implemented to dynamically identify the LUN ID modifications, determine valid LUN IDs, and retransmit failed I/O requests. This can help minimize I/O request failures due to LUN ID modifications without disrupting the communication path between the host device and the physical storage.

Abstract: A method for storing and retrieving blocks of data having different dimensions is disclosed. The method can include receiving a first data segment to be stored in a block storage device where the first data segment has an address. The method can also include determining if the first data segment conforms to a standard dimension and sorting the first data segment according to the destination address if it does not have a standard dimension. The method can further include placing a non-standard data segment into a unfilled block allocation and placing a second non-standard data segment into the unfilled block allocation when the second data segment has the destination identifier. Other embodiments are also disclosed.