HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

volumes, and so forth) are collectively referred to as
"backing stores."
Integrity VM recognizes the following types of guest virtual
devices:
• Virtual DVDs, which can be backed by files in a VM
Host file system or by physical DVD drives.
• Virtual disks, which can be backed by files in a VM
Host file system, by logical volumes or by whole disks.
• Attached I/O devices (DVD, tape, changer, and other
peripheral device types).
• Attached AVIO devices (tape, changer, and burner).
• Virtual network devices, which are created using the
hpvmnet command and backed by physical LAN
cards. See the hpvmnet manpage for more information
about virtual network devices.
For information about specifying storage and network
resources for guests, see hpvmresources(5).
-i package-name
Specifies whether the virtual machine is managed by
Serviceguard or gWLM (or both). For the argument, specify
the Serviceguard package name, GWLM, both, or NONE.
This option is used by Integrity VM software; do not use
this option without express instruction by 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 express
instruction by HP.
-l vm-label
Specifies a descriptive label for this virtual machine. This
can be useful in identifying a specific virtual machine in
the hpvmstatus -V display. The label can contain up to
256 alphanumeric characters, including A-Z, a-z, 0-9, the
dash (-), the underscore (_), and the period (.). If white
space is desired, the label must be quoted ("").
-B start-attr
Specifies the startup behavior of the virtual machine. The
start_attr attribute 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 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 may fail to start.
If the attribute is set to manual, the virtual machine will
not be started automatically when Integrity VM is
256