HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

the hpvmmigrate command sets the guest to be runnable, it now also sets the
modify_status=enabled and visible_status=enabled attributes.
8.2.4 Cannot Distinguish Between JBOD and Remote SAN with Device Check
If your Integrity VM server has local JBOD disks configured, they appear as disks that are
SAN-resident in the Virtualization Provider making them available for guests. If your guest
configurations require only SAN-resident disks, the JBOD disks, set them as restricted disks in
the Integrity VM device database.
The following example sets the device /dev/rdisk/disk100 as a restricted device:
# hpvmdevmgmt -a rdev:/dev/rdisk/disk100
8.2.5 Unpresenting SAN Devices to Integrity VM Hosts
Unpresenting SAN devices that were configured to be used by guests causes the guest to fail to
start. If SAN devices must be unpresented, guests configured to use those devices should be
reconfigured to no longer require them. After unpresenting a device special file, remove it from
the Integrity VM Host using the following command:
rmsf –a device_special_file
The device special file can be derived from the wwid_string, obtained from the SAN appliance,
as follows:
scsimgr -p get_attr -a wwid -a device_file current all_lun | grep wwid_string
8.2.6 Changes to the hpvmstatus Command
The Runsysid column of the hpvmstatus command output has been renamed to "Rmt Host"
to help with usability. Serviceguard-packaged VMs that are "On" that are running on another
member of the cluster will have the state "On (RMT)" instead of simply "On". If a VM is not
packaged in a Serviceguard cluster, the Rmt Host column displays a dash (-) instead of a zero
(0).
The following example shows the output of the hpvmstatus command:
# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Rmt Host
==================== ===== ======= ========= ====== ===== ===== ======= ========
vm1 1 HPUX Off 2 2 2 6 GB -
vm2 2 HPUX On (RMT) 4 1 1 2 GB 3
vm3 3 HPUX On (RMT) 2 1 1 1 GB 2
vm4 4 HPUX On (OS) 4 1 1 2 GB 1
vm5 5 HPUX On (RMT) 4 9 1 2 GB 3
The hpvmstatus -V option has been modified to display the new attributes, after the "Runnable
status" and associated attributes.
Graceful stop timeout : 30
Runnable status : Disabled
Not runnable setby : Migrate
Not runnable reason : Guest has been migrated to host colonial6.
Modify status : Disabled
Not modify setby : Migrate
Not modify reason : Guest has been migrated to host colonial6.
Visible status : Disabled
Not visible setby : Migrate
Not visible reason : Guest has been migrated to host colonial6.When these attributes are enabled the string
"Enabled" will be displayed.
If you need to parse the output of the hpvmstatus command, use the -M option, which provides
output in a machine-readable format. The hpvmstatus manpage explains the -M option:
-M displays verbose attribute and resource information in machine-readable format including
information about migrating virtual machines.
148 Managing Guests