HP Integrity Virtual Machines Installation, Configuration, and Administration Version A.03.50

Some devices should be restricted to use by the VM Host 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 9.8.2.4 (page 140).
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 3-3 (page 39).
3.1.7 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 character (_), and the period (.). If white space
is desired, the label must be quoted ("").
3.1.8 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 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 initialized on the VM Host. 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.
The following command clones the VM oldvm, creating a new VM named newvm:
# hpvmclone -P oldvm -N newvm -b disk:scsi:0,1,2:file:/hpvm/newvm/diskA
The -b option copies the contents of oldvm virtual disk with bus, device, target triple of 0,1,2 to
the file /hpvm/newvm/diskA. The boot options for the new VM are automatically modified to
use the specified disk as its boot disk. The following command, which refers to the device listing
for oldvm, copies the contents of /hpvm/oldvm/disk0 to /hpvm/newvm/diskA:
# hpvmstatus -P oldvm -d
[Virtual Machine Devices]
[Storage Interface Details]
disk:scsi:0,1,2:file:/hpvm/oldvm/disk0
disk:scsi:0,0,1:file:/hpvm/oldvm/disk1
[Network Interface Details]
network:lan:0,1,0xDAA9A3B92227:vswitch:vswB
[Misc Interface Details]
serial:com1::tty:console
3.1 Specifying Virtual Machine Characteristics 37