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

A.2.1 Configuration Example


A.2.1 Configuration Example
This section describes an example of configuring a logical domain consisting of two SPARC M10-4S, i.e. two system boards (PSB<BB>) (2BB configuration).
To enable physical partition dynamic reconfiguration in a physical partition, the I/O configuration must satisfy the following conditions.
  1. The system volume disk and network interface of the control domain must be made redundant by connecting the I/O of each SPARC M10-4S. This is done to make it possible to continue operation with the I/O of the remaining SPARC M10-4Ss when a SPARC M10-4S is removed.
  2. It is necessary to place a root domain for each SPARC M10-4S and to use that root domain as the dedicated one for providing a virtual I/O to the guest domain. The reason for this is as follows: If the root domain is being used for business, it must be stopped upon the disconnection of the SPARC M10-4S and so the business will stop.
  3. The business must be operated in the guest domain. The virtual I/O service of each root domain must be assigned to the virtual I/O devices (vdisk, vnet) of this guest domain to make those virtual I/O devices redundant. The reason for this is as follows: Even if the SPARC M10-4S is disconnected on one side, I/O access can be continued by using the virtual I/O service of the root domain on the remaining SPARC M10-4S. In this way, disconnecting the SPARC M10-4S does not influence the guest domain, allowing business operations to continue.
The following is a schematic diagram of a configuration that satisfies the above conditions. Moreover, the I/O configuration of each logical domain is simplified.
Figure A-2  Configuration Example in Which Operations Can Continue in the 2BB Configuration
Figure A-2 Configuration Example in Which Operations Can Continue in the 2BB Configuration
The following table gives an example of the CPU cores, memory, and I/O configuration to be assigned to the control domain, root domain, and guest domain in the 2BB configuration. There is no empty resource which is large enough to enable movement of the CPU core and memory assigned to each logical domain upon SPARC M10-4S disconnection.
Table A-1  Example of the 2BB Configuration With No Empty Hardware Resources
Logical Domain Name primary root-dom0 root-dom1 guest0 guest1
CPU core
(activation: 128)		 32 16 16 32 32
Memory
(Total: 256 GB)
56 GB (*1)
32 GB
32 GB
64 GB
64 GB
Physical I/O
(Root complex assignment)		 On-board #0
(PCIE0, PCIE4)
On-board #1
(PCIE8, PCIE12)		 PCIE1, PCIE2,
PCIE3, PCIE5,
PCIE6, PCIE7		 PCIE9, PCIE10,
PCIE11, PCIE13,
PCIE14, PCIE15		 - -
Virtual I/O device - vds0
vsw0, vsw1		 vds1
vsw10, vsw11		 vdisk0, vdisk10
vnet0, vnet10		 vdisk1, vdisk11
vnet1, vnet11
*1 In the configuration example shown above, the size of memory to be assigned to the control domain is calculated as the remainder of the memory after assignment to the other logical domains.

First, when the remaining size, calculated by subtracting the sizes assigned to domains other than the control domain from the total capacity of the physical memory, is obtained, it is 64 GB.

256 GB - 32 GB - 32 GB - 64 GB - 64 GB = 64 GB

The maximum size to be actually assigned to the control domain is up to the size (60.75 GB) calculated by subtracting, from the above result, the memory size (2 GB + 1.25 GB) assigned to the hypervisor.

64 GB - 2 GB - 1.25 GB = 60.75 GB

In addition, when the version of Oracle VM Server for SPARC is earlier than 3.2, it is 56 GB when the calculation is made with a maximum size of less than 60.75 GB to make it a multiple of (number of cores x 256 MB) as a condition for performing physical partition dynamic reconfiguration.

60.75 GB/(32 cores x 256 MB) = 7.59

To make it an integral multiple, round it down to "7."

(32 cores x 256 MB) x 7 = 56 GB
Note - You should design the size of memory to be assigned to logical domains by noting the following two points. For details, see "2.4.1 Consideration of Logical Domain Configuration."
- The size of memory to be assigned to logical domains becomes smaller than the physical memory size.

- When the version of Oracle VM Server for SPARC is earlier than 3.2, use a multiple of (number of cores x 256 MB) to enable physical partition dynamic reconfiguration.

Top of Page