HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

11.2.3 Changes to the hpvmmodify command
The hpvmmodify -x command has been changed to allow changing the modify_status,
and visible_status, and register_status attributes with the -x option, in addition to
runnable_status.
# hpvmmodify -P vmname -x runnable_status={enabled|disabled}
# hpvmmodify -P vmname -x modify_status={enabled|disabled}
# hpvmmodify -P vmname -x visible_status={enabled|disabled}
# hpvmmodify -P vmname -x register_status={enabled|disabled}
• The runnable_status option, which already exists in Integrity VM, prevents a VM from
being started.
CAUTION: HP does not recommend using the -x runnable_status option. Integrity
VM ensures that the VM is runnable only on one VSP at a time. Marking a VM runnable on
more than one VSP can lead to accidentally booting the VM on more than one VSP.
• The modify_status option of a VM is listed in the hpvmstatus -V output. If
modify_status=disabled, you cannot modify a VM except to set
modify_status=enabled.
CAUTION: HP does not recommend using the -x modify_status option, except with
extreme caution. If modify_status is disabled, the VM is most likely running on another
VSP. Any modification made to this VM's configuration will be lost when it is migrated back
to this VSP.
• You can enable or disable visible_status with the hpvmmodify command. When a
VM has the visible_status option set to disabled, the graphical tools will not display the
VM.
CAUTION: HP does not recommend using the -x visible_status option, except with
extreme caution. Use of this option may cause inconsistencies with the display of graphical
tools and has no effect on the command-line output.
• If a VM is not registered on any VSP, you can manually register it with the hpvmmodify -x
register_status=enabled command.
CAUTION: HP does not recommend using the -x register_status option. Integrity VM
commands ensure that the VM is registered only on one VSP at a time. Registering a VM on
more than one VSP can lead to accidentally booting the VM on more than one VSP, which
could cause inconsistencies with the display of graphical tools.
The hpvmmodify command does not allow modification to guests marked
modify_status=disabled. When the modify_status=disabled attribute is set, the only
change allowed is to set the modify_status=enabled attribute. When the hpvmmigrate
command sets the guest to the NR state (runnable_status=disabled), it now also sets the
modify_status=disabled and visible_status=disabled attributes. Likewise, when
the hpvmmigrate command sets the guest to be runnable, it now also sets the
modify_status=enabled and visible_status=enabled attributes.
11.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.
11.2 VM Virtualization Provider 169