Installing Integrity VM

Install these Patches

Install the following patches, from the ITRC website (http://www.itrc.hp.com), after installing Integrity VM:

Go to the http://software.hp.com and search for the keyword avio, to download and install any AVIO web release bundles.

	NOTE: Although the installation order does not matter, Integrity VM patches and AVIO web release bundles cannot be installed using a single swinstall command.

Do not install Integrity VM V3.5 Kit on a Host Prior to HP–UX 0712

The HP Integrity VM Version 3.5 kit can be installed only onto an HP–UX 11i v2 0712 host. You must upgrade to 0712 before you upgrade to the current version of Integrity VM. Any attempt to install the Integrity VM Version 3.5 kit onto a host running any HP-UX system prior to 0712 does the following:

The swlist command also shows the Integrity VM Version 3.5 bundles T2767AC, VMGuestLib and VMKernelSW as installed after the host reboot. However, the Integrity VM Version 3.5 product does not install completely and can leave the host in an unknown state.

Integrity VM Includes the Foundation Operating Environment

The HP-UX Foundation Operating Environment (FOE) is included with Integrity VM. Install the FOE on the VM Host on which you install Integrity VM. The license for the FOE (used in the VM Host only) is included with the purchase of Integrity VM. (Licenses for OEs that run inside the individual virtual machines must be purchased separately.)

For VM Hosts that will support guests as Serviceguard packages, the Mission Critical Operating Environment (MCOE) can also be used.

Upgrade HP WBEM Services

Integrity VM fails to install if the version of WBEM Services on your VM Host is old. The VM Host system must be running HP WBEM Services A.02.00.10 or later. The HP WBEM Services for HP-UX software bundle (B8465BA) is available as part of the HP-UX operating system, or download the software from www.hp.com. This version of HP WBEM Services is also required to install VM Provider and VM Manager.

Installing the Migration Tools Including hpvmmigrate and Physical-to-Virtual Assist Tools

The VMMigrate SD-UX bundle no longer exists. The functionality delivered with this bundle is now delivered with installation of the Integrity VM bundle T2767AC. Installation of T2767AC causes the old VMMigrate bundle to be automatically removed. The functionality previously delivered with the VMMigrate bundle has been replaced by the contents of two SD-UX products within the T2767AC bundle, VMMIGRATE and VMCONVERT. The VMMIGRATE product contains the hpvmmigrate command along with its supporting tools and manual. The physical-to-virtual tools and documentation are delivered in the VMCONVERT product. These SD-UX products and others can be seen with the swlist command:

swlist -R T2767AC

The repackaging of the physical-to-virtual tools in the T2767AC.VMCONVERT product, allows them to be installed on any Integrity HP-UX 11i v2 system, not just on a VM Host or a virtual machine. This results in more practical use of the physical-to-virtual tooks enabling them on physical Integrity servers, vPars, nPars, and so on.

To install the physical-to-virtual tools on an Integrity HP-UX 11i v2 system, enter the following command:

# swinstall -s <path to Integrity VM install media> T2767AC.VMCONVERT

This installs only the physical-to-virtual tools without any of the other Integrity VM functionality.

	NOTE: Be sure to completely specify T2767AC.VMCONVERT, so that you do not accidentally transform your host to a VM Host that is left in an unknown state.

Installing VM Provider

To install the VM Provider bundle with the Integrity VM software on the VM Host, enter the following command:

# swinstall -x autoreboot=true -s my.server.foo.com:/depot/path T2767AC vmProvider

To install the VM Provider bundle with the Integrity VM software on the HP-UX guest, see Section :

If you install the VMProvider on either the VM Host or a guest, make sure that the system is using HP WBEM Services A.02.00.10 or higher. For example:

# swlist WBEMServices
# Initializing...
# Contacting target "alien2"...
#
# Target:  alien2:/
#

# WBEMServices                            A.02.00.11     WBEM Services CORE
 Product
  WBEMServices.WBEM-CORE                  A.02.00.11     WBEM Services CORE
 Fileset for hp Integrity servers
  WBEMServices.WBEM-CORE-COM              A.02.00.11     WBEM Services COM
 Fileset for hp Integrity servers and hp 9000 servers
  WBEMServices.WBEM-MAN                   A.02.00.11     WBEM Services MAN
 Fileset
  WBEMServices.WBEM-MX                    A.02.00.11     WBEM Services MX
 fileset

VMMGR V3.0 Does Not Support Integrity VM V3.5 AVIO Functionality

Integrity Virtual Machine Manager Version 3.0 and earlier versions do not support AVIO functionality. You can use Integrity VM Manager to view and manage virtual machines with the following restrictions:

VxVM Device Path Not Valid Error on HP-UX 0803

Installing or updating HP-UX 0803 might result in the following VxVM error:

NOTICE: VxVM vxdmp V-5-0-34 added disk array OTHER_DISKS, datype = OTHER_DISKS

VxVM vxdisk ERROR V-5-1-5433 Device disk1_p2: init failed:
        Device path not valid
       * smapi listener returned "ACTION_FAILURE" for message "CREATE_GROUP"
        The configuration process has incurred an error, would you like
        to push a shell for debugging purposes? (y/[n]):

This error is caused by a 32–byte VxVM length limitation on disk device ID information. Integrity VM virtual disks report back a standard T10 device ID created with the 8–byte T10 HP identifier followed by a null terminated string of the backing store name. For example, the resource statement, "disk:scsi::lv:/dev/vx/rdsk/lvrackA/disk1", results in the T10 device ID, "HP /dev/vx/rdsk/lvrackA/disk1". Therefore, to avoid this error, the length of the backing store must not exceed 23 characters.

HP-UX Patches Required in the VM Host

Table 2-1 lists the patches that are required in the VM Host system running Integrity VM A.01.00 and later. For patches required for earlier versions of Integrity VM, consult the Release Notes document for that version. For the most up-to-date patch list, see the HP ITRC website: http://www.itrc.hp.com.

Patches Required in the HP-UX Guest

Table 2-3 lists the patches that are required in HP-UX guests:

For more information about updates to HP-UX software, contact your HP representative or support specialist.

Table 2-4 lists patches and products that you should not install on HP-UX guests. In guests where these patches are installed, degradations and regressions have been observed.

Patches Required for Ignite/UX Servers

Table 2-5 lists the patches that are required in the Ignite/UX server:

Patches Required for Windows Guests

Table 2-6 lists the patches that are required in the guests.

Table 2-7 lists patches and products that you should not install on Windows guests.

Patches Required for Red Hat Linux Guests

Table 2-8 lists the patches that are required in the guests.

Patches Required for SUSE Enterprise Linux Guests

Table 2-9 lists the patches that are required in the guests.