How to restore a LDOM config across M5/M6 expandable property change
(Doc ID 1640383.1)
Last updated on DECEMBER 01, 2023
Applies to:
SPARC M6-32 - Version All Versions to All Versions [Release All Releases]SPARC M5-32 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
If you change the expandable property from true to false or vice versa, after logical domains(LDOMs) are created, you will see similar messages like the ones below, during POST. This will prevent the LDOMs from booting.
:
2014-03-26 06:15:18 24:0:0> DEBUG: Storing PlatMD to memory
2014-03-26 06:15:18 24:0:0> DEBUG: stored plat md to 0x65e0000 (mdp=1d5d850) size=22288
2014-03-26 06:15:19 24:0:0> WARNING: HOST expandable property must be set to true in order to boot config
2014-03-26 06:15:20 24:0:0> WARNING: Unable to boot config_kon3 due to missing resources *
2014-03-26 06:15:20 24:0:0> DEBUG: Trying to fall back to degraded config
2014-03-26 06:15:20 24:0:0> DEBUG: Can't open degraded cfg "config_kon3" - rv = -6
2014-03-26 06:15:20 24:0:0> DEBUG: Degraded config doesn't exist
2014-03-26 06:15:20 24:0:0> WARNING: Falling back to factory-default
2014-03-26 06:15:20 24:0:0> NOTICE: Booting config = factory-default
2014-03-26 06:15:20 24:0:0> DEBUG: Updating mdset-boot-reason prop: "1""config_kon3""factory-default"
2014-03-26 06:15:20 24:0:0> DEBUG: bootconfig differs from last boot
2014-03-26 06:15:20 24:0:0> DEBUG: clearing TOD offset
2014-03-26 06:15:20 24:0:0> DEBUG: clear_tod_offset_in_PDomain_info
2014-03-26 06:15:20 24:0:0> DEBUG: ldm_set_bootedconfig_name: New bootedcfg factory-default, last bootedcfg config_kon3
:
* "config_kon3" here is an original LDOM config stored at the ILOM. Upon changing the expandable property, the PDomain will fail back to "factory-default" and the original LDOM config will be degraded during POST.
Assuming the ldmd/recovery_mode is not enabled. (Ref: ldmd/recovery_mode )
Changes
PDomain expandable values changed from true to false or vice versa after LDOMs were created.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |