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

The -e and the -E options are mutually exclusive.
NOTE: If you change from -E cycles to -e percent on a
guest that previously had a maximum configured and do
not specify a maximum, then the default maximum value
is chosen.
-F
Suppresses all resource conflict checks and associated
warning messages (force mode). Force mode is provided
for scripts and other noninteractive applications. Note that
you will receive no notification of potential resource
problems for a virtual machine modified with the -F
option.
The -F and -s options are mutually exclusive.
-i package-name
Specifies whether the virtual machine is managed by
Serviceguard or gWLM (or both). For the argument, specify
the Serviceguard package name or gWLM, both, or NONE.
This option is used by Integrity VM software; do not use
this option without explicit instruction from HP.
-j {0 | 1}
Specifies whether the virtual machine is a distributed guest
(that is, managed by Serviceguard and can be failed over
to another cluster member). This option is used by Integrity
VM software; do not use this option without explicit
instruction from HP.
-l vm-label
Specifies a descriptive label for the virtual machine, which
can be useful in identifying a specific virtual machine in
the hpvmstatus verbose display. The label can contain
up to 256 alphanumeric characters, including A-Z, a-z, 0-9,
the dash (—), the underscore (_), and the period (.). To
specifiy white space, the label must be quoted (" ").
-B start-attr
Specifies the startup behavior of the virtual machine. The
start_attr argument can have the following
(case-insensitive) values:
auto: Automatically start the virtual machine when
Integrity VM is initialized on the host.
manual: Manually start the virtual machine.
If the start_attr attribute is set to auto, the virtual machine
is started when Integrity VM is initialized. This is the
default. This occurs when the VM Host system is booted,
and when the Integrity VM software is stopped and
restarted on a running VM Host. For example, when you
upgrade Integrity VM to a new version on a running
system, the software is started automatically. The VM Host
attempts to start all virtual machines for which the attribute
is set to auto. If insufficient resources exist, some virtual
machines might fail to start.
If the attribute is set to manual, the virtual machine does
not start automatically when Integrity VM is initialized on
the VM Host. The virtual machine can then be started
manually with the hpvmstart command or through its
virtual console.
271