The following sections contain release notes specific to installing
HP-UX guests.
Installing the Guest Management Software |
 |
The guest management software is required on each guest. The
guest management software ensures that guests have the required patches
for optimum performance and manageability. It enables the hpvmcollect and hpvminfo commands on
the guest.
The guest management software is stored on the VM Host system
in the /opt/hpvm/guest-images directory. A subdirectory
contains the guest management software for each type of guest operating
system, as shown in the following example:
# cd /opt/hpvm/guest-images
# ls
common hpux linux windows |
To install guest management software on an HP-UX guest, select
the appropriate version of HP-UX:
11iv2 indicates HP-UX 11.23.
For HP-UX
11i v2 guests, the guest depot file:
/opt/hpvm/guest-images/hp-ux/11iv2/hpvm_guest_depot.11iv2.sd
11iv3 indicates HP-UX 11.31.
For HP-UX
11i v3 guests, the guest depot file is:
/opt/hpvm/guest-images/hpux/11iv3/hpvm_guest_depot.11iv3.sd
Before installing the guest kit (bundle HPVM-Guest), preview
the install task allowing the installation analysis. This provides
the opportunity to identify and address any warnings that might result
from this preview before proceeding with the installation. For example,
the analysis phase includes checks for installation of the appropriate
AVIO drivers on the guest. To preview the installation, use the -p option of swinstall as shown in the
following example:
swinstall -p -x autoreboot=true -s path to hpvm_guest_depot.11iv#.sd HPVM-Guest vmProvider |
You might see the following warning on an Integrity VM guest
installed on an HP-UX 11i v2 prior to December 2007:
WARNING: Recommended bundle GUESTAVIOLAN not installed on guest.
WARNING: Recommended bundle GUESTAVIOSTOR not installed on guest.
WARNING: The "checkinstall" script for "vmTools.VMTOOLS-RUN" had a
warning (exit code "2"0. The script location was
"/var/tmp/BAAa05960/catalog/vmTools/VMTOOLS-RUN/chekinstall".
* This script had warnings but the execution of this fileset
will still proceed. Check the above output from the script
for further details. |
HP-UX 11i v3 Guests Might Fail to Configure Interface Cards
Due to Lack of Memory Resources |
|
HP-UX 11i v3 guests with small memory resources (less or equal
to 2 GB RAM) might fail to configure one or more virtual interface
cards. Messages like the following might be seen on the guest console:
wsio_claim init failed isc=0xe000000109c41400 name=mpt or
igssn: The device at hardware path 0/0/1/0 failed initialization (3309).
|
The problem might occur during installation, in which case it
results in some devices not being seen by the guest.
The error messages displayed in the case of guest system installation
are as follows:
|
* Preparing to execute init...
======= 05/02/08 08:07:57 EDT HP-UX Installation Initialization. (Fri May 02
08:07:56 EDT 2008)
@(#)Ignite-UX Revision C.7.0.212
@(#)ignite/launch (opt) $Revision: 10.590.1.2 $ $Date: 2006/12/18
20:51:11 $
* Configuring RAM filesystems...
* Scanning system for IO devices...
WARNING: Could not find Q_BOOT device. Cannot determine what the boot device
was.
ERROR: Could not get io-device data (ioscan)
WARNING: Could not find source device in ioscan output. You must select from
the list of devices below to use for the source device:
index HW-path Class description
0) 120 processor Processor
1) 121 processor Processor
2) 122 processor Processor
3) 123 processor Processor
4) 124 processor Processor
5) 125 processor Processor
6) 126 processor Processor
7) 127 processor Processor
8) 0/0/0/0 ext_bus SCSI_Ultra320
9) 0/0/0/0.0x0.0x0 disk HP_Virtual_LvDisk
10) 0/0/0/0.0x2.0x0 disk HP_Virtual_FileDVD
11) 0/0/0/0.0x1.0x0 disk HP_Virtual_FileDVD
|
|
To resolve this problem, temporarily increase memory assigned
to the guest to more than 2 GB (for example 2.5 GB). Then reduce memory
back to the intended size after you reboot the guest.
Patches for HP-UX 11i v3 Guests |
|
Customers running HP-UX 11i v3 guests should install the following
patches (or their superseding patches) in each guest running HP-UX
11i v3 :
These patches prevent performance problems in environments where
applications spawn large numbers of short-lived processes (such as
development environments). To obtain these patches, contact your support
specialist or HP representative.
Do Not Run Live Kernel Debuggers Inside a Guest |
|
Do not run tools that write kernel text, such as live kernel
debuggers and performance tools such as kgmon and ktracer inside a guest. Under rare circumstances,
these tools cause the guest to panic.
Do Not Use the iomap(7) Mechanism on HP-UX
Guests |
|
The iomap(7) mechanism
allows you to map physical I/O addresses into the user process address
space. Do not use this command on HP-UX guests.
iCAP Commands Fail on HP-UX Guests |
|
iCAP is installed as part of the HP-UX OS installation. Install-time
configuration of iCAP reports failure with messages similar to the
following:
|
NOTE: Checking for partitionable system.
ERROR: Software configuration has failed. After addressing the issues
in the following output, configure this software with
'swconfig B9073BA'.
ERROR: Command not allowed to run on a Virtual Machine Guest.
ERROR: The "configure" script for "iCOD.ICOD-RUN" failed (exit code
"1"). The script location was
"/var/adm/sw/products/iCOD/ICOD-RUN/configure".
* This script had errors and the execution of this fileset
cannot proceed until the problem is fixed. Check the above
output from the script for further details.
* Running config clean command /usr/lbin/sw/config_clean.
* Summary of Execution Phase:
ERROR: Installed iCOD.ICOD-RUN,l=/,r=B.11.23.08.00.00.95
ERROR: 1 of 882 filesets had Errors.
* 881 of 882 filesets had no Errors or Warnings.
ERROR: The Execution Phase had errors. See the above output for
details. |
These startup messages in /etc/rc.log can
be disregarded.
iCAP commands cannot be used on virtual machines. iCAP commands
are designed to work on the VM Host system.
This problem is resolved in guests running HP-UX 11i v2 0706
and later.
Printable version
