HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

the following command modifies the virtual machine named host1, adding a virtual DVD device
backed by the physical disk device /c1t1d2. The virtual hardware address is omitted and will
be generated automatically.
# hpvmmodify -P host1 -a dvd:avio_stor::disk:/dev/rdisk/disk2
You can modify storage devices while the virtual machine is running. It is not necessary to restart
the virtual machine; however, it may be necessary to re-scan for devices on the virtual machine.
Some devices should be restricted to use by the VSP and to each guest (for example, boot devices
and swap devices). Specify restricted devices using the hpvmdevmgmt command. For more
information about sharing and restricting devices, see Section 11.11.2.4 (page 192).
Any alternate boot devices should be set with the same care that you would use on a physical
system. If the primary boot device fails for any reason, a virtual machine set to autoboot attempts
to boot from devices in the specified boot order until either an option succeeds or it reaches the
EFI Shell. Make sure that any specified boot options, and the boot order, are appropriate for the
guest. For more information about the autoboot setting, see Table 14.
7.1.11 Creating virtual machine labels
The -l option specifies the label of the virtual machine. The virtual machine label is a descriptive
label unique to this virtual machine. The label 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 ("").
7.1.12 Specifying the virtual machine boot attribute
The -B option 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 is the default. This occurs when the VSP system is booted, and when the Integrity
VM software is stopped and restarted on a running VSP. For example, when you upgrade Integrity
VM to a new version on a running system, the software is started automatically. The VSP 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 initialized on the VSP. The virtual machine can then be started manually with the hpvmstart
command or through its virtual console.
This option does not set the virtual machine's console to enable booting when the virtual machine
is started. This function must be set with the virtual machine's console.
NOTE: If the start_attr attribute is set to Auto, the virtual machine also starts after you install
or upgrade Integrity VM.
In addition to automatically starting guests when Integrity VM starts, this feature also determines
a startup order to best utilize VSP processor and memory resources. On cellular systems with cell
local memory (CLM) configured, the goal is to start the guests so that CLM is utilized first. For each
guest with the start_attr attribute set to auto, the startup order is based on a memory weight
and a processor weight added together.
A rough estimate of the memory weight calculation is:
100 * guest memory size / available host memory + 2 (if the guest resources can fit into a cell's
available CLM and processors)
7.1 Specifying virtual machine characteristics 83