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.10 Checking the Usage Status of I/O Devices


3.2.10 Checking the Usage Status of I/O Devices
Use the ldm list-io command to check the I/O devices configured in logical domains in a physical partition.
# ldm list-io [-l] [-p] [bus | device | pf-name]
# ldm list-io -d pf-name
  1. -l

    Displays the details such as the relationship between the root complex and the PCIe direct I/O device.
  2. -p

    Displays information in parseable format, such as in the script.
  3. -d pf-name

    Displays the list of information regarding the specified physical functions.
  4. bus, device, and pf-name
    These are, respectively, the PCIe bus, the direct I/O-assignable device, and the PCIe SR-IOV physical function.
The following example displays the usage status of I/O devices in logical domains.
For PCIe devices that support the SR-IOV function, "PF" is indicated in the [TYPE] column.
For devices that create or use a virtual function of the SR-IOV, "VF" is indicated in the [TYPE] column.
# ldm list-io
NAME TYPE BUS DOMAIN STATUS
---- ---- --- ------ ------

PCIE0 BUS PCIE0 primary IOV
PCIE1 BUS PCIE1 primary IOV
PCIE2 BUS PCIE2 primary IOV
PCIE3 BUS PCIE3 primary IOV
PCIE4 BUS PCIE4 primary IOV
PCIE5 BUS PCIE5 primary IOV
PCIE6 BUS PCIE6 primary IOV
PCIE7 BUS PCIE7 primary IOV
(Omitted)
/BB0/PCI6 PCIE PCIE6 primary EMP
/BB0/PCI9 PCIE PCIE7 primary EMP
/BB0/PCI10 PCIE PCIE7 primary EMP
/BB0/PCI0/IOVNET.PF0 PF PCIE1 primary
/BB0/PCI0/IOVNET.PF1 PF PCIE1 primary
/BB0/CMUL/NET0/IOVNET.PF0 PF PCIE0 primary
/BB0/CMUL/NET0/IOVNET.PF1 PF PCIE0 primary
/BB0/CMUL/NET2/IOVNET.PF1 PF PCIE4 primary
/BB0/CMUL/NET2/IOVNET.PF0 PF PCIE4 primary
/BB0/PCI0/IOVNET.PF0.VF0 VF PCIE1 iodom00
/BB0/PCI0/IOVNET.PF0.VF1 VF PCIE1 iodom01
/BB0/PCI0/IOVNET.PF0.VF2 VF PCIE1 iodom02
To confirm the details, such as the relationship between the root complex and the PCIe direct I/O device, execute the command with the -l option specified.
The following example displays the usage status of I/O devices in logical domains.
  1. Logical domain to which the PCIe card is assigned
    The name displayed in the [DOMAIN] column of the slot (the line whose [NAME] column displays "/BBx/PCIx") of the maintenance target PCIe card indicates the logical domain to which the PCIe card is assigned.
  2. Logical domain to which the PCIe root complex that the PCIe card belongs to is assigned
    "PCIEx," which is displayed in the [BUS] column that was confirmed above, is the name of the PCIe root complex to which the PCIe card belongs. The [DOMAIN] column displays a name for the same PCIe root complex (on the line whose [NAME] column displays "PCIEx"). The name is a logical domain name. That PCIe root complex to which the PCIe card belongs is assigned to the logical domain.
# ldm list-io -l
NAME TYPE BUS DOMAIN STATUS
---- ---- --- ------ ------

PCIE0 BUS PCIE0 primary IOV
[pci@8000]
PCIE1 BUS PCIE1 primary IOV
[pci@8100]
PCIE2 BUS PCIE2 primary IOV
[pci@8200]
PCIE3 BUS PCIE3 rootdom IOV
[pci@8300]
PCIE4 BUS PCIE4 primary IOV
[pci@8400]
PCIE5 BUS PCIE5 primary IOV
[pci@8500]
PCIE6 BUS PCIE6 rootdom IOV
[pci@8600]
PCIE7 BUS PCIE7 primary IOV
[pci@8700]
/BB0/CMUL/NET0 PCIE PCIE0 primary OCC
[pci@8000/pci@4/pci@0/pci@9]
network@0
network@0,1
/BB0/CMUL/SASHBA PCIE PCIE0 primary OCC
[pci@8000/pci@4/pci@0/pci@0]
scsi@0/iport@f/disk@w50000393a82368b2,0
scsi@0/iport@f/smp@w500000e0e06d03bf
scsi@0/iport@f/enclosure@w500000e0e06d03bd,0
scsi@0/iport@v0
/BB0/PCI0 PCIE PCIE1 primary OCC
[pci@8100/pci@4/pci@0/pci@0]
/BB0/PCI3 PCIE PCIE2 primary EMP
[pci@8200/pci@4/pci@0/pci@0]
/BB0/PCI4 PCIE PCIE2 iodom1 OCC
[pci@8200/pci@4/pci@0/pci@8]
/BB0/PCI7 PCIE PCIE3 rootdom EMP
[pci@8300/pci@4/pci@0/pci@0]
/BB0/PCI8 PCIE PCIE3 rootdom EMP
[pci@8300/pci@4/pci@0/pci@8]
/BB0/CMUL/NET2 PCIE PCIE4 primary OCC
[pci@8400/pci@4/pci@0/pci@a]
network@0
network@0,1

Top of Page