Solaris Cluster Failover Zones Fails to Start when Conflicting "dedicated-cpu" Settings are used (Doc ID 2008604.1)

Last updated on AUGUST 01, 2016

Applies to:

Solaris Cluster - Version OSC 3.3 3/13 to OSC 4.2 [Release 3.3 to 4.2]
Solaris Operating System - Version 10 3/05 to 11.2 [Release 10.0 to 11.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

Some Solaris Cluster resources controlling failover zones are failing to start upon failover and /var/adm/messages shows errors like these:

 

Changes

The system had configured some zones with "dedicated-cpu" property and setting specific cpus for the zone using the "cpus" property while other were using "ncpus".
Such constraints are typically used either for licensing reasons (to restrict number of cpus usable by applications in the zone) .
They are also used to assign non-overlapping sets of cpus to different zones to better partition the server hardware across different workloads.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms