HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

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.
9.1.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 VM Host 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 source virtual machine as registered.
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 command.
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 VM Host at a time. Registering a VM
on more than one VM Host can lead to accidentally booting the VM on more than one VM Host
and could cause inconsistencies with the display of graphical tools. However, if you find that
VM is not registered on any VM Host, you can manually register it with the hpvmmodify
command. For information on this command, see Section 9.1.3.
9.1.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.
142 Managing Guests