HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration
dependency_name hpvm_vgsharedA
dependency_condition hpvm_vgsharedA = up
dependency_location same_node
c. Check the configuration of the package:
# cmcheckconf -P /etc/cmcluster/slvmtest/slvmtest2.conf
Attempting to validate slvmtest.
...
cmcheckconf: Verification completed with no errors found.
d. Save the original configuration file and use the modified configuration in its place to
apply the package configuration to the cluster:
# cp slvmtest.conf slvmtest.conf.orig
# mv slvmtest2.conf slvmtest.conf
# cmapplyconf -P /etc/cmcluster/slvmtest/slvmtest.conf
Attempting to validate slvmtest.
...
Modify the package configuration ([y]/n)? y
Completed the cluster update
e. Run the package associated with the SLVM and virtual machine independent order:
# cmrunpkg hpvm_vgsharedA
Running package hpvm_sharedA on node ghost1
Successfully started package hpvm_sharedA on node ghost1
Running package hpvm_sharedA on node ghost2
Successfully started package hpvm_sharedA on node ghost2
cmrunpkg: All specified packages are running
# cmrunpkg slvmtest
Running package slvmtest on node ghost1
Successfully started package slvmtest on node ghost1
cmrunpkg: All specified packages are running
NOTE: If the package associated with the SLVM is not run prior to starting the package
associated with the virtual machine, then a message similar to the following is displayed:
# cmrunpkg slvmtest
Unable to execute command. Dependency on the following packages not met:
hpvm_vgsharedA
cmrunpkg: Unable to start some package or package instances
10.5.3 Online Migration of VMs with SLVM Virtual Disks in VM as Serviceguard
Package Configurations Requires Manual Reconfiguration
Successful online migration of VMs with SLVM virtual disks in VMs as Serviceguard Package
configurations requires you to configure each SLVM as an independent multinode package.
Additionally, the VM as Serviceguard Package must be modified to indicate a new package
dependency that is the package name associated with the SLVM package.
If the SLVM created and associated with VM is created and associated with the package, perform
the following steps:
1. Create and apply to the cluster an SLVM package for each using multinode and
volume_group modules.
2. Edit the VM package configuration:
a. Remove all references to the volume data reference for each SLVM.
b. Add a dependency for each SLVM package associated with the VM.
c. Check and apply the VM package configuration.
3. Ensure that all SLVM packages are running on all nodes.
10.5 Migrating VMs That are Using Logical Volume Backing Stores 221