1) Trying to restrict the repository won't help, you cannot create a non global zone with a lower version than the one of the global zone, the reason why I told you to start with a Solaris 11 FCS global zone.
2) All non global zones are both whole root and branded under Solaris 11, unlike with Solaris 10.
3) When importing a zone created with an older Solaris 11 update, some (but not all) packages are required to be in sync with the global zone to be attached, so the non global zone won't stay strictly identical to what it used to be.
To update this set of packages, the '-u' option is used, To update all packages, the '-U' one is available.
I agree hypervisor based virtualisation is required if a strictly 11.0 or 11.1 environment is expected but for 11.2, 11.3, 11.4 and newer, I would recommend kernel zones (vs VirtualBox or Ldoms).
solaris -
man pages section 5: Standards, Environments, and Macros
Quote:
If the packages that the zone depends on from the global zone are different (have different revision numbers) from the dependent packages on the source machine, zoneadm reports these conflicts and does not perform the attach.