Creating and Administering Oracle® Solaris 11.2 Boot Environments

Exit Print View

Updated: July 2014

beadm in Non-Global Zones

    Note the following support specifications for non-global zones in the beadm command and in related processes:

  • The beadm command is supported inside a non-global zone.

  • The root dataset for non-global zones must not be under the rpool/ROOT namespace. Non-global zones are cloned or copied only when the original zone is within the shared area for the global zone, for example, within rpool/export or within rpool/zones.

  • Although the beadm command affects the non-global zones on your system, the beadm command does not display zones information. Use the zoneadm command to view changes in the zones in your boot environment. For example, use the zoneadm list command to view a list of all current zones on the system.

    For further information, see zoneadm (1M) the man page.

  • Not all of the beadm command options can be used in non-global zones. See the specific limitations for each command option in the beadm (1M) man page.