About Resuming a Kernel Zone After a Warm Migration
The migrated zone might fail to boot if the zone configuration on the source system was modified after the zone was suspended or halted. Also, live zone configuration changes might have been made to the running zone before it was suspended that are not reflected in the permanent zone configuration. For this reason, no compatibility checking is done between source and target zone configurations or systems. Only the storage is checked.
You should be able to resume a migrated kernel zone on a target system if
you ensured before migration that the configuration was compatible. If a
suspended zone fails to resume on the target system due to compatibility or zone
configuration differences between the source and target systems, modify the zone
configuration on the target system and then try again to resume. You can also
boot the zone in a non-resume mode by specifying the ‐R option
with the boot
command, but this results in the saved
information in the zone's suspended image not being used, and it is no longer a
warm migration.