Configuring and Migrating Memory on vPars

17
the user has already explicitly bound 512 MB of address range as base and 512 MB
of address range as floating.
3. When the partition is live, add or delete of a user specified range results in an increase or
decrease of memory that the partition owns. In the example above, if vpar1 is live, at the end
of the operation vpar1 will own 1.5 GB of base and 1.5 GB of floating ILM.
4. When a partition is down, the partition should contain enough unbound memory of that type
(base or floating ILM or CLM) before a range can be added. In the above example, assuming
vpar1 is in down state, the range add will fail, if the size of the base or floating range exceeds
1 GB as that is more than the 1 GB of base or floating allocated to the partition. If another
command is issued in the above example to add a range, the size of the base or floating range
cannot exceed 512 MB because that is the amount of base or floating ILM that is not yet
bound.
5. When a partition is down or belongs to a non-live database, the allocated memory of a given
type cannot go below the sum of the address ranges. In the above example, a command to
delete memory as given below fails because deleting 768 MB of floating ILM memory takes the
allocated floating ILM to 256 MB which is less than the 512 MB address range bound to the
partition.
# vparmodify –p vpar1 –d mem::768:f
6. When a partition belongs to a live database, there should be valid memory within the specified
range. A range cannot overlap a memory hole.
7. User specified ranges should be deleted only by using the delete range option. There is an
exception to this rule:
During boot, the HP-UX kernel might convert any floating granule to base granule (as
described in Memory Granules chapter). Similarly during delete from a live partition, the
HP-UX kernel might select any floating granule to optimize the deletion time. If the floating
granule that was selected by the HP-UX kernel belongs to a user specified floating range,
the vPars monitor deletes the user specified floating range and the explicit binding between
the granules and the partition. The granules will still be part of the partition as monitor-
bound granules.
8. The vPars software does not validate the range for valid memory or type of memory while
adding to a non-live database. Hence, the system administrator should ensure that the target
system contains valid memory of that type within the specified end points. During monitor boot,
the requested range is deleted if there is no valid memory within the range or if the addition of
the range results in the amount of bound base or floating ILM or CLM to exceed the amount of
base or floating ILM or CLM that has been allocated. In the above example, if there is no valid
memory at address 0x20000000, the first range is deleted. If the memory at address
0x100000000 belongs to cell 0, the second range is deleted because no CLM from cell 0 is
allocated to the partition.