Using Warm Migration to Migrate a Kernel Zone

You can migrate a kernel zone to another host by using the zoneadm suspend command followed by the zoneadm migrate command. This zone migration method is known as a warm migration or migrating using suspend and resume.

A warm migration does not require a full system reboot and restart of the application while the kernel zone is running.

Warm migrations require the zone configurations to be compatible on both the source and target hosts. If you create a zone configuration on the target host before migration, that configuration is used. Otherwise the configuration of the migrating zone is used.

Warm migrations require that the zone has a suspend resource configured to have shared storage accessible by both the source and target hosts. See the solaris-kz(7) man page and Chapter 13, Oracle Solaris Zones on Shared Storage in Creating and Using Oracle Solaris Zones.

The migration automatically verifies that the zone's shared storage is accessible from the target system, detaches the kernel zone on the source system, and attaches the zone on the destination system.

Note:

If you are migrating systems that are not using identical processors, before suspending, set the cpu-arch property as explained in Preparation for Migrating Kernel Zones to Systems With Different CPUs or OS Versions.

You can resume the zone manually on the target system after the migration is complete. See About Resuming a Kernel Zone After a Warm Migration for information about resuming.