Abstract: For a first virtual machine (VM) executing in a physical machine, a second VM is instantiated in the physical machine, the first VM using a physical adapter installed in the physical machine, the first VM virtualizing a portion of physical memory of the physical machine, the second VM virtualizing the physical adapter. The second VM is deployed using a memory mapping virtualizing the portion of physical memory. Checkpointing of an application executing in the first VM is caused, generating application state data of the application. The application is caused to execute in the second VM using the application state data. Process data of the application is caused to be updated in the second VM, the updating instructing the application to use the memory mapping.

Abstract: For a first virtual machine (VM) executing on a physical machine and virtualizing a set of redundant physical adapters installed in the physical machine, a second VM is instantiated on the physical machine. A first physical adapter is reassigned from the first VM to the second VM, the first physical adapter comprising one of the set of redundant physical adapters, the reassigning performed without rebooting a first operating system executing in the first VM. A second rule configuration of the second VM is updated to match a first rule configuration of the first VM, forming an updated second VM. A hypervisor managing the physical machine is caused to redirect traffic for a first virtual adapter associated with the reassigned first physical adapter to the updated second VM.

Abstract: Examples of techniques for failure detection for central electronics complex (CEC) group management are described herein. An aspect includes issuing a first virtual input/output server (VIOS) probe to a hardware management console (HMC) of a central electronics complex (CEC) group. Another aspect includes receiving a first response packet that includes health data corresponding to a plurality of VIOSes. Another aspect includes determining, based on the first response packet, that cluster down is indicated on a first VIOS. Another aspect includes, based on determining that cluster down is indicated on the first VIOS, getting a VIOS state for the first VIOS from the HMC. Another aspect includes determining based on the VIOS state that the first VIOS is in a down state and determining that the first VIOS is unhealthy. Another aspect includes updating a health data entry corresponding to the first VIOS to indicate that the first VIOS is unhealthy.

Abstract: A write operation storing data in a first storage device is duplicated to a first replication file. A set of differences between a first version of the first replication file determined at a first time and a second version of the first replication file determined at a second time is determined, the set of differences comprising a set of results of duplicated write operations occurring between the first time and the second time. At a second file system, storage of the set of differences in a second storage device is caused, creating a duplicate in the second storage device of the data stored in the first storage device.

Abstract: A system for monitoring the health of virtual machines associated with a shared storage pool (SSP) includes a plurality of virtual machines (VMs), two or more virtual input/output servers (VIOSes) participating in the SSP, and an orchestration node. Each VIOS in the SSP is associated with a respective set of VMs of the plurality of VMs. Each VM is configured to transmit respective health data describing the VM to its associated VIOS. The orchestration node is in communication with each of the two or more VIOSes participating in the SSP, where each VIOS is configured to transmit to the orchestration node the respective health data of each VM in the respective set of VMs associated with the VIOS. The orchestration node is configured to monitor the health of a plurality of VMs associated with the two or more VIOSes participating in the SSP.

Abstract: For a first virtual machine (VM) executing on a physical machine and virtualizing a set of redundant physical adapters installed in the physical machine, a second VM is instantiated on the physical machine. A first physical adapter is reassigned from the first VM to the second VM, the first physical adapter comprising one of the set of redundant physical adapters, the reassigning performed without rebooting a first operating system executing in the first VM. A second rule configuration of the second VM is updated to match a first rule configuration of the first VM, forming an updated second VM. A hypervisor managing the physical machine is caused to redirect traffic for a first virtual adapter associated with the reassigned first physical adapter to the updated second VM.

Abstract: A system includes a plurality of virtual machines (VMs), a shared storage pool (SSP) configured to store health information for the plurality of VMs, and a plurality of virtual input/output servers (VIOSs) participating in the shared storage pool (SSP). Each VIOS is associated with a respective group of VMs of the plurality of VMs and is configured to receive health data for each VM of the respective group of VMs. The system also includes a health information database associated with each VIOS of the plurality of VIOSs, the health information database configured to store a subset of the health data for each VM of the respective group of VMs. Each VIOS is configured to transmit the health data for each VM of the respective group of VM to the SSP, and in parallel, store the subset of the health data in the health information database.

Abstract: Examples of techniques for failure detection for central electronics complex (CEC) group management are described herein. An aspect includes issuing a first virtual input/output server (VIOS) probe to a hardware management console (HMC) of a central electronics complex (CEC) group. Another aspect includes receiving a first response packet that includes health data corresponding to a plurality of VIOSes. Another aspect includes determining, based on the first response packet, that cluster down is indicated on a first VIOS. Another aspect includes, based on determining that cluster down is indicated on the first VIOS, getting a VIOS state for the first VIOS from the HMC. Another aspect includes determining based on the VIOS state that the first VIOS is in a down state and determining that the first VIOS is unhealthy. Another aspect includes updating a health data entry corresponding to the first VIOS to indicate that the first VIOS is unhealthy.

Abstract: Examples of techniques for failure detection for central electronics complex (CEC) group management are described herein. An aspect includes issuing a first logical partition (LPAR) probe to a hardware management console (HMC) of a central electronics complex (CEC) group, wherein the CEC group comprises a plurality of LPARs. Another aspect includes receiving a first response packet from the HMC corresponding to the first LPAR probe, wherein the first response packet comprises health data corresponding to a first LPAR of the plurality of LPARs. Another aspect includes storing the health data corresponding to the first LPAR in a first health data entry corresponding to the first LPAR. Another aspect includes, for a second LPAR of the plurality of LPARs that was not included in the first response packet, updating a second health data entry corresponding to the second LPAR to indicate that the second LPAR is healthy.

