|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management Oracle Solaris 11 Information Library|
To begin, examine the source system and collect needed information by using the zonep2vchk tool documented in zonep2vchk(1M) and Chapter 22, About Zone Migrations and the zonep2vchk Tool. This tool is used to assess the system to be migrated and produce a zonecfg template that includes a networking configuration.
Depending on the services performed by the original system, the global administrator or a user granted the appropriate authorizations might need to manually customize the zone after it has been installed. For example, the privileges assigned to the zone might need to be modified. This is not done automatically. Also, because not all system services work inside zones, not every Oracle Solaris 10 system is a good candidate for migration into a zone.
Note - If there are any native non-global zones on the system to be migrated, these zones must either be deleted, or be archived and moved into zones on the new target system first. For a sparse root zone, the archive must be made with the zone in the ready state. For additional information on migration, see Chapter 31, (Optional) Migrating an Oracle Solaris 10 native Non-Global Zone Into an Oracle Solaris 10 Zone. For additional information on sparse root zones, see Zones Overview in the Oracle Solaris 10 documentation.