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

Known Problems and Workarounds
Monitor Assigns All Available ILM Memory to a Virtual Partition rather than Requested Amount
Chapter 3 29
.
[Available ILM (Base /Range)]: (bytes) (MB)
[Available ILM (MB)]: <none>
When a boot of any other partition is attempted, the boot fails because it is
unable to find any available memory:
keira1# vparboot -p keira2
vparboot: Booting keira2. Please wait...
keira1#No memory range to load kernel keira2
Error reading program segments
Failed to load (0/0/0/2/0.6.0.0.0.0.0;)/stand/vmunix
[MON] keira2 has halted.
Workaround
You can perform either one of the following workarounds:
• Bring down the partition that is causing this problem (in the above
example, this is keira1) and reduce the user-specified ranges such that
the difference between the requested ILM size and the sum of the
user-specified ranges is greater than or equal to the ILM granularity
value.
Taking the above example, vparstatus -p keira1 -v shows the
memory portion as:
[Memory Details]
ILM, user-assigned [Base /Range]: 0x4000000/256
(bytes) (MB) 0x3000000/16
0x18000000/1664
ILM, monitor-assigned [Base /Range]: (bytes) (MB)
ILM Total (MB): 1984
The requested ILM size is 1984MB and sum of the user-specified ranges
is 1936MB. The difference is 48MB. This is less than the granularity
value of 64MB.
If we reduce one of the memory ranges, for example 0x4000000/256 to
0x4000000/192, this makes the difference to be 112MB, which is more
than 64MB. This eliminates the problem, and we can boot both keira1
and keira2.
• Add another memory range to the partition that is causing the problem,
such that the difference between the requested ILM size and the sum of
the user-specified ranges becomes zero. In the above example, adding
the range 0x13c000000/48 to the partition keira1 makes the difference
to be zero and eliminates the problem.