Zone Migration and Package Updates

solaris zones always have their storage mapped and zpools imported, even in an attached state. This is necessary so that packages in the zone can be updated when the global zone is updated. When a solaris zone is attached on the target system during migration, the packages in the zone are verified against the global zone and the attach fails if the package levels are different, unless you specify to attempt to update the zone with the ‐u or ‐U update option.

A migration using a ‐u or ‐U update option attempts to update the packages in the solaris zone to match the global zone. During that attempt a new ZBE might be created.

If no -x attach-*-zbe option is given to zoneadm migrate, the attach on the destination system selects the most recently mounted ZBE to be cloned. The cloned ZBE is then attached.