HP-UX Virtual Partitions Release Notes A.04.07 (HP-UX 11i v2) (T1335-91000, March 2010)

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
System..............: winona2
Summary:
INIT initiated
Workaround Note that in a vPars environment, when system events are reported via EMS
either from system firmware or an OS instance, the system events are decoded and reported
on all virtual partitions. The OS instance that is shown as sending the event is not necessarily
indicative of the actual virtual partition that encountered the problem. The Reporting Entity
ID is the only clue to which virtual partition reported the problem. The output will be similar
to the following:
Reporting entity ID: 6 ( Cab 0 Cell 0 CPU 6 ) (possibly from one vPar)
8