Oracle® VM Server for SPARC 3.3 Release Notes

Exit Print View

Updated: October 2015
 
 

SR-IOV Issues

SPARC M5 and SPARC M6: Virtual Function Add Operation Triggers a PCIe Fabric Error Panic When Attempting to Enable SR-IOV on the PCIe Bus That Hosts rKVMS Devices

Bug ID 21548747: If you use any SR-IOV devices on a SPARC M5 or SPARC M6 system on a PCIe bus that hosts rKVMS devices, attempting to enable SR-IOV after a dynamic bus add DBUS operation triggers an FMA error panic.

Workaround: Restrict the use of a PCIe bus that hosts rKVMS devices to the primary domain. Only use the static PCIe bus assignment method to remove and add this bus to the primary domain.

Fibre Channel Physical Function Configuration Changes Require Several Minutes to Complete

Bug ID 21299683: After you create or destroy virtual functions, it might take up to five minutes before you can attempt to create or destroy more virtual functions from the Fibre Channel physical function.

If you attempt to perform these operations before five minutes elapse, the operations fail with a message similar to the following:

The attempt to offline the pf /SYS/PCI-EM4/IOVFC.PF0 in domain
primary failed.
Error message from svc:/ldoms/agents in domain primary:
CMD_OFFLINE Failed. ERROR: devices or resources are busy.

Sometimes the states of the physical function, the virtual function, or both appear as INV in ldm list-io output. For example, in the following sample output, physical function 0 and its child virtual functions have an INV status.

primary# ldm list-io pci_5
NAME                                       TYPE   BUS      DOMAIN    STATUS
----                                       ----   ---      ------    ------
pci_5                                      BUS    pci_5    primary   IOV
/SYS/RCSA/PCIE5                            PCIE   pci_5    primary   OCC
/SYS/RCSA/PCIE6                            PCIE   pci_5    primary   OCC
/SYS/RCSA/PCIE5/IOVFC.PF0                  PF     pci_5    primary   INV
/SYS/RCSA/PCIE5/IOVFC.PF1                  PF     pci_5    primary
/SYS/RCSA/PCIE5/IOVFC.PF0.VF0              VF     pci_5              INV
/SYS/RCSA/PCIE5/IOVFC.PF0.VF1              VF     pci_5              INV
/SYS/RCSA/PCIE5/IOVFC.PF0.VF2              VF     pci_5              INV
/SYS/RCSA/PCIE5/IOVFC.PF0.VF3              VF     pci_5              INV
/SYS/RCSA/PCIE5/IOVFC.PF0.VF4              VF     pci_5              INV
/SYS/RCSA/PCIE5/IOVFC.PF0.VF5              VF     pci_5              INV
/SYS/RCSA/PCIE5/IOVFC.PF0.VF6              VF     pci_5              INV

Workaround: To clear the INV status on the physical and virtual functions, perform the following steps:

  1. Wait five minutes.

  2. Retry the IOV operation to create or destroy the virtual function on the Fibre Channel physical function.

You can perform all necessary IOV configurations for the Fibre Channel physical function in a single command by using the ldm create-vf -n max or ldm destroy-vf -n max command.

ldm remove-io Command Reports a Timeout and Fails to Remove the Last SR-IOV Virtual Function From an I/O Domain

Bug ID 20731016: When you use the ldm remove-io command to remove the last SR-IOV virtual function from an I/O domain, the command might report a timeout and fail to remove the virtual function.

Workaround: If this problem occurs, perform the following steps:

  1. Verify that the system/management/hwmgmtd package is installed on the system.

    # pkg info system/management/hwmgmtd
  2. Disable the svc:/system/sp/management service.

    # svcadm disable -st svc:/system/sp/management
  3. Retry the ldm remove-io command.

  4. When the SR-IOV virtual function is successfully removed, enable the svc:/system/sp/management service.

    # svcadm enable svc:/system/sp/management

Fibre Channel Physical Function Is Faulted by FMA and Disabled

Bug IDs 18168525 and 18156291: You must connect the Fibre Channel PCIe card to a Fibre Channel switch that supports NPIV and that is compatible with the PCIe card. If you do not use this configuration, using the format command, or creating or destroying a virtual function might cause the physical function to be faulted by FMA and disabled. If this fault occurs, the message is similar to the following:

SUNW-MSG-ID: PCIEX-8000-0A, TYPE: Fault, VER: 1, SEVERITY: Critical
EVENT-TIME: event-time
PLATFORM: platform-type
SOURCE: eft, REV: 1.16
EVENT-ID: event-ID
DESC: A problem was detected for a PCIEX device.
AUTO_RESPONSE: One or more device instances may be disabled
IMPACT: Loss of services provided by the device instances associated with
this fault
REC-ACTION: Use 'fmadm faulty' to provide a more detailed view of this event.
Please refer to the associated reference document at
http://support.oracle.com/msg/PCIEX-8000-0A for the latest service procedures
and policies regarding this diagnosis.

Workaround: If the card has been faulted by FMA, first check its connections and ensure that the card is not directly connected to storage. Then, perform the step that matches your configuration:

  • Card is directly connected to storage – Correctly configure the Fibre Channel PCIe card by connecting it to a Fibre Channel switch that supports NPIV and is compatible with the PCIe card. Then, run the fmadm repair command to override the FMA diagnosis.

  • Card is not directly connected to storage – Replace the card.

Warnings Appear on Console When Creating Fibre Channel Virtual Functions

Bug ID 17623156: When you create Fibre Channel virtual functions, you might see the following warnings:

WARNING: kmem_cache_destroy: 'px0_emlxs3_3_cache2'
  (3000383e030) not empty
WARNING: vmem_destroy('px0_emlxs3_3_vmem_top'):
  leaked 262144 identifiers

These messages do not affect the normal operation of the system and you can ignore them.

Workaround: None.

Fujitsu M10 Server Has Different SR-IOV Feature Limitations

On a Fujitsu M10 server you can assign PCIe endpoint devices and SR-IOV virtual functions from a particular PCIe bus to a maximum of 24 domains. The maximum is 15 domains for supported SPARC T-Series and SPARC M-Series platforms.