Abstract: Methods and systems for migrating a virtual machine instance between devices include one or more migration risk rules, each migration risk rule relating to a validation set having one or more validation substasks. A processor is configured to score a received migration request against one or more of the migration risk rules to generate one or more scores for the migration request, to compare each score to a respective threshold to determine if a level of risk according to the respective rule merits performing validation for the validation set, to validate the migration request by only those validation sets that correspond to the scores that exceed the respective threshold, and to trigger migration of a virtual machine to a target device in accordance with the migration request if none of the validation sets fail to validate the migration request.

Abstract: A system includes a plurality of virtual machines (VMs), a shared storage pool (SSP) configured to store health information for the plurality of VMs, and a plurality of virtual input/output servers (VIOSs) participating in the shared storage pool (SSP). Each VIOS is associated with a respective group of VMs of the plurality of VMs and is configured to receive health data for each VM of the respective group of VMs. The system also includes a health information database associated with each VIOS of the plurality of VIOSs, the health information database configured to store a subset of the health data for each VM of the respective group of VMs. Each VIOS is configured to transmit the health data for each VM of the respective group of VM to the SSP, and in parallel, store the subset of the health data in the health information database.

Abstract: Examples of techniques for failure detection for central electronics complex (CEC) group management are described herein. An aspect includes issuing a first logical partition (LPAR) probe to a hardware management console (HMC) of a central electronics complex (CEC) group, wherein the CEC group comprises a plurality of LPARs. Another aspect includes receiving a first response packet from the HMC corresponding to the first LPAR probe, wherein the first response packet comprises health data corresponding to a first LPAR of the plurality of LPARs. Another aspect includes storing the health data corresponding to the first LPAR in a first health data entry corresponding to the first LPAR. Another aspect includes, for a second LPAR of the plurality of LPARs that was not included in the first response packet, updating a second health data entry corresponding to the second LPAR to indicate that the second LPAR is healthy.

Abstract: A system for monitoring the health of virtual machines associated with a shared storage pool (SSP) includes a plurality of virtual machines (VMs), two or more virtual input/output servers (VIOSes) participating in the SSP, and an orchestration node. Each VIOS in the SSP is associated with a respective set of VMs of the plurality of VMs. Each VM is configured to transmit respective health data describing the VM to its associated VIOS. The orchestration node is in communication with each of the two or more VIOSes participating in the SSP, where each VIOS is configured to transmit to the orchestration node the respective health data of each VM in the respective set of VMs associated with the VIOS. The orchestration node is configured to monitor the health of a plurality of VMs associated with the two or more VIOSes participating in the SSP.

Abstract: Methods for migrating a virtual machine instance between devices include scoring a received migration request against one or more rules in a rule database to generate one or more scores for the migration request. Each rule relates to one or more respective validation sets. Each score is compared to a respective threshold. The migration request is validated by only those validation sets that correspond to the scores that exceed the respective threshold. A virtual machine is migrated to a target device in accordance with the migration request responsive to successful validation by the validation sets used.

Abstract: Methods for migrating a virtual machine instance between devices include scoring a received migration request against one or more rules in a rule database to generate one or more scores for the migration request. Each rule relates to one or more respective validation sets. Each score is compared to a respective threshold. The migration request is validated by only those validation sets that correspond to the scores that exceed the respective threshold. A virtual machine is migrated to a target device in accordance with the migration request responsive to successful validation by the validation sets used.

Abstract: Methods and systems for migrating a virtual machine instance between devices include one or more migration risk rules, each migration risk rule relating to a validation set having one or more validation substasks. A processor is configured to score a received migration request against one or more of the migration risk rules to generate one or more scores for the migration request, to compare each score to a respective threshold to determine if a level of risk according to the respective rule merits performing validation for the validation set, to validate the migration request by only those validation sets that correspond to the scores that exceed the respective threshold, and to trigger migration of a virtual machine to a target device in accordance with the migration request if none of the validation sets fail to validate the migration request.

Abstract: Methods for migrating a virtual machine instance between devices include scoring a received migration request against one or more rules in a rule database relating to one or more respective validation sets. Each validation set includes one or more validation subtasks. Each score is compared to a respective threshold to determine if a level of risk according to the respective rule merits performing validation. The migration request is validated by one or more validation sets that correspond to the scores that exceed the respective threshold.

Abstract: Methods and systems for migrating a virtual machine instance between devices include scoring a received migration request against one or more rules in a rule database relating to one or more respective validation sets. Each validation set includes one or more validation subtasks. Each score is compared to a respective threshold to determine if a level of risk according to the respective rule merits performing validation. The migration request is validated by one or more validation sets that correspond to the scores that exceed the respective threshold.

Abstract: Multipath I/O in a computer system includes: receiving asynchronously, for a single I/O operation by a memory controller from a plurality of I/O adapters, a request to access a memory page, where each request to access the memory page includes an adapter-specific tag; and for each request received by the memory controller: determining, by the memory controller, whether an adapter-specific tag has been assigned to the memory page; if an adapter-specific tag has not been assigned to the memory page: assigning, by the memory controller, the received adapter-specific tag to the memory page; and allowing, by the memory controller, access to the memory page; and if an adapter-specific tag has been assigned to the memory page, granting access to the memory page only when the received adapter-specific tag is the adapter-specific tag assigned to the memory page.

Abstract: Methods for migrating a virtual machine instance between devices include scoring a received migration request against one or more rules in a rule database relating to one or more respective validation sets. Each validation set includes one or more validation subtasks. Each score is compared to a respective threshold to determine if a level of risk according to the respective rule merits performing validation. The migration request is validated by one or more validation sets that correspond to the scores that exceed the respective threshold.