From fec048c5614b6d903fcb553810d068b29c1ca8a6 Mon Sep 17 00:00:00 2001 From: Sean Mooney Date: Thu, 30 May 2019 18:52:37 +0100 Subject: [PATCH] update sriov config docs for live migration support. - In the train release of Nova SR-IOV live migration support was added to the libvirt virt driver. - This change updated the admin config docs to reflect that live migration is now supported. Change-Id: I429d2477d1b379de06d666edbdef4a9afcfe4b5d --- doc/source/admin/config-sriov.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/doc/source/admin/config-sriov.rst b/doc/source/admin/config-sriov.rst index a46645bee19..504924e28c9 100644 --- a/doc/source/admin/config-sriov.rst +++ b/doc/source/admin/config-sriov.rst @@ -639,7 +639,14 @@ Known limitations * SR-IOV is not integrated into the OpenStack Dashboard (horizon). Users must use the CLI or API to configure SR-IOV interfaces. -* Live migration is not supported for instances with SR-IOV ports. +* Live migration support has been added to the Libvirt Nova virt-driver in the Train + release for instances with neutron SR-IOV ports. Indirect mode SR-IOV interfaces + (vnic-type: macvtap or virtio-forwarder) can now be migrated transparently to + the guest. Direct mode SR-IOV interfaces (vnic-type: direct or direct-physical) + are detached before the migration and reattached after the migration so this is not + transparent to the guest. To avoid loss of network connectivy when live migrating + with direct mode sriov the user should create a failover bond in the guest with a + transparently live migration port type e.g. vnic-type normal or indirect mode SR-IOV. .. note::