Remember:  A software appliance that is deployed in a Secure Service Container runs in a  dedicated LPAR. When activated, it reduces the maximum number of available LPARs by  one. z14 ZR1 servers use separate PU pools for each optional PU type. The separate  management of PU types enhances and simplifies capacity planning and management of the  configured LPARs and their associated processor resources. The supported operating systems are listed in Table 7-3 on page 214 and Table 7-4 on  page 216. Planning an LPAR configuration includes defining reserved PUs that can be brought online  when extra capacity is needed. Operating system support is required to use this capability  without an IPL; that is, nondisruptively. This support is available in z/OS for some time. The dynamic PU add function enhances this support by allowing you to dynamically define  and change the number and type of reserved PUs in an LPAR profile, which removes any  planning requirements. The new resources are immediately made available to the operating  system and in the case of z/VM, to its guests. The supported operating systems are listed in Table 7-3 on page 214 and Table 7-4 on  page 216. An LPAR can be defined with an initial and a reserved amount of memory. At activation time,  the initial amount is made available to the partition and the reserved amount can be added  later, partially or totally. Although these two memory zones do not have to be contiguous in  real memory, they appear as logically contiguous to the operating system that runs in the  LPAR. z/OS can take advantage of this support and nondisruptively acquire and release memory  from the reserved area. z/VM can acquire memory nondisruptively and immediately make it  available to guests. z/VM virtualizes this support to its guests, which now also can increase  their memory nondisruptively if supported by the guest operating system. Releasing memory  from z/VM is not supported. Releasing memory from the z/VM guest depends on the guest’s  operating system support. Separate LPAR management of PUs Dynamic PU add Dynamic LPAR memory upgrade LPAR group absolute capping Linux on Z also supports acquiring and releasing memory nondisruptively. This feature is  enabled for SUSE Linux Enterprise Server 11 and RHEL 6 and later releases and for  supported Ubuntu versions. On z13s servers, PR/SM is enhanced to support an option to limit the amount of physical  processor capacity that is used by an individual LPAR when a PU that is defined as a CP or  an IFL is shared across a set of LPARs. This enhancement is designed to provide a physical  capacity limit that is enforced as an absolute (versus a relative) limit. It is not affected by  changes to the logical or physical configuration of the system. This physical capacity limit can  be specified in units of CPs or IFLs. The supported operating systems are listed in Table 7-3 on page 214 and Table 7-4 on  page 216. Chapter 7. Operating system support  229