Go to main content
Oracle® Solaris 11.3 Release Notes

Exit Print View

Updated: July 2017
 
 

Kernel Zones Issues

This section describes issues related to kernel zones in Oracle Solaris 11.3.

Kernel Zones Interfere With hardware-counter-overflow Interrupt (18355260)

On a system running kernel zones, the DTrace CPU performance counter (CPC) provider might time out on some CPUs on the host and guest, stop delivering hardware-counter-overflow interrupts, and provide incomplete data.

Workaround: None.

AI Manifest configuration Element Cannot be Used to Install Kernel Zones (18537903)

When a system is deployed by using the automated installer (AI), non-global zones can optionally be installed on the system by using the configuration element within the AI manifest. Non-global zones are configured and installed by the zones self-assembly SMF service (svc:/system/zones-install:default) on first reboot after the global zone installation has completed.

If you attempt to install a kernel zone by using the configuration element, the installation fails and the SMF service svc:/system/zones-install:default goes into the maintenance mode.

Workaround: Install kernel zones by using the zoneadm install command after the installation of the system is completed.

Kernel Zones on NFS Can Have zpool Corruption During Live Migration (20697332)

Kernel zones that use ZOSS NFS might experience zpool data corruption during live migration. Fault management architecture (FMA) zpool errors might be generated in the zone and the zpool status will report checksum errors in the zone.

Workaround: Do not live migrate kernel zones that use ZOSS NFS.

SPARC: Live Migration of Guest Domain Fails When Kernel Zones Are Running Inside (21289174)

A running kernel zone within an Oracle VM Server for SPARC domain blocks the live migration of the guest domain. A similar issue was described previously in Bug 18289196, which is superseded by this report. The following error message might be displayed:

Guest suspension failed due to the presence of active Kernel Zones.
Stop Kernel Zones and retry the operation.

Workaround: Choose one of the following workarounds: