Restrictions and limitations in the WPAR environment

Edit online

This section lists the restrictions and limitations in the WPAR environment.

The following functionality is unavailable within a WPAR:

  • PowerHA SystemMirror
  • RSCT
  • NFS server
  • WLM controls
  • WPAR management
  • Kernel tuning
  • AutoFS must not be used in a WPAR because it might prevent the WPAR from stopping cleanly.
  • Running the halt -q command inside a WPAR is expected to stop the WPAR and bring it to a defined state. Because of a timeout condition and delays while unmounting the file systems, the WPAR might not stop cleanly, which leaves the WPAR in transition state.
Consider the following restrictions when creating WPARs:
  • WPAR partitions are not supported on thin servers (diskless and dataless systems that are not capable of starting and running without the assistance of servers on a network).
  • WPAR input parameters must consist of upper or lower case ASCII letters, numbers, and underscores (_). This includes the following WPAR variables:
    • WPAR name
    • WPAR password
    • WPAR paths
    • WPAR application
    • WPAR hostname
  • If a WPAR is configured to have writable, non-shared /usr and /opt filesystems, the AIX® system software within that WPAR cannot be directly managed from within the WPAR. Operations that are prevented on system software include apply, commit, deinstall, and reject. If it is necessary to modify system software within a non-shared WPAR, use the /usr/sbin/swvpdmgr -w <fileset_names> command to allow those file sets to be directly managed within the workload partition.