Skip to main content

Contents

  1. Preface
  2. Chapter 1 Understanding an Overview of Domain Configuration
    1. Click 1.1 SPARC M12/M10 Domain Configurations
    2.  1.2 SPARC M12/M10 Hardware Resources
    3. Click 1.3 What is a Physical Partition?
    4. Click 1.4 What is a Logical Domain?
    5. Click 1.5 What is Physical Partition Dynamic Reconfiguration?
    6. Click 1.6 Mixed Use of the SPARC64 X+ Processor and SPARC64 X Processor
  3. Chapter 2 Conditions and Settings for System Operation
    1. Click 2.1 XSCF Status Management
    2. Click 2.2 XSCF Conditions and Settings
    3. Click 2.3 Oracle Solaris Conditions and Settings
    4. Click 2.4 Logical Domain Conditions and Settings
    5. Click 2.5 Dynamic Reconfiguration Conditions and Settings
    6. Click 2.6 Considerations When Using the SPARC64 X+ Processor
  4. Chapter 3 Operations for Domain Configuration
    1. Click 3.1 Operations and Commands Related to Physical Partition Configurations
    2. Click 3.2 Operations and Commands Related to Logical Domain Configurations
  5. Chapter 4 Configuring a Physical Partition
    1.  4.1 Physical Partition Configuration Flow
    2.  4.2 Configuring and Operating a Physical Partition
  6. Chapter 5 Logical Domain Configuration Example
    1.  5.1 Logical Domain Configuration Flow
    2. Click 5.2 Example of Logical Domain Configuration Operations
  7. Chapter 6 Physical Partition Reconfiguration
    1. Click 6.1 Flow for Physical Partition Reconfiguration
    2. Click 6.2 Example of System Board Addition
    3. Click 6.3 Example of Operations for Deleting a System Board
    4.  6.4 Example of Operations for Moving a System Board
    5.  6.5 Example of Operations for Replacing a System Board
    6.  6.6 Considerations When Changing a Physical Partition Number
  8. Chapter 7 Migrating a Guest Domain
    1. Click 7.1 Overview
    2.  7.2 Migrating a Guest Domain
    3.  7.3 Guest Domain Migration Example
  9. Appendix A Environment Configuration Examples and Procedures Using Physical Partition Dynamic Reconfiguration
    1. Click A.1 Updating a System That Does Not Support Physical Partition Dynamic Reconfiguration to One That Does Support It
    2. Click A.2 For New Installations from XCP 2220 or Later, Where the Logical Domain Configuration Has No Free Space for Hardware Resources
    3. Click A.3 For New Installations from XCP 2220 or Later, Where the Logical Domain Configuration Has Free Hardware Resources
    4. Click A.4 For Expansion of a Newly Installed System of Version XCP 2220 or Later from the 1BB to 2BB Configuration
    5. Click A.5 For Installation of the System Board Configured by the SPARC64 X+ Processor to the Physical Partition Configured Only by the SPARC64 X Processor
    6. Click A.6 For Active Replacement of a System Board in a Configuration with Only the Control Domain (for Oracle VM Server for SPARC 3.2 or Later)
  10. Appendix B Supplementary Information for Using Dynamic Reconfiguration
    1. Click B.1 Considerations for the XSCF Reboot or Failover Time
    2.  B.2 Supplementary Information on CPU Operational Mode
    3.  B.3 Other Considerations
  11. Appendix C Meanings of Messages and Corresponding Corrective Action
    1. Click C.1 Command Messages

3.2.15 Setting CPU Socket Restrictions


3.2.15 Setting CPU Socket Restrictions
Use the ldm set-socket command to set CPU socket constraints. CPU socket constraints are used to assign virtual CPUs, cores, and memory only from the specified CPU socket. This subcommand is supported by Oracle VM for SPARC 3.3 and later.
# ldm set-socket [-f] [--remap] socket_id=[id[,id[,...]]] ldom
  1. -f

    This option clears constraints on all the existing virtual CPUs, cores, and memory for inactive logical domains. If the specified CPU socket for a bound or active domain has fewer resources than those defined by constraints, the constraints on resources and/or the degraded CPU socket may be modified.
  2. --remap

    This option moves virtual resources assigned to an active physical resource to another physical resource while the domain that has the virtual resources is operating.
  3. id
    Specify the CPU socket ID.
The following example sets CPU socket#2 constraints on logical domain ldom1.
# ldm set-socket socket_id=2 ldom1

Top of Page