HP Integrity Virtual Machines Installation, Configuration, and Administration

Table 3-5 Options to the hpvmclone Command (continued)
DescriptionOption
Specifies a user authorization. The specified administrative level (admin or
oper) is applied to the specified user group.
-u user[:{admin|oper}]
Specifies values for dynamic memory setting associated with the guest,
including:
• dynamic_memory_control
• ram_dyn_type
• ram_dyn_min
• ram_dyn_max
• ram_dyn_target_start
For more information about dynamic memory, see Section 9.6: “Dynamic
Memory” (page 120).
To specify the serial number of the new virtual machine, enter
serial_number={new | same}
To specify the serial number of the new virtual machine, enter
serial_number={new | same
-x keyword=parameter
For example, to clone the virtual machine named compass2, to create a new virtual machine
named compass5, enter the following commands. First display the current guest status on the
VM Host:
# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
compass1 2 HPUX On (OS) 1 1 1 2 GB 0
compass2 3 UNKNOWN Off 1 1 1 1 GB 0
compass3 4 HPUX Off 1 1 1 2 GB 0
You can create a clone of compass1 by entering the following command. The new virtual machine
is named clone1:
# hpvmclone -P compass1 -N clone1
To see the results of the command, enter the hpvmstatus command again:
# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
compass1 2 HPUX On (OS) 1 1 1 2 GB 0
compass2 3 UNKNOWN Off 1 1 1 1 GB 0
compass3 4 HPUX Off 1 1 1 2 GB 0
clone1 5 UNKNOWN Off 1 1 1 1 GB 0
The hpvmclone command creates a copy of an existing virtual machine and its configuration
information. This command copies the configuration files of the existing guest. It does not copy
the actual data and software associated with the guest. The clone_vm_name must not already
exist on the same VM Host.
The new virtual machine's configuration information can be modified from the original
configuration file by using command options. If no options are specified, all original parameters
are retained. This will cause resource conflicts if both the original and clone virtual machines are
booted together.
Resources are checked to determine whether the virtual machine could boot by itself on the
server. Any problems are reported as WARNINGS. These warnings will not prevent the new
virtual machine from being created. These conditions will, however, prevent the guest from
starting.
Backing storage devices (for example, directories and files) cannot be shared, and therefore they
cannot be used by two running guests at the same time. In this case, you must either enter a
3.5 Cloning Virtual Machines 41