Only features enabled by both migration class (cpu-arch) and host compatibility level (host-compatible) are visible to a SPARC kernel zone. To migrate a SPARC kernel zone, you must ensure that the feature set visible to the kernel zone matches on both the source and target hosts by configuring the migration class cpu-arch and host-compatible global properties.
If not set, the default value of cpu-arch is solaris. The zone boots with the same CPU class as the host. You can migrate the zone between CPU types that are compatible with the CPU class of the host. By default, Silicon Secured Memory (SSM), also known as ADI, is turned off for a kernel zone.
Do not set the cpu-arch global property to a migration class if you want to use SSM or DAX.
This section provides the following additional overview information:
For details about configuring CPU migration classes and host compatibility levels for kernel zones, see cpu-arch Global Property (solaris-kz Only), Host Compatibility Levels (solaris-kz SPARC Only), and the solaris-kz(7) man page.
Use the cpu-arch global property to configure SPARC kernel zones with a specific CPU class. The CPU class can be independent of the host CPU class, to ensure a safe migration between different CPU types.
If an Oracle VM Server for SPARC guest domain is booted with a specific class, the guest can be migrated safely among all platforms with compatible CPU types. Kernel zones use the same set of CPU classes as guest domains.
The default value of the cpu-arch global property is solaris. By default, the zone boots with the same CPU class as the host. You can migrate the zone between CPU types that are compatible with the CPU class of the host.
The host does not resume a zone previously suspended on an incompatible platform. The host also does not boot a zone if the migration class is set to an incompatible value for the host platform. For example, a guest on a T5 system will not boot if the cpu-arch global property is set to sparc64-class1. The CPU class of the zone cannot exceed the limits of the CPU class of the host.
A kernel zone booted with the generic class cannot be migrated to systems earlier than the SPARC T4. Kernel zones run on SPARC T4, Fujitsu SPARC M12, and Fujitsu M10/SPARC M10 supported systems.
For configuration details, see cpu-arch Global Property (solaris-kz Only) and the solaris-kz(7) man page.
Only features enabled by the migration class are visible to an x86 kernel zone. To migrate an x86 kernel zone, ensure that the feature set visible to the kernel zone matches on both the source and target hosts by configuring the migration class cpu-arch global property. The source and the target hosts must be the same platform. On x86 hosts, the CPU model names must match.
If no value is set, the default value of cpu-arch is solaris. The zone boots with the same CPU class as the host. You can migrate the zone between CPU types that are of exactly the same type or are the same micro architecture.
The host does not resume a zone previously suspended on an incompatible platform. The host also does not boot a zone if the migration class is set to an incompatible value for the host platform. The CPU class of the zone cannot exceed the limits of the CPU class of the host.
For configuration details, see cpu-arch Global Property (solaris-kz Only) and the solaris-kz(7) man page.
Use the host-compatibility global property to enable compatible features between the source and target hosts. The compatible features are those features supported by the version of Oracle Solaris running in the global zone. For live or warm migration between hosts running different Oracle Solaris releases, the host-compatible global property enables you to control the features that can be used by the zone.
If no value is set, the default host compatibility level of a kernel zone includes only the features supported in the Oracle Solaris 11.2 release.
For configuration details, see Host Compatibility Levels (solaris-kz SPARC Only) and the solaris-kz(7) man page.