HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

Figure 11-2 Guest Application Failover to Another Guest on the Same VM Host
VM Host 1
Serviceguard Cluster
Serviceguard
Package
Failover
Guest VM2
Guest VM1
Physical Node 1
In this configuration, the primary node and the adoptive node are guests running on the same
VM Host system. This cluster does not provide protection against single point of failure (SPOF),
because both the primary cluster member and the adoptive cluster member are guests on the
same physical machine. However, this configuration is useful in testing environments.
If you are running more than one guest on the VM Host system, and you need to share the same
storage among the guests, you must change the SHARE attribute of the shared disk to YES using
the hpvmdevmgmt command. For example:
# hpvmdevmgmt -m gdev:/dev/rdisk/disk1:attr:SHARE=YES
For more information about using the hpvmdevmgmt command, see Section 9.9 (page 161).
11.2.3 VMs and Separate Physical Nodes
Figure 11-3 shows the configuration of an application package that can fail over to a physical
node or partition that is not running Integrity VM software. In this case, the physical node may
be a discreet physical system, a hard partition (nPar), or a soft partition (vPar).
Figure 11-3 Guest Application Failover to an HP Integrity Server
Serviceguard
Package Failover
VM Host Physical Node
Guest VM
Serviceguard
Cluster
The Serviceguard cluster consists of a VM Host system and a Serviceguard node that is not
running Integrity VM. The application configured as a Serviceguard package can fail over to the
physical node. Alternatively, you can run the application on the physical node and configure
the guest on the VM Host system as the adoptive node.
11.2 VMs as Serviceguard Nodes 189