HP-UX vPars and Integrity VM V6.3 Administrator Guide

The number of pFCs on the target host.◦
◦ The number of active NPIV HBAs that each of them already has.
◦ The FC connectivity of the pFCs to the FC fabric (that is, to which physical switch and
fabric they are connected).
• For each guest NPIV HBA, a HBA port on the target is selected based on the following criteria:
An attempt is made to distribute the NPIV HBAs of the guest, first across eligible HBA
cards, and then across eligible HBA ports on the target.
◦
◦ Of these, when selecting an HBA port, the first preference is for one that is connected to
the same physical switch as on the source host.
◦ Of all such eligible HBA ports, the first preference is for the one with the least number of
active NPIV HBA instances.
12.3.4.5 Using NTP on the VM guests
HP strongly recommends using NTP for OVMM environments. Each guest must include all potential
VSPs as servers in ntp.conf file so that the current local VSP can be used as a time source.
Whether migrating or not, guests must not be used as time servers. To maintain reliable time
synchronization on a guest, it might be necessary to reduce the NTP polling interval, so the guest
checks the time more frequently with the NTP server.
12.3.4.6 Marking a guest not runnable
On all VSPs that have a VM configured, the VM must be marked Runnable on only one VSP at
a time. While migrating online guests, unexpected errors or guest resets or aborts must not cause
your guest to be incorrectly marked Runnable or Not Runnable.
To verify the Runnable state of a VM, use the hpvmstatus command to see that the guest is
Runnable on only one VSP and Not Runnable on all other VSPs. If the Runnable state of a
VM is not correct on a VSP, use the hpvmmodify command to correct it.
To mark a guest Not Runnable, use the following command:
# hpvmmodify -P guestname -x runnable_status=disabled
To mark a guest Runnable, use the following command:
# hpvmmodify -P guestname -x runnable_status=enabled
WARNING! You must be careful when marking a guest Runnable when it was previously Not
Runnable. Ensure this guest is Not Runnable and definitely not actually running on any other
VSP.
12.3.5 Restrictions and limitations of online VM migration
Administrators must configure certain aspects of VSPs and guests for online migration capability.
Integration with automated workload placement, management, and load balancing tools are not
supported. More automated and more convenient management of distributed Integrity VM guests
might follow in subsequent Integrity VM releases.
A dedicated high-speed network must not be on the data center, work site, company, or “public”
LAN. Online migration can also swamp the network while a migration is in progress. Using the
site's network for migration traffic would also create peaks of network activity that might affect
network performance. Using a high-speed network is desirable to minimize guest memory transfer
time and allows your guest to migrate smoothly.
The following devices are supported for guest storage for online guest migration:
214 Migrating VMs and vPars