HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

NOTE: HP does not recommend using -x
runnable_status, -x modify_status, or -x
visible_status except with extreme caution.
Integrity VM ensures that the VM is runnable only on
one VM Host at a time. Marking a VM runnable on
more than one VM Host can lead to accidentally
booting the VM on more than one VM Host.
If modify_status is disabled, the VM is most likely
running on another VM Host. Any modification made
to this VM's configuration will be lost when it is
migrated back to this VM Host.
You can enable or disable visible_status;
however, when a VM has the visible_status set
to disabled, the graphical tools will not display the
VM.
HP does not recommend using -x
register_status. 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, which could cause inconsistencies with
the display of graphical tools.
• -x sched_preference={none|cell|ilm}
where:
— none — The default preference. If your application
is predominantly CPU bound, specifying either
ilm or cell will perform the same.
— cell — The cell with the most CPU and memory
space is chosen. When that guest is active, the
scheduler then optimizes where the guest runs,
so that it can be closest to its memory.
— ilm — Indicates that guests that are larger than
any single cell and contain highly threaded
applications.
• -x migrate_copy_phase_timeout= {number
of seconds} — Specifies the maximum number of
seconds the online migration spends during the
full-copy stage. The default is 0 seconds.
• -x migrate_frozen_phase_timeout= {number
of seconds} — Specifies the maximum number of
seconds the migration spends during the freezing
stage. The default is 60 seconds.
• -x migrate_init_phase_timeout={number of
seconds} — Specifies the maximum number of
seconds the online migration spends during the
initialize phase of the migration. The default is 10
seconds.
• -x migrate_io_quiesce_phase_timeout=
{number of seconds} — Specifies the maximum
302