HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration
8 logical processors (2 per socket)
Vendor identification: GenuineIntel
Processor version info: 0x0000000020000704
Family 32, model 0, stepping 7
Processor capabilities: 0x0000000000000005
Implements long branch
Implements 16-byte atomic operations
. . .
10.3.1.2 Private Network Setup
Source and target VM Host systems should be connected with a dedicated, high-speed private
network. To use the private network during a migration, specify the name of the private network
connection in the hpvmmigrate -h option. As a helpful convention, if you specify a simple
non-qualified host name, the hpvmmigratecommand appends -hpvm-migr to the name and
checks if a host alias has been defined for a private network corresponding to the simple name.
If so, that host-alias is used (that is, host-hpvm-migr is used instead of host.).
To set up a private network between two systems, identify which physical network interfaces
are to be used for the private network. Then connect those ports to the same network switch, or
cable them directly to each other with a cross-over cable if these two VM Host systems are the
only two systems that will migrate guests. Also, BladeSystems in the same enclosure can be
connected directly together without an external switch or cable.
Assign private network IP addresses to those interfaces by editing /etc/hosts, /etc/
nsswitch.conf and /etc/rc.config.d/netconf on each host. Private (non-routable) IP
addresses in the range of 10.0.0.0 to 10.255.255.255 are good choices to use. (See the chapter on
"Network Addressing in the current version of the HP-UX LAN Administrator’s Guide for assistance
with subnetworking configuration: http://docs.hp.com/en/5991-7412/5991-7412.pdf).
In the following example, VM Host system host2 is using network interface lan3 as its private
network to connect to VM Host host1:
Address aliases from/etc/hosts on the host1 and host2 systems:
127.0.0.1 localhost loopback
16.17.81.141 host1 host1.alg.hp.com
16.17.81.142 host2 host2.alg.hp.com
10.3.81.141 host1-hpvm-migr
10.3.81.142 host2-hpvm-migr
Excerpt from /etc/nsswitch.confon the VM Host systems:
hosts: files dns
ipnodes: files dns
Excerpt from /etc/rc.config.d/netconf on the host2 system:
INTERFACE_NAME[3]=lan3
IP_ADDRESS[3]=10.3.81.142
SUBNET_MASK[3]=255.255.252.0
BROADCAST_ADDRESS[3]=""
INTERFACE_STATE[3]=""
DHCP_ENABLE[3]=0
INTERFACE_MODULES[3]=""
Example output from netstat on the host2 VM Host system:
# netstat -in
Name Mtu Network Address Ipkts ...
lan3 1500 10.3.80.0 10.3.81.142 1022313379 ...
lan0 1500 16.17.80.0 16.17.81.142 2420913 ...
lo0 32808 127.0.0.0 127.0.0.1 123762 ...
The hpvmmigrate command does not encrypt the guest's memory and state during the transfer
and does not check that a private network connection is being used between the source and
target VM Hosts. Because the data is not encrypted, using a private network is important for
176 Migrating Virtual Machines