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

2.4.2 Consideration of Logical Domain Reconfiguration


2.4.2 Consideration of Logical Domain Reconfiguration
You need to note the following points when reconfiguring hardware resources assigned to a logical domain.
Preparation on the device side
Before reconfiguring a virtual disk and virtual network among virtual I/O devices, perform the following work:
  1. Unmounting the virtual disk
  2. Executing unplumb for the virtual network interface
Delayed reconfiguration for the control and root domains
To statically add a physical I/O to or delete it from the control and root domains, operate it through delayed reconfiguration. Once you reconfigure physical I/Os assigned to the target control and root domains through delayed reconfiguration, any other reconfiguration requests for the control and root domains are postponed until the control and root domains are restarted.
Limit on delayed reconfiguration
You cannot reconfigure the hardware resources for a guest domain when delayed reconfiguration mode is set for the control or root domain to reconfigure hardware resources. Perform reconfiguration work for the guest domain after finishing the reconfiguration work on the control or root domain.
Cancellation of delayed reconfiguration
Use the ldm cancel-operation reconf command to cancel a delayed reconfiguration operation on the control or root domain. For details of the ldm command, see the Oracle VM Server for SPARC Reference Manual.
Logical domain requirements
  1. When dynamically reconfiguring a physical partition, ensure that Oracle Solaris on the control domain has already started.
  2. The disk that configures the system volume on the control domain must be in a redundant configuration. The redundant configuration is required with the disk on both the system board deleted through dynamic reconfiguration and the system board not deleted through dynamic reconfiguration. If the disk is not in a redundant configuration, the control domain cannot be started when the I/O devices have been released in advance to delete the system board where the disk is mounted.
Memory size assigned to the hypervisor
The amount of memory that can be used with the logical domain is less than the amount of memory actually installed in the chassis. This is because the memory used for hypervisor operation is reserved on each chassis. At system configuration, design the domain configuration by subtracting the memory used by this hypervisor. The amount of memory assigned to the hypervisor depends on the model, building block configuration, and PPAR-DR mode setting. For details on PPAR DR mode, see "2.5.3 How to Check/Set PPAR DR Mode."

The hypervisor memory assigned to each physical partition is as follows:
Table 2-9  Amount of Memory Assigned to the Hypervisor
Model PPAR DR Mode
Enabled Disabled
SPARC M12-1/M12-2 2.5 GB
SPARC M12-2S 2.5 GB + (1.5 GB x (number of chassis comprising the physical partition - 1))
SPARC M10-1/M10-4 -
2 GB
SPARC M10-4S 2 GB + (1.25 GB x (number of chassis - 1)) 2 GB + (1.0 GB x (number of chassis - 1))
Placement of CPU cores and memory
To enable disconnection of the system board with physical partition dynamic reconfiguration, be careful when determining the number of CPU cores to be assigned, as well as the memory placement. For details, see "Placement of CPU cores and memory" in "2.5.2 Considerations in System Operation for Dynamic Reconfiguration."

Top of Page