The following sections describe release notes for Linux guests.
SLES10 SP1 Guests Supported on Integrity Servers |
 |
SLES10 SP1 guests are supported on all Integrity servers except
the following:
HP Integrity rx1600 server
HP Integrity rx2600 server
HP Integrity rx5600 server
Before Installing the SUSE Linux Guest |
|
You must install the tog-pegasus RPM kit prior to installing
the SUSE Linux RPM guest; however, the SUSE Linux installation media
does not contain the tog-pegasus RPM kit. This RPM kit is available
in the “HP Integrity Essentials Foundation Pack for Linux”
(also known as HPIEFL for Linux).
The SUSE Linux RPM guest kit is actually two parts, a guest
kit and a provider kit. The Hpvm.*.rpm kit contains:
The Hpvmprovider.*.rpm kit contains the VMprovider
and related files. This RPM requires that both the hpvm and tog-pegasus
kits must be installed.
http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T2387AA
The information you need is provided in Chapter 5 of the HP Integrity Essentials Foundation Pack for Linux User's Guide.
To download the HPIEFL for Linux kit, click the link http://www.hp.com/go/integritylinuxessentials listed in Chapter 5, then click Download for HP Integrity
Essentials Foundation Pack for Linux link on this website.
Installing Linux Guest Management Software for the First Time |
|
The first time you install the Linux guest management software,
the following error might occur:
=== from /var/log/messages file ===
Jan 18 22:45:00 1sn000 kernel: ipmi_si: Error clearing flags: cl
=== from "dmesg" command ===
ipmi_si: Error clearing flags: cl |
You can ignore this error message.
ACPI Warnings, Errors, and Exceptions Displayed when SUSE Guest
Booted |
|
When an installed SUSE guest is booted, messages similar to
the following are displayed on the guest's console:
|
Loading processor
ACPI Error (acpi_processor-0500): Invalid PBLK length [0] [20060127]
ACPI Error (acpi_processor-0500): Invalid PBLK length [0] [20060127]
ACPI Error (acpi_processor-0500): Invalid PBLK length [0] [20060127]
ACPI Error (acpi_processor-0500): Invalid PBLK length [0] [20060127]
ACPI Warning (acpi_processor-0555): BIOS reporting wrong ACPI id for the processor [20060127]
ACPI Exception (evxface-0538): AE_BAD_PARAMETER, Removing notify handler [20060127]
ACPI Error (acpi_processor-0500): Invalid PBLK length [0] [20060127]
ACPI Warning (acpi_processor-0555): BIOS reporting wrong ACPI id for the processor [20060127]
ACPI Exception (evxface-0538): AE_BAD_PARAMETER, Removing notify handler [20060127]
ACPI Error (acpi_processor-0500): Invalid PBLK length [0] [20060127]
ACPI Warning (acpi_processor-0555): BIOS reporting wrong ACPI id for the processor [20060127]
ACPI Exception (evxface-0538): AE_BAD_PARAMETER, Removing notify handler [20060127]
ACPI Error (acpi_processor-0500): Invalid PBLK length [0] [20060127]
ACPI Warning (acpi_processor-0555): BIOS reporting wrong ACPI id for the processor [20060127]
ACPI Exception (evxface-0538): AE_BAD_PARAMETER, Removing notify handler [20060127]
ACPI Error (acpi_processor-0500): Invalid PBLK length [0] [20060127]
ACPI Warning (acpi_processor-0555): BIOS reporting wrong ACPI id for the processor [20060127]
ACPI Exception (evxface-0538): AE_BAD_PARAMETER, Removing notify handler [20060127]
ACPI Error (acpi_processor-0500): Invalid PBLK length [0] [20060127]
ACPI Warning (acpi_processor-0555): BIOS reporting wrong ACPI idfor the processor [20060127]
ACPI Exception (evxface-0538): AE_BAD_PARAMETER, Removing notify handler [20060127]
ACPI Error (acpi_processor-0500): Invalid PBLK length [0] [20060127]
.
.
.
ACPI Warning (acpi_processor-0555): BIOS reporting wrong ACPI id for the processor [20060127]
ACPI Exception (evxface-0538): AE_BAD_PARAMETER, Removing notify handler [20060127]
|
|
These warnings, errors, and exceptions occur because some optional
elements are not provided by the Integrity VM ACPI table. These messages
are printed because the SUSE startup/initialization code is trying
to reference these optional elements, particularly for configured
guest CPUs.
The messages do not impede the SUSE boot process; the boot/startup
process completes. The only known side-effect of these messages is
that there is an extra CPU created in the /proc/acpi/processor file system, which might lead to confusion as to the actual number
of CPUs configured in the guest.
HP SIM CMS Cannot Connect to SLES10 over SSH |
|
SSH password authentication is turned off by default in SLES10.
In this default setting, HP SIM CMS cannot connect to the SUSE guest.
To enable password authentication for SSH, do the following:
Login to SUSE.
Edit the /etc/ssh/sshd_config file.
Set passwordauthentication value to yes.
Restart sshd.
For more information, see Secure Shell (SSH) in HP SIM 5.x, Troubleshooting
section (page 31).
Preparing Linux Guests for VM Manager |
|
If Linux guests are to be managed by VM Manager:
Install the tog-pegasus package.
On Red Hat Enterprise Linux, modify the file /etc/Pegasus/access.conf to allow WBEM access using your
designated WBEM user name and password. Follow the steps below to
configure this file. In this example, your designated WBEM user name
is assumed to be wbemuser.
Look for the following line in this file:
-: ALL EXCEPT pegasus:wbemNetwork |
Change this line to either of the following options:
# Allow access only from user 'wbemuser':
-: ALL EXCEPT wbemuser pegasus:wbemNetwork
|
# Allow access by all users:
+: ALL EXCEPT :wbemNetwork |
Start the tog-pegasus package by executing the following command:
# /etc/init.d/tog-pegasus start |
For information on where to download the Utilization Provider
for the Red Hat Linux guest, see the VSE Management Software
Installation and Update Guide.
|
| |
|
 | NOTE: If using SUSE Linux SLES10 SP1 guests, install need the HP Integrity
