HP-UX Virtual Partitions Release Notes (A.04.06)

• QXCR1000784543 vparstatus shows -ve cpus after vparboot -I on vpar with floater cpus.

• QXCR1000586118 Enhance vPars/iCAP to allow easier fix on non-compliant vPar database.

Known Problems and Workarounds

This section provides a list of problems and limitations known to HP at the time of publication.

If workarounds are available, they are included. For information on specific defects, see the HP

ITRC at http://itrc.hp.com.

• Virtual Partition Fails to Load after a Reboot or Issuing vparload –all

Related JAG or Patch ID Number JAGae88150

Applicable On

• vPars A.05.xx on PA-RISC

• vPars A.04.xx on PA-RISC

• vPars A.03.xx on PA-RISC

Description On PA-RISC systems, vPars that use certain host bus adapters (such as Ultra320)

for boot disks may not boot to the UP state after a reboot or after the vparload –all

command is issued.

Symptoms The virtual partitions will not boot after a reboot. One or more of the following

errors may appear in the vPars Monitor event log:

iodc_perror: dev_open/Boot device init (0x42)

iodc_perror: reinit_bootdev/Read ENTRY IO (0x44)

iodc_perror: dev_reopen/Read ENTRY IO (0x47)

iodc_perror: iodc_io_init/init module and device(0x4b)

Could not read IODC firmware for HPA <hpa>

Unknown filesystem for path <hardware path>

Workaround Manually boot the virtual partitions with the vparboot or vparload

command.

• System Activity Events Reported Through IPMI by EMS

Related Defect ID and Patch Number JAGaf62654

Applicable On

— vPars A.05.xx

— vPars A.04.xx on Integrity

— vPars A.04.xx on PA-RISC

Description In a vPars environment, system activity events are decoded and reported on

all virtual partitions. When examining any single virtual partition, this can be misleading,

such that it may appear the events occurred on the virtual partition that reported the problem.

Symptoms A virtual partition reports an event, similar to the following:

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Wed May 4 15:29:44 2005

winona2 sent Event Monitor notification information:

/system/events/ipmi_fpl/ipmi_fpl is >= 3.

Its current value is CRITICAL(5).

Event data from monitor:

Event Time..........: Wed May 4 15:29:44 2005

Severity............: CRITICAL

Monitor.............: fpl_em

Event #.............: 267