Installing Integrity VM

This section describes information about installing the HP Integrity Virtual Machines product and associated software on the VM Host system.

HP Integrity Virtual Machines B.04.00 is supported on HP Integrity servers or nPartitions running HP-UX 11i v3 (September 2008 0809 or later). When you upgrade or reinstall Integrity VM, guests are stopped, but they are not removed. When the new version of Integrity VM starts, the virtual machines might also start, depending on the setting of the guest boot attribute.




	NOTE: Version 4.0 of Integrity Virtual Machines requires the installation of both the HostAVIOStor and HostAvioLan bundles. Other Integrity Virtual Machines documentation may state this requirement is optional, but it is not. The VM Host system is not a general-purpose system; it is dedicated to the hosting of virtual machines. After you install Integrity VM, no operating system or process management reconfiguration should be performed outside those provided by the Integrity VM interfaces. Specific examples of actions that are not supported on the VM Host system include: Changing priorities or scheduling attributes of processes on the VM Host system. Modifying kernel tunables in any way.

For complete information about the requirements for installing Integrity VM, see the HP Integrity Virtual Machines Version 4.0 Installation, Configuration, and Administration manual.

Installing Integrity VM V4.0 As Independent Product Fails

If you try to install Integrity VM V4.0 independently (that is, not as part of or in conjunction with the OE), then the installation fails. There are two basic reasons for the failure:

Installing T2767BC from DVD #1 fails, because the bundle is not on DVD #1
Installing T2767BC from DVD #2 fails, because its prerequisite (VMKernelSW) is not on DVD #2.

To work around this problem, follow these steps:

Install VMKernelSW from DVD #1.
#swinstall -x autoreboot=true -s DVD #1 VMKernelSW

Install T2767BC from DVD #2.

#swinstall -x autoreboot=true -s DVD #2 T2767BC

HPVMNETINTVL No Longer Necessary

HPVMNETINTVL is no longer necessary in the /etc/rc.config.d/hpvmconf file.

Integrity VM Includes the Base Operating Environment

