1. Creating and Using Oracle Solaris Zones
  2. About Non-Global Zone Administration
  3. Migration and Transformation of Non-Global Zones
  4. About Zone Transformations
  5. Zone Transformation Requirements for Source and Target Hosts

Zone Transformation Requirements for Source and Target Hosts

Transformation of solaris zones has the following requirements:

  • Architecture – The source and target systems must use the same instruction set architecture (ISA). For example, they must both be SPARC based systems, or must both be x86 based systems.

  • Oracle Solaris versions –The global zone on the target system must be running an Oracle Solaris release that is equal to or higher than that on the original source host.

    • Before you transform a global zone to a non-global zone, verify that the software running in the global zone is compatible with non-global zones. The zonep2vchk(8) tool evaluates a global zone's configuration before transformation to a non-global zone.

    • Before you transform a non-global zone to a global zone or kernel zone, you must ensure that the Oracle Solaris operating system versions of the source and target hosts are compatible. You do not need to check for additional compatibility. Any software running in the non-global zone can also run in a global zone or kernel zone, provided that the host systems are compatible.

  • Oracle Solaris packages – To ensure that the zone will run properly, the target system must have the same or later versions of the required operating system packages as those installed on the original source host. For example, if the source host is running a Support Repository Update (SRU), then the target must also be running that SRU or a later SRU.

    Other packages, such as those for third-party products, can be different.