HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

be allowed to deliver time (allow guests to be a time consumers). Because a VM guest never
delivers time, you do not need to configure the local clock (server 127.127.1.0) or an ntp.drift
file. So, the ntp.conf file on a VM guest should be as simple as the single line:
server <VM-HOST-SERVER-NAME> minpoll 4 maxpoll 6
After configuring the guest's /etc/ntp.conf file, assuming NTP is already enabled (that is,
the XNTPD variable in /etc/rc.config.d/netdaemons is set to 1, as in export XNTPD=1),
you can run the following commands on an HP-UX guest to sync its time with the VM Host and
restart xntpd:
/sbin/init.d/xntpd stop
/usr/sbin/ntpdate -b <VM-HOST-SERVER-NAME>
/sbin/init.d/xntpd start
NOTE: For VM guests that are on a different subnet than the VM Host, the VM Host may not
be the best source of time if there is another accurate time server available with less network
latency. In the case of different subnets, measure latency from the guest to various time servers
using the ping and traceroute commands to determine which potential time server has the
least network latency. Using the VM Host may be the best solution, but this depends on your
local network topology and the relative network distance to alternate time servers. If using an
alternate (non-VM-Host) time server appears best, it may be helpful for the alternate time server
and the VM Host to use each other for peer mutual time synchronization.
9.3.2 VM Host Requirements and Setup
The VM Hosts must be configured with Integrity VM Version 4.3 or later. All the latest HP-UX
patches required by Integrity VM, as well as any required Integrity VM patches for Integrity
VM, should be installed. Consult the most recent HP Integrity Virtual Machines Release Notes,
available from http://www.hp.com/go/virtualization-manuals, for general Integrity VM installation
details, including supported VM Host operating system versions, patches, and other system
requirements. Required patches are available on the http://www.itrc.hp.com website.
9.3.2.1 VM Host Processors for Online Migration
VM Hosts can be different Integrity server models with different numbers of processors, different
I/O adapters and configurations, different amounts of memory, different firmware revisions,
and so on. In particular, guests can migrate between radically different size, capacity, and power
VM Hosts. However, for online migration, all the eligible VM Host servers in a group must have
equivalent architecture implementations. They must all report the same processor family output
for the HP-UX command machinfo -v. Different processor frequencies and cache sizes are
supported for Online VM Migration. Table 9-4 lists the recent Itanium processors showing
different values for processor family:
Table 9-4 Itanium Processor Families
SeriesModelFamily
Itanium 2031
Itanium 2131
Itanium 2231
Itanium 9000032
Itanium 9100132
Look for identical processor Family as shown in the following example output from the
machinfo -v command. (As more processors families and models are added, more specific
capability requirements might be necessary.) The systems host19 and host20 in this example
are compatible for migration, because they have the same processor family (32).
9.3 VM Host and Virtual Machine Configuration Considerations 187