HP Integrity Virtual Machines Installation, Configuration, and Administration Version A.03.50

host2# cmrunpkg -n host2 compass1
4. Enable the package:
host2# cmmodpkg -e compass1
5. On the adoptive node, verify that the compass1 package has started:
host2# cmviewcl -v -p compass1
6. On the adoptive node, verify that the guest named compass1 is on:
host2# hpvmstatus -P compass1
11.3.7 Managing Distributed Guests
To start, stop, and monitor distributed guests, use the Serviceguard commands described in this
section. Do not use the Integrity VM commands (hpvmstart, hpvmstop, and hpvmmigrate)
to manage distributed guests.
11.3.7.1 Starting Distributed Guests
To start a distributed guest, enter the following command:
# cmrunpkg guest-name
11.3.7.2 Stopping Distributed Guests
To stop a distributed guest, enter the following command:
# cmhaltpkg guest-name
11.3.7.3 Monitoring Distributed Guests
To monitor the distributed guest, enter the following command:
# cmviewcl -v -p guest-name
11.3.7.4 Modifying Distributed Guests
You can modify the resources for the distributed guest using the hpvmmodify command.
However, if you modify the guest on one VM Host server, you must make the same changes on
the other nodes in the multiserver environment.
After you modify vswitches, logical volumes, or file backing stores used by distributed guests,
make sure that Serviceguard can continue to monitor the guests. Run the hpvmsg_package
script and restart the guest packages to update the Serviceguard information.
11.3.8 Monitoring Network Connections
The vswitch monitor runs the vswitchmon script on the VM Hosts in the multiserver environment
and monitors the Serviceguard Network Manager by monitoring the syslog.log file. When
it detects that Serviceguard is failing over a primary network to a standby network, the vswitch
monitor halts, deletes, creates, and boots the vswitch associated with the primary network onto
the the standby network. When the primary network is restored, Serviceguard and the vswitch
monitor move the network and associated vswitch back to the primary network.
11.4 Upgrading from the Integrity VM A.01.20 Toolkit
If the Integrity VM A.01.20 Serviceguard for Integrity VM Toolkit is installed, remove the Integrity
VM A.01.20 toolkit before installing the current version of Integrity VM. After you install Integrity
VM, repackage the distributed guests, as described in this section.
To upgrade to the current version of Integrity VM, perform the following sequence of steps on
each VM Host node in the multiserver environment:
11.4 Upgrading from the Integrity VM A.01.20 Toolkit 163