HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

• File:
# hpvmdevmgmt -a gdev:/var/opt/hpmv/ISO-images/hpux/112350GOLD.ISO:attr:PRESERVE=YES
• VxVM volume:
# hpvmdevmgmt -a gdev:/dev/vx/rdisk/guestdg/vxvm_g2:attr:PRESERVE=YES
To remove a device from the storage pool, used the following command:
# hpvmdevmgmt -d gdev:/dev/rdisk/disk23
NOTE: Adding devices to the storage pool does not prevent them from being used by the HP-UX
operating system or other Integrity VM commands.
The storage pool does not fully support lunpaths or directories. In addition, Virtual Machine
Management (VMM), a layer between Integrity VM and LSM, has no way to insert or eject a DVD,
because this is done from the virtual console.
11.2.2 Registering and unregistering a VM
A VM is registered when it is runnable, modifiable, and visible. When a VM is not registered, it
is not visible to the graphical tools, such as LSM, and you cannot modify it or start it. When you
register a virtual machine with VMM using the hpvmmodify command, the following attributes
are set:
• runnable_status=enabled
• modify_status=enabled
• visible_status=enabled
VMM and LSM ensure that a virtual machine is registered (and, therefore, runnable) on only one
VSP at a time.
When a virtual machine is unregistered, the following attributes are set:
• runnable_status=disabled
• modify_status=disabled
• visible_status=disabled
After a migration, the hpvmmigrate command sets the virtual machine on the source host as
unregistered. The VM is marked not runnable, not visible, and not modifiable. The hpvmstatus
command lists these attributes:
# hpvmstatus -P vmname -V
When the graphical tool queries the register_status, the value of visible_status is
returned. If the VM is not visible, you cannot visualize it with the graphical tools, and therefore;
you cannot modify it or run it.
You can set the register_status of a VM to enabled or disabled with the hpvmmodify -x
register_status 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 and could cause
inconsistencies with the display of graphical tools. However, if you find that VM is not registered
on any VSP, you can manually register it with the hpvmmodify command. For information on this
command, see Table 16 (page 91).
168 Managing vPars/VMs