Go to main content

Creating and Using Oracle® Solaris 10 Zones

Exit Print View

Updated: October 2017

If native Non-Global Zones Are Installed

An additional step in the P2V process occurs when there are native zones on the Oracle Solaris 10 9/10 (or later released update) source physical system. Because zones do not nest, the P2V process on these systems makes the existing zones unusable inside the branded zone. The existing zones are detected when the zone is installed, and a warning is issued indicating that any nested zones will not be usable and that the disk space could be recovered. Those zones can be migrated first using the V2V process described in Migrating an Oracle Solaris 10 native Non-Global Zone Into an Oracle Solaris 10 Zone.

If you apply the kernel patch on a system running an earlier release, apply the patch before you migrate the existing zones.