The HP-UX Base Operating Environment (BOE) is included with Integrity VM. Install the BOE on the VM Host on which you install Integrity VM. The license for the BOE (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 support guests as Serviceguard packages, the High Availability Operating Environment (HA-OE) 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 VMProvider and HP 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 T2767BC. Installation of T2767BC 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 T2767BC 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 T2767BC

The repackaging of the physical-to-virtual tools in the T2767BC.VMCONVERT product, allows them to be installed on any Integrity HP-UX 11i v3 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 v3 system, enter the following command:

# swinstall -s path to Integrity VM install media T2767BC.VMCONVERT

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




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

Installing VMProvider

To install the VMProvider 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 T2767BC vmProvider

To install the VMProvider 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

Limitations When using Integrity VM Manager with Integrity VM V4.0

Integrity Virtual Machines Manager (VMMgr) Version 3.5 can be used with Integrity VM V4.0. Earlier versions of VMMgr (V3.0 and earlier) do not install or run on an HP-UX 11i v3 VM Host and cannot be used with Integrity VM V4.0. Users upgrading to Integrity VM V4.0 must upgrade to VMMgr V3.5. In addition, users of HP Insight Dynamics Virtual Software Environment software versions earlier than V4.0 must upgrade to ID-VSE V4.0 (which contains VMMgr V3.5).

Because VMMgr V3.5 is designed to run on HP-UX 11i v2 with Integrity VM V3.5 or earlier, VMMgr cannot use or display information about new features in Integrity VM V4.0 or new features in HP-UX 11i v3, in particular the new agile addressing hardware paths and device files for storage devices. This means the following:

Integrity Virtual Machines Manager (VMMgr) Version 3.5 does not display or allow the setting of minimum or maximum numbers of vCPUS, the graceful stop timeout, or entitlement caps for a virtual machine. If a new entitlement is set on the Modify > Virtual Machine Entitlement dialog that exceeds the current entitlement cap when VMMgr executes the hpvmmodify command to effect the change, the command rejects the setting and issues an error message that VMMgr displays. VMMgr behaves similarly if a new number of vCPUs set on the Modify > Virtual Machine vCPU Count dialog is outside the range of the current minimum and maximum number of vCPUs.
VMMgr does not display any information about MSE group membership for the VM Host.
The limitation documented in the VMMgr V3.5 Release Notes concerning HP SecurePath virtual device files located in /hpap does not apply. HP SecurePath is not supported on HP-UX 11i v3.
Only legacy device files and hardware paths are displayed as backing device choices when adding a storage device to a new or existing VM. This dialog appears when invoking the Modify > Add Storage Device to Virtual Machine menu item and when defining virtual storage in the Create > Virtual Machine wizard. The new persistent device files and LUN hardware paths are not listed in the choices. To add a virtual storage device using a persistent device file as a backing device to a new virtual machine, use the hpvmcreate command. To add such an I/O device to an existing VM, use the hpvmmodify command.
Only legacy device files are displayed in the boxes representing physical storage devices in the rightmost column of the Storage tabs appearing in the Manage Host or Manage VM views. Hardware paths for host bus adapters are unchanged in the new agile addressing scheme and display correctly in the boxes representing them. The new persistent device files are shown, except as described in the following list:
- If a virtual storage device is added using the hpvmcreate command or the hpvmmodify command to a virtual machine, with a persistent device file specified as the backing device, VMMgr displays the backing device on the Storage tabs with the correct persistent device file shown, but displays an icon indicating an unknown device. In addition, VMMgr is unable to link the virtual device to a physical storage device.
- If a physical storage device is marked as restricted using a new persistent device file, VMMgr lists the device as a choice in the Add Storage dialog. Normally, restricted devices are excluded from this list. Although VMMgr allows this selection, and attempts to create the VM or add the storage device using the hpvmcreate command or the hpvmmodify command, the command fails because the device is restricted. The command rejects the specification and issues an error message, which is displayed by VMMgr. As a workaround, add additional restricted devices with the hpvmdevmgmt command using the legacy device files for the physical storage device. These can be determined by using the ioscan -m command. For example:
  # ioscan -m dsf /dev/rdisk/disk3
If an LVM volume group or whole-disk swap is defined using the new persistent device files, VMMgr does the following:
- Displays the disk in the Add Storage dialog as a valid choice. Disks used for LVM volume groups and whole-disk swap are normally excluded from this list; however, VMMgr allows this selection. When VMMgr attempts to create the VM or add the storage device using the hpvmcreate or the hpvmmodify command, the command rejects the specification and issues an error messages, which is displayed by VMMgr. As a workaround, manually make the disk restricted by using the hpvmdevmgmt command using the legacy device files for the disk or use legacy device files to define new whole-disk swap or volume groups. For example, if the persistent device file is /dev/rdisk/disk3, and a legacy device file corresponding to this disk is /dev/rdsk/c0t1d0, then the command would be:
  # hpvmdevmgmt -a rdev:/dev/rdsk/c0t1d0
- If a logical volume in an LVM volume group defined using the persistent device file is used as a backing device for virtual storage in a VM, VMMgr links the virtual storage device to the correct logical volume box in the middle column of the Storage tab. However, it is not able to link the logical volume box with the correct physical device used for the volume group. As a workaround, define LVM volume groups to be used as backing storage for VMs using legacy device files.
  NOTE: This issue does not occur with disks used for VxVM volume groups. VxVM does not yet completely support the new agile addressing, but that may change with future versions of VxVM.

VxVM Device Path Not Valid Error on HP-UX 0803 Guest

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 name 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.

Table 2-1 VM Host Patches

Affected HP-UX (VM Host) Version

Affected Integrity VM Version

Fix

Description/Impact

Comment

11i v2 0505 through 0509

A.01.20 or later

PHKL_33052 (11.23.0512)

FSS

This patch incorporated into 0512 update.

11i v2 0505 through 0606

A.01.20 or later

PHKL_34082 (11.23.0609)

Bug fix

Resolves panic on host.

11i v2 0512 or later

A.02.00 or later

PHNE_33724 (11.23.0706)

Bug fix

Fixes a problem of a panic on the VM Host. Likely only on Integrity VM V2.0 as HP-UX guests in V1.0 do not do what the Windows guests do in V2.0 (ping the guest).

11i v2 0505 or later

A.02.00 or later

PHNE_34474

Bug fix

Required when using linkloop over VLANs between guest and VM Host VLAN.

11i v2 0505 or later

A.01.00 or later

Cimserver 02.00.09

PHSS_34429

Bug fix

Resolves potential corruption of guest configuration, cimserver, or other WBEM files when under extreme load. Download HP WBEM Services for HP-UX Product Bundle B8465BA from the HP software depot.

11i v2 0505 thru 0606

A.02.00 or later

PHKL_33604 (11.23.0609)

PHKL_33605 (11.23.0609)

FSS

Must install PHKL_33605 before PHKL_33604.

11i v2 0512 thru 0606

A.01.00 or later

PHKL_33827 (11.23.0609)

Bug fix

Resolves panic on guest. Specific to EVA8000 environment. (corrected to be Host patch, not guest)

11i v2 0505 or later

A.01.00 or later

PHKL_34278

Bug fix

Resolves panic and system hang symptoms

11i v2 0505 or later

A.01.00 or later

PHNE_35182

Bug fix

Cumulative ARPA transport patch, resolves panic. Requires prerequisite PHNE_32277.

11i v2 Intel Itanium 9000 (Montecito)

A.01.20 or later

HPVM A.02.00 11.23.0609 HWE

Montecito HW support

HPVM V2.0 or later is strongly recommended for use with Intel Itanium 9000-based systems. See the support statement at: http://wtec.cup.hp.com.

11i v2 0505 or later

A.01.20 or later

PHSS_35863 (Serviceguard A.11.16)

PHSS_35427 (Serviceguard A.11.17)

Bug fix

Specific to Serviceguard. If Serviceguard is running on a node with only one CPU, threads can get blocked, and the node will TOC. This happens only on nodes with a single CPU and pthreads patch installed (PHCO_34944, or later). Nodes with more than 1 CPU will not see this problem.

11i v2 0706 or later

A.03.00

PHSS_36737

Bug fix

Dynamic memory expansion might fail on guest running on 11.23.0706 host.

11i v2 0505 to 0706

A.03.50

PHNE_36839

Bug fix

DLPI is modified to pre-enable network performance enhancements.

11i v2 0712

A.03.50

PHSS_37312

Bug fix

Mandatory Integrity VM patch

11i v2 0712

A.03.50

PHSS_37306

Bug fix

Mandatory Integrity VM patch

11i v2 0505 or later

A.03.00 or later

PHSS_36997 (Serviceguard A.11.18)

Bug fix

Serviceguard support for 11i v2.

11i v2 0712

A.03.50

PHSS_37845

Bug fix

Enables users to create Red Hat 4.6 guests.

11i v3 0809

B.04.00 or later

PHKL_38038

Bug fix

64K base page size

11i v3 0809

B.04.00 or later

PHNE_36857

Bug fix

Network stack (VIO)

11i v3 0809

B.04.00 or later

PHKL_38025

PHKL_38035

PHKL_38055

PHKL_38089

Bug fix

RUC support

11i v3 0809

B.04.00 or later

PHKL_38079

Bug fix

Per-CPU capping

Table 2-2 Do Not Install Product or Patch

Affected HP-UX Host Version	Affected Integrity VM Version	Fix	Description/Impact	Comment
11i v2 0505 or later	A.02.00 or later	PHNE_35793	igelan patch	An Integrity VM guest that uses a virtual interface that belongs to an IGELAN interface configured on the Integrity VM Host can experience hangs with network services like ping, NFS, rcp, ftp for data transfers that use full-sized frames.

Patches Required in the HP-UX Guest

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

Table 2-3 HP-UX Guest Patches

Affected Guest OS and Version

Affected Integrity VM Version

Fix

Description/Impact

Comment

11i v2 0505

A.01.00 or later

U320 SCSI MPT driver version B.11.23.03, bundle A7173A

Includes fixes for performance and stability.

MPT driver update. This patch is included in the 0512 update.

11i v2 0505 or later

A.01.00 or later

PHKL_34278

Bug fix

Resolves panic and system hang symptoms.

11i v2 0505 through 0606

A.01.00 or later

PHKL_34589 (11.23.0609)

Bug fix

Resolves panic on guest.

11i v2 0505 or later

A.01.20 or later

PHKL_34540 (11.23.0609 HWE)

PHKL_34336 (11.23.0606)

PHKL_34928 (11.23.0609)

Fix to allow sharing of idle CPU cycles between guests.

Ensure loaded when using 0606 and later. Must be manually installed if feature 11i is not installed. Without this patch, Integrity VM might not detect guest is idle and not share resources, heavily impacting performance.

11i v2 0505 through 0606

A.01.00 or later

PHKL_33823 (11.23.0609)

Bug fix

Resolves panic on guest.

11i v2 0505 or later

A.02.00 or later

PHSS_34760

Serviceguard Monitor fix

Required for running in Serviceguard 11.16 environment.

11i v2 0505 or later

A.02.00 or later

PHSS_34337

Serviceguard Monitor fix

Required for running in Serviceguard 11.17 environment.

11i v2 0505 or later

A.01.00 or later

Cimserver 02.00.09 (PHSS_34429)

Bug fix

Resolves potential corruption of guest configuration, cimserver, or other WBEM Services files when under extreme load.

11i v2 0505 or later

A.01.00 or later

PHNE_35182

Bug fix

Cumulative ARPA transport patch, resolves panic. Requires prerequisite PHNE_32277.

11i v2 Intel Itanium 9000 (Montecito)

A.01.20 or later

HPVM A.02.00 11.23.0609 HWE

Intel Itanium 9000 hardware support

Integrity VM V2.0 or later is strongly recommended for use with Intel Itanium 9000-based systems. See the support statement at http://wtec.cup.hp.com/

11i v2 0505 or later

A.01.20 or later

PHSS_35863 (Serviceguard A.11.16)

PHSS_35427 (Serviceguard A.11.17)

Bug fix

11i v3

A.03.00

PHKL_36261

PHKL_36242

Bug fix performance

Without these patches, 11i v3 guest performance is severely impacted when running applications that continually spawn a large number of short-lived processes (that is, a software build environment).

11i v2 0505 or later

A.03.00

PHSS_36997 (Serviceguard A.11.18)

Bug fix

Serviceguard 11.18 support for 11i v2.

11i v3

A.03.00

PHSS_36998 (Serviceguard A.11.18)

Bug fix

Serviceguard 11.18 support for 11i v3.

11i v2 0505 or later

A.03.50

PHNE_35765

Bug fix

Fixes NAT consumption panic.

11i v2 0505 through 0706

A.03.50

PHCO_37038 (11.23.0712)

Bug fix

Fixes mkboot command with AVIO.

11i v2 0505 or later

A.03.50

PHCO_36563

Bug fix

SAM-NNC support in the guest for Integrity VM V3.5 AVIO support.

11i v3 0703

A.03.50

PHKL_36009 (11.31.0709)

Bug fix

Fixes panic caused by failure to allocate alias page table entry.

11i v2 0505 through 0706

A.03.50

PHKL_37091 (11.23.0712)

Bug fix

Fixes EFI bootpath with AVIO.

11i v3

A.03.50

PHSS_37843

Bug fix

11i v3 LR through 0709

B.04.00 or later

PHKL_37453 (11.31.0803)

edisk cumulative patch

VIO/AVIO storage

11i v3 LR through 0709

B.04.00 or later

PHKL_37454 (11.31.0803)

esctl cumulative patch

VIO/AVIO storage

11i v3 LR through 0709

B.04.00 or later

PHCO_37483 (11.31.0803)

scsimgr cumulative patch

VIO/AVIO storage

11i v3 LR

B.04.00 or later

PHCO_36371 (11.31.0709)

olrad(1m) cumulative patch

AVIO network

11i v3 LR

B.04.00 or later

PHKL_36332 (11.31.0709)

Cumulative GIO

AVIO network

11i v3 LR

B.04.00 or later

PHKL_36387 (11.31.0709)

MCA recovery and DLKM stacktrace updates

AVIO network

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.

Table 2-4 Do Not Install Products or Patches on HP-UX Guests

Affected Guest OS and Version

Affected Integrity VM Version

Fix

Description/Impact

Comment

HP–UX 11i v2 0505 or later

A.01.00

A.01.20

PHKL_33361

Cumulative kernel SCSI patch

Resolved in Integrity VM A.02.00 and later.

HP–UX 11i v2 0505 or later

A.01.00

A.01.20

A.02.00

PHKL_35739

PHKL_35891

VxVM 4.1 Kernel Patch 04 or 05

Installing VxVM 4.1 Kernel Patch 04 onto HP-UX 11i v2 guest with VxVM boot disk results in an unbootable system. Resolved in Integrity VM V3.0.

Patches Required for Ignite/UX Servers

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

Table 2-5 Ignite/UX Patches

Affected OS and Version	Affected Integrity VM Version	Fix	Description/Impact	Comment
HP-UX 11.00	A.01.00 or later	PHNE_25355	tftpd
HP-UX 11.11	A.01.00 or later	PHNE_32825	tftpd

Patches Required for Windows Guests

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

Table 2-6 Windows Patches

Affected Guest OS and Version	Affected Integrity VM Version	Fix	Description/Impact	Comment
Windows Server 2003	A.02.00 or later	SSM 4.6	Bug fix	Microsoft patches correct a compiler issue that can affect Windows guests in various ways.

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

Table 2-7 Do Not Install Products or Patches on Windows Guests

Affected Guest OS and Version

Affected Integrity VM Version

Fix

Description/Impact

Comment

SSM 4.5

SSM 4.6

Intel Itanium 9000 (Montecito)

A.02.00

PalHaltLightRegEdit component

Idle detection

See Section : “Running Windows Guests on a Dual Core Intel Itanium Processor (Montecito) System”

Patches Required for Red Hat Linux Guests

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

Table 2-8 Red Hat Linux Patches

Affected Guest OS and Version

Affected Integrity VM Version

Fix

Description/Impact

Comment

RHEL4U4 through U5

A.03.00

or later

SGLX_00190 (Serviceguard or Linux A.11.18.02)

Bug fix

Serviceguard on Linux SG A.11.18.02

Patches Required for SUSE Enterprise Linux Guests

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

Table 2-9 SUSE Enterprise Linux Guests

Affected Guest OS and Version	Affected Integrity VM Version	Fix	Description/Impact	Comment
SLES10U1	A.03.50	SGLX_00196 (Serviceguard or Linux A.11.18)	Bug fix	Serviceguard on Linux SG A.11.18.02

Installing Integrity VM

Technical documentation

» Table of Contents

» Index

Installing Integrity VM V4.0 As Independent Product Fails

HPVMNETINTVL No Longer Necessary

Integrity VM Includes the Base Operating Environment

Upgrade HP WBEM Services

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

Installing VMProvider

Limitations When using Integrity VM Manager with Integrity VM V4.0

VxVM Device Path Not Valid Error on HP-UX 0803 Guest

HP-UX Patches Required in the VM Host

Patches Required in the HP-UX Guest

Patches Required for Ignite/UX Servers

Patches Required for Windows Guests

Patches Required for Red Hat Linux Guests

Patches Required for SUSE Enterprise Linux Guests