Go to main content

Oracle® VM Server for SPARC 3.6 Administration Guide

Exit Print View

Updated: September 2019
 
 

Configuration Management Issues

init-system Does Not Restore Named Core Constraints for Guest Domains From Saved XML Files

If you assigned named core resources to a domain, using the ldm init-system command might fail to re-assign those named resources to that domain. This might occur because the ldm init-system command initiates a delayed reconfiguration for the primary domain and you can perform only one virtual CPU operation per delayed reconfiguration. So, this command fails to restore the named CPU core constraints for guest domains from a saved XML file.

Workaround: Perform the following steps:

  1. Create an XML file for the primary domain.

    primary# ldm list-constraints -x primary > primary.xml
  2. Create an XML file for the guest domain or domains.

    primary# ldm list-constraints -x domain-name[,domain-name][,...] > guest.xml
  3. Power cycle the system and boot a factory-default configuration.

  4. Apply the XML configuration to the primary domain.

    primary# ldm init-system -r -i primary.xml
  5. Apply the XML configuration to the guest domain or domains.

    primary# ldm init-system -f -i guest.xml

After Dropping Into factory-default, Recovery Mode Fails if the System Boots From a Different Device Than the One Booted in the Previously Active Configuration

 

While triggering a recovery after dropping into factory-default, recovery mode fails if the system boots from a different device than the one booted in the previously active configuration. This failure might occur if the active configuration uses a boot device other than the factory-default boot device.


Note - This problem applies to SPARC T4 series servers. This problem also applies to SPARC T5, SPARC M5, and SPARC M6 series servers that run a system firmware version prior to 9.5.3.

To work around the problem, perform the following steps any time you want to save a new configuration to the SP:

  1. Determine the full PCI path to the boot device for the primary domain.

    Use this path for the ldm set-var command in Step 4.

  2. Remove any currently set boot-device property from the primary domain.

    Performing this step is necessary only if the boot-device property has a value set. If the property does not have a value set, an attempt to remove the boot-device property results in the boot-device not found message.

    primary# ldm rm-var boot-device primary
  3. Save the current configuration to the SP.

    primary# ldm add-spconfig config-name
  4. Explicitly set the boot-device property for the primary domain.

    primary# ldm set-var boot-device=value primary

    If you set the boot-device property after saving the configuration to the SP as described, the specified boot device is booted when recovery mode is triggered.

If recovery mode has already failed as described, perform the following steps:

  1. Explicitly set the boot device to the one used in the last running configuration.

    primary# ldm set-var boot-device=value primary
  2. Reboot the primary domain.

    primary# reboot

    The reboot enables the recovery to proceed.

Guest Domain eeprom Updates Are Lost if an ldm add-spconfig Operation Is Not Complete

 

An attempt to set an OBP variable from a guest domain might fail if you use the eeprom or the OBP command before one of the following commands is completed:

  • ldm add-spconfig

  • ldm remove-spconfig

  • ldm set-spconfig

  • ldm bind

This problem might occur when these commands take more than 15 seconds to complete.

# /usr/sbin/eeprom boot-file\=-k
promif_ldom_setprop: promif_ldom_setprop: ds response timeout
eeprom: OPROMSETOPT: Invalid argument
boot-file: invalid property

If you encounter this error, retry the eeprom or OBP command after the ldm operation has completed.

To avoid this error, retry the eeprom or OBP command on the affected guest domain. You might be able to avoid the problem by using the ldm set-var command on the primary domain.

Trying to Connect to Guest Domain Console While It Is Being Bound Might Cause Input to Be Blocked

 

A domain's guest console might freeze if repeated attempts are made to connect to the console before and during the time the console is bound. For example, this might occur if you use an automated script to grab the console as a domain is being migrated onto the machine.

To unfreeze console, perform the following commands on the domain that hosts the domain's console concentrator (usually the control domain):

primary# svcadm disable vntsd
primary# svcadm enable vntsd