ldm init-system Command Might Not Correctly Restore a Domain Configuration on Which Physical I/O Changes Have Been Made

Bug ID 15783031: You might experience problems when you use the ldm init-system command to restore a domain configuration that has used direct I/O or SR-IOV operations.

A problem arises if one or more of the following operations have been performed on the configuration to be restored:

• A slot has been removed from a bus that is still owned by the primary domain.

• A virtual function has been created from a physical function that is owned by the primary domain.

• A virtual function has been assigned to the primary domain, to other guest domains, or to both.

• A root complex has been removed from the primary domain and assigned to a guest domain, and that root complex is used as the basis for further I/O virtualization operations.

  In other words, you created a non-primary root domain and performed any of the previous operations.

If you have performed any of the previous actions, perform the workaround shown in Using the ldm init-system Command to Restore Domain Configurations on Which Physical I/O Changes Have Been Made (Doc ID 1575852.1).