Because zones do not nest, the P2V process makes any existing zones insidethe converted system image unusable in the destination zone. Unified archivesbypass this limitation by using thearchiveadm create -r -zcommand. For more information, seeRecovery Archives inUsing Unified Archives for System Recovery and Cloning in Oracle Solaris 11.3.
This section provides the following information:
About Converting an Oracle Solaris System (Global Zone) Into a solaris Brand Non-Global Zone
How to Create an Archive of the System Image on a Network Device
How to Configure and Install a Migrated Zone on the Target System
An existing Oracle Solaris 11 system can be directly migrated into asolaris brand zone on an Oracle Solaris 11 system. Use the UnifiedArchivearchiveadm command on systems running Oracle Solaris 11.2 orhigher. Use legacy archives on systems running the Oracle Solaris 11 or Oracle Solaris 11.1releases.
For all systems, use thezonep2vchk command on thesource system to prepare for converting and archiving the system image. Use thezonecfg andzoneadm commands to configureand to install the archive in the destination zone on the target system.
The following restrictions apply to migrating a global zone to anon-global zone:
The global zone on the target system must be running an Oracle Solaris 11 releasethat is equal to or higher than the source system.
To ensure that the zone runs properly, the target system must have thesame or a later version of required operating system packages. Other packages,such as packages for third-party products, can be different.
For more information, see thezonep2vchk(1M),archiveadm(1M),zfs(1M),zonecfg(1M), andzoneadm(1M), andsolaris(5) man pages.
For more information, seeUsing Your Assigned Administrative Rights inSecuring Users and Processes in Oracle Solaris 11.3.
source#zonep2vchk -b
This inspects ELF binaries for system and library calls that might affectoperation inside a zone.
source#zonep2vchk -s /opt/myapp/bin,/opt/myapp/lib
source#zonep2vchk -r 2h
source#zonep2vchk -c > /net/somehost/p2v/s11-zone.config
This configuration will contain resource limits and network configurationbased on the physical resources and networking configuration of the sourcehost.
Archive the file systems in the global zone. Verify that no non-globalzones are installed on the source system. The examples in this section use thearchiveadm command for creating archives.
For more information, seeUsing Your Assigned Administrative Rights inSecuring Users and Processes in Oracle Solaris 11.3.
In this procedure, the recovery archive of the global zone is named/net/somehost/p2v/s11-zone-config.uar.
source$archiveadm create -r -z global /net/somehost/p2v/s11-zone-config.uar
See Also
The Unified Archive generated witharchiveadm containsa zone configuration that serves as a starting point for the converted zone.Additional configuration may be needed to configure the zone in a way that isoptimal for the target system. For more information, seeHow to Create a Recovery Archive inUsing Unified Archives for System Recovery and Cloning in Oracle Solaris 11.3 andthearchiveadm(1M) man page.
The templatezonecfg script generated by thezonep2vchk tool defines aspects of the source system'sconfiguration that must be supported by the destination zone configuration.Additional target system dependent information must be manually provided tofully define the zone.
In this procedure, the zone is nameds11-zone and theconfiguration file is named/net/somehost/p2v/s11-zone-config.uar.
You must also be assigned the Network Management rights profile. Theroot role has all of these rights.
For more information, seeAssigning Limited Rights to Zone Administrators.
target$zonecfg -z s11-zoneUse 'create' to begin configuring a new zone.zonecfg:s11-zone>create -a /net/somehost/p2v/s11-zone-config.uarzonecfg:s11-zone>info
zonecfg:s11-zone>set zonepath=/system/zones/%{zonename}zonecfg:s11-zone>add rootzpoolzonecfg:s11-zone:rootzpool>add storage iscsi://zfssa/luname.naa.600144F0DBF8AF19000052E820D60003zonecfg:zonename:rootzpool>endBest practice is to use ZOSS for a storage resource when configuring zonesthat were deployed using Unified Archives. SeeGetting Started With Oracle Solaris Zones on Shared Storage.
target$dladm show-linktarget$dladm show-phystarget$ipadm show-addr
By default, thezonecfg script defines an exclusive-IPnetwork configuration with ananet resource for everyphysical network interface that was configured on the source system. The targetsystem automatically creates a VNIC for eachanet resourcewhen the zone boots.
The use of VNICs make it possible for multiple zones to share the samephysical network interface. The lower-link name of ananetresource is initially set tochange-me by thezonecfg command. You must manually set this field to the nameof one of the data links on the target system. Any link that is valid for thelower link of a VNIC can be specified.
zonecfg:s11-zone>commitzonecfg:s11-zone>exittarget#
Install the zone using the Unified Archive file created on the sourcesystem. This example does not alter the original system configuration during theinstallation.
target$zoneadm -z s11-zone install -a s11-zone-config.uar