Essentials Foundation Pack for Linux (HPIEFPL) Version 2.1 kit or
later to get an appropriate version of the Utilization Provider. To
get the VMProvider for the SLES10 guest, install the HPIEFPL Version
2.2 kit or later or make sure you install the Integrity VM V3.5 guest
kit. For more information about obtaining the Utilization Provider,
see the HPIEFPL 2.2 Release Notes. |
|
| |
|
Linux Guests with FC Tapes Display Errors |
|
MPT errors might appear while booting a Linux guest if FC tapes
are attached to it. FC tape devices return EIO on device reset, which
causes timeout of the MPT reset. The boot proceeds after the reset
timeouts; these errors can be ignored. For example:
Use ^ and v to change option(s). Use Enter to select an option
Loading: Red Hat Enterprise Linux AS
Starting: Red Hat Enterprise Linux AS- - - - - - - - - - - -
ELILO boot: Uncompressing Linux... done
Loading initrd initrd-2.6.9-42.EL.img...done
i8042.c: i8042 controller self test timeout.
Red Hat nash version 4.2.1.8 starting
mptbase: ioc0: ERROR - Doorbell ACK timeout (count=4999), IntStatus=80000000!
mptbase: ioc0: ERROR - Doorbell ACK timeout (count=4999), IntStatus=80000000!
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
2 logical volume(s) in volume group "VolGroup00" now active
INIT: version 2.85 booting
Welcome to Red Hat Enterprise Linux AS |
Disable IPv6 on Linux Guests |
|
Integrity VM does not support IPv6 on guests. Red Hat Linux
enables IPv6 by default. When the Linux guest boots, the following
message is displayed:
printk: 1 message suppressed |
The dmesg command reports numerous duplicate address detected! messages on every IPv6
configured interface. These messages indicates an issue in the IPv6
DAD (Duplicate Address Detect) mechanism and are harmless. You can
ignore them, or you can disable them by including the following line
in the/etc/modprobe.conf file:
Infrequent “Ooops: timer ticks before it is due” Errors |
|
Infrequent Ooops: timer ticks before it is due messages appear on the console. You can safely ignore this message,
because it is harmless.
Infrequent “e1000: eth1: e1000_clean_tx_irq: Detected
Tx Unit Hang” Errors |
|
Infrequent e1000: eth1: e1000_clean_tx_irq:
Detected Tx Unit Hang messages appear on the console.
You can safely ignore this message, because it is harmless.
Inconsistent “Bogomips” Values between Virtual
CPU0 and Other Virtual CPUs |
|
“Bogomips” values can be inconsistent between virtual
CPU0 and other virtual CPUs. This condition is harmless. To prevent
this problem, add the lpj=4000000 boot option in /boot/efi/efi/redhat/elilo.conf. For example:
# cat elilo.conf
prompt
timeout=20
default=linux
relocatable
image=vmlinuz-2.6.9-42.EL.img
label=linux
initrd=initrd-2.6.9-42.EL.img
read-only
root=/dev/VolGroup00/LogVo100
append="console=tty0 console=ttyS0 rhgb quiet lpj=4000000 |
Incorrect Display of Special Characters when Displayed Using
HP-UX Terminal |
|
The Linux Red Hat installation program does not display correctly
when run within hpvmconsole on an
HP-UX terminal. It displays accented A characters instead of boxes.
Occasional Floating-Point Assist Fault Messages. |
|
Occasional floating-point assist fault messages appear when
running Mozilla. This problem also occurs o native Integrity servers
running Linux. For more information, see the “Developer &
Solution Partner Program (DSPP)” web page on http://www.hp.com, and search for “floating-point assist fault”.
Serviceguard in VM Host Configuration |
|
The default KILLTIME of 10 seconds (in hpvmsg_stop for a legacy package) and a wait of 10 seconds (in hpvmsg_ext for a modular package) might be too aggressive in some environments
and can result in a file system corruption on Linux guests. HP recommends
that you tune this value, so that the file systems on the guests are
successfully unmounted before the guest is powered off.
Printable version
