How to Migrate a Kernel Zone by Using Warm Migration
-
Ensure that the source and target hosts meet requirements described in Kernel Zone Migration Requirements.
-
Ensure that the required services are available as described in Enabling Services for Warm or Live Migration.
-
If the source and target hosts are not identical, see About Migration and Compatible Configurations.
Example 5-13 Failed Configuration Check on Warm Migration
This example shows a migration attempt with the suspend resource on a local path.
global3$ zoneadm -z z1kz migrate ssh://global5
zoneadm: zone 'z1kz': configuration check failed: suspend path resource must be an NFS path
Example 5-14 Suspending the Kernel Zone and Warm Migrating
This example shows the commands for displaying the suspend
resource, suspending the zone, listing the zones to include the kernel zone auxiliary state which is suspended
for z2kz
, and then the successful migration of the suspended kernel zone. Issuing the uptime
command on the migrated zone on the target host shows how long it has been running, which includes time since it was booted on the source host.
global3$ zonecfg -z z2kz info suspend suspend: storage: iscsi://system/luname.naa.501337600144f0dbf8af1900 global3$ zoneadm -z z2kz suspend global3$ zoneadm list -cp 0:global:running:/::solaris:shared:-:none: -:z2kz:installed:/system/volatile/zones/z2kz/zonepath:890d94b7-23c7-48c8-922e-ede10c3d1ac6:solaris-kz:excl:-:solaris-kz:suspended global3$ zoneadm -z z2kz migrate ssh://global5 zoneadm: zone 'z2kz': Importing zone configuration. zoneadm: zone 'z2kz': Attaching zone. zoneadm: zone 'z2kz': Migration successful. global3$ ssh global5 zlogin z2kz uptime 12:02pm up 2 day(s), 2:55, 0 users, load average: 0.04, 0.04, 0.03