|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management Oracle Solaris 11 Information Library|
Because zones do not nest, the P2V process makes any existing zones inside the migrated system image unusable in the destination zone. Existing non-global zones on the source system must be migrated before you migrate the global zone's system image.
An existing Oracle Solaris 11 system can be directly migrated into a solaris brand zone on an Oracle Solaris 11 system. Use the zonep2vchk and zfs commands on the source system to prepare for migration and archive the system image. Use the zonecfg and zoneadm commands to configure and install the archive in the destination zone on the target system.
The following restrictions apply to migrating a global zone to a non-global zone:
The global zone on the target system must be running the same Oracle Solaris 11 release as the original source host.
To ensure that the zone runs properly, the target system must have the same or a later version of required operating system packages. Other packages, such as packages for third-party products, can be different.
source# zonep2vchk -b 11
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 configuration based on the physical resources and networking configuration of the source host.
Archive the file systems in the global zone. Verify that no non-global zones are installed on the source system. Multiple archive formats are supported including cpio, pax archives created with the -x xustar (XUSTAR) format, and zfs. The examples in this section use the zfs send command for creating archives. The examples assume the root pool is named rpool.
source# zfs snapshot -r rpool@p2v
source# zfs destroy rpool/swap@p2v
source# zfs destroy rpool/dump@p2v
source# zfs send -R rpool@p2v | gzip > /net/somehost/p2v/s11-zfs.gz
source# zfs send -rc rpool@p2v
The template zonecfg script generated by the zonep2vchk tool defines aspects of the source system's configuration that must be supported by the destination zone configuration. Additional target system dependent information must be manually provided to fully define the zone.
The configuration file is named s11-zone.config in this procedure.
target# less /net/somehost/p2v/s11-zone.config
The initial value of zonepath in this script is based on the host name of the source system. You can change the zonepath directory if the name of the destination zone is different from the host name of the source system.
Commented-out commands reflect parameters of the original physical system environment, including memory capacity, number of CPUs, and network card MAC addresses. These lines may be uncommented for additional control of resources in the target zone.
target# dladm show-link target# dladm show-physical target# ipadm show-addr
By default, the zonecfg script defines an exclusive-IP network configuration with an anet resource for every physical network interface that was configured on the source system. The target system automatically creates a VNIC for each anet resource when the zone boots. The use of VNICs make it possible for multiple zones to share the same physical network interface. The lower-link name of an anet resource is initially set to change-me by the zonecfg command. You must manually set this field to the name of one of the data links on the target system. Any link that is valid for the lower-link of a VNIC can be specified.
target# cp /net/somehost/p2v/s11-zone.config .
target# vi s11-zone.config
target# zonecfg -z s11-zone -f s11-zone.config
This example does not alter the original system configuration during the installation.
target# zoneadm -z s11-zone install -a /net/somehost/p2v/s11-zfs.gz -p