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

hpvmmigrate(1M)
NAME
hpvmmigrate -- Migrate an active guest or an offline virtual machine to a specified VM Host.
SYNOPSIS
hpvmmigrate { -P vm-name | -p vm-number } -h target-host-alias-or-IP-addr
[-l new-vm-label ] [-N new-vm-name] [-D] [-n] [-s] [-F] [-q] [ -e percent
[:max_percent] | -E cycles[:max_cycles] ] [-c number-vcpus ] [-r amount] [-m
rsrc-with-absolute-path [-C] [-t]]... [-T] [-b] [-d]
hpvmmigrate -o { -P vm-name | -p vm-number } -h target-host-alias-or-IP-addr
[-l new-vm-label ] [-N new-vm-name] [-D] [-n] [-s] [-F] [-q] [-Q] [-w]
hpvmmigrate -o -s -h target-host-alias-or-IP-addr
hpvmmigrate -k { -P vm-name | -p vm-number } -h target-host-alias-or-IP-addr
hpvmmigrate -A { -P vm-name | -p vm-number }
hpvmmigrate -v
hpvmmigrate -H
DESCRIPTION
The hpvmmigrate command moves an online guest or an offline virtual machine from a source
VM Host to a specified target VM Host. Virtual machine can be migrated while OFF, and active
guests can be migrated while ON and running. Use the -o option to migrate running guests
online, which involves moving the virtual machine, memory and active state for a running guest.
To move a guest from a source VM Host to a target VM Host, both hosts must be configured to
allow common access to all of the required resources of the migrating guest. The guest can be
either a non-running virtual machine, offline migration, or a running guest, online migration.
Online migration enables a running guest and its applications to be moved from one VM Host
to another without service interruption. SAN storage is assumed for Online VM Migration.
The resources that are defined in the virtual machine's configuration are checked to determine
whether the migrated guest can boot on the target VM Host. If there is a problem, it is reported,
and the guest is not migrated. You can specify the -F option (force) to suppress the errors and
force the guest migration to the target VM Host.
CAUTION: Use the -F option with caution, because some errors can prevent a virtual machine
from working properly on the target VM Host.
Only superusers can execute the hpvmmigrate command. In addition, the migration of a guest
is controlled by a set of secure remote operations that must be enabled on both systems. SSH
security must be set up so that root can use the equivalent of the ssh and scp commands
between the source and the target VM Hosts without requiring passwords. The easiest way to
do this is to use the secsetup script provided by Integrity VM. Otherwise, see the HP-UX
ssh-keygen command.
If you specify the -D option, the virtual machine is deleted from the source VM Host system
after it is successfully migrated to the target VM Host. By default, however, Integrity VM retains
the virtual machine and marks it Not Runnable (NR) on the source VM Host after it is migrated
successfully to the target VM Host. Specifying a subsequent hpvmstatus command on the
source VM Host after you have migrated the virtual machine will show the state of the virtual
machine as Off (NR), that is Not Runnable on the source VM Host, because the virtual machine
is now runnable on the target VM Host.
This mechanism allows the same virtual machine to exist on multiple VM Hosts, while still
preventing accidental booting of the same virtual machine on multiple hosts simultaneously.
Each virtual machine must be runnable on only one VM Host at any given time to prevent the
possibility of two virtual machines using the same resources at the same time. Use the
263