On 1/9/24 07:46, pet...@redhat.com wrote:
From: Peter Xu <pet...@redhat.com>

Move it one layer down, so taking Virtio-migration as a feature for
migration.

Cc: Michael S. Tsirkin <m...@redhat.com>
Cc: Jason Wang <jasow...@redhat.com>
Signed-off-by: Peter Xu <pet...@redhat.com>


Reviewed-by: Cédric Le Goater <c...@redhat.com>

Thanks,

C.



---
  docs/devel/migration/features.rst | 1 +
  docs/devel/migration/index.rst    | 1 -
  2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/devel/migration/features.rst 
b/docs/devel/migration/features.rst
index dea016f707..a9acaf618e 100644
--- a/docs/devel/migration/features.rst
+++ b/docs/devel/migration/features.rst
@@ -9,3 +9,4 @@ Migration has plenty of features to support different use cases.
     postcopy
     dirty-limit
     vfio
+   virtio
diff --git a/docs/devel/migration/index.rst b/docs/devel/migration/index.rst
index 2479e8ecb7..7b7a706e35 100644
--- a/docs/devel/migration/index.rst
+++ b/docs/devel/migration/index.rst
@@ -10,5 +10,4 @@ QEMU live migration works.
     main
     features
     compatibility
-   virtio
     best-practises


Reply via email to