Requirements for All Kernel Zone Migration Methods

The cold, warm, and live migration methods for kernel zones all have the following requirements:

• The source and target host systems must be the same architecture family. Migrating a zone between SPARC and x86 architectures is not supported.

• Both the source and target host systems must meet the general kernel zone requirements described in Software and Hardware Requirements for Oracle Solaris Kernel Zones.

• The zone storage must be accessible by both the source and target hosts through a shared storage resource defined by an NFS, iSCSI or LU storage URI.

  For more information about NFS storage URIs, see NFS Storage URIs and Kernel Zones.

  For more information about shared storage URIs for other types of storage, see the suri(7) man page and Chapter 13, Oracle Solaris Zones on Shared Storage in Creating and Using Oracle Solaris Zones

• If you plan to use ssh to migrate, SSH public key authentication between the source and target hosts must be configured so that SSH does not require a prompt. In addition to a public key, you must configure ssh-agent to remember the public key after you remotely log in at least once to the SSH prompt. See How to Generate a Public/Private Key Pair for Use With Secure Shell in Managing Secure Shell Access in Oracle Solaris 11.4.

• The zone configuration must be compatible and consistent on both the source and target hosts. See About Migration and Compatible Configurations.

• If you want to perform warm or live migration of running kernel zones, the source and target hosts must meet additional system requirements described in Additional Requirements for Kernel Zone Warm Migration and Live Migration.

Note:

If you cannot use shared storage, you cannot use the zoneadm migrate command to migrate a zone. However, you can create a unified archive and recreate the zone from the archive on a new host system. See Using Unified Archives for System Recovery and Cloning in Oracle Solaris 11.4.