How to Migrate a Kernel Zone Using Cold Migration
Ensure that the source and target hosts meet requirements described in Kernel Zone Migration Requirements.
Example 5-11 Dry Run Fails for Cold Migration Due to Local Storage
The following example shows verification that a kernel zone is not running, and then a cold migration dry run that fails because of local storage being used in the kernel zone z3kz
.
root@global3 $ zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running / solaris shared - z3kz installed - solaris-kz excl root@global3 $ zoneadm -z z3kz migrate -n ssh://global5 zoneadm: zone 'z3kz': configuration check failed: The storage property dev:/dev/zvol/dsk/rpool/VARSHARE/zones/z3kz/disk0 is not a shared storage URI.
Example 5-12 Successful Cold Migration After Configuration Change
The following example shows removal of a non-booting local storage device from the zone configuration for zone z3kz
, and then a successful migration. The zone configuration that is used comes from the migrating zone and is imported on the target host.
root@global3 $ zonecfg -z z3kz 'remove device id=1;commit;exit' root@global3 $ zoneadm -z z3kz migrate ssh://global5 zoneadm: zone 'z3kz': Importing zone configuration. zoneadm: zone 'z3kz': Attaching zone. zoneadm: zone 'z3kz': Migration successful.
If you are migrating to an earlier version of Oracle Solaris, see Clearing the pagesize-policy Property Before Migrating a Kernel Zone to an Earlier Oracle Solaris Release.