Use of the non-primary root domain has the following limitations:
An I/O domain cannot start if the associated root domain is not running.
Support for delayed reconfiguration has been extended to the non-primary root domains. Only the following commands can be run until that root domain has been rebooted or the delayed reconfiguration has been canceled:
ldm add-io
ldm remove-io
ldm set-io
ldm create-vf
ldm destroy-vf
The root domain must be active and booted to perform the following operations:
Creating and destroying SR-IOV virtual functions
Adding and removing PCIe slots
Adding and removing SR-IOV virtual functions
You must initiate a delayed reconfiguration on the root domain when you perform the ldm add-io and ldm remove-io direct I/O operations for PCIe slots.
When your configuration does not meet the dynamic I/O virtualization requirements, you must use delayed reconfiguration for the following SR-IOV virtual function operations:
ldm create-vf
ldm destroy-vf
ldm add-io
ldm remove-io
ldm set-io
The reboot of a root domain affects any I/O domain that has a device from the PCIe buses that the root domain owns. See Rebooting the Root Domain With PCIe Endpoints Configured.
You cannot assign an SR-IOV virtual function or a PCIe slot from one root domain to another root domain. This limitation prevents circular dependencies.