From: Oleg Vasilev <oleg.vasilev@virtuozzo.com>
Date: Fri, 3 Mar 2023 08:24:55 +0000 (+0600)
Subject: docs: fix changed API calls
X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=794c583f4645a34e73660fc95c0a09f97bf9480a;p=libvirt.git

docs: fix changed API calls

Signed-off-by: Oleg Vasilev <oleg.vasilev@virtuozzo.com>
---

diff --git a/docs/kbase/internals/qemu-migration.rst b/docs/kbase/internals/qemu-migration.rst
index d9061ca49e..420f8971e8 100644
--- a/docs/kbase/internals/qemu-migration.rst
+++ b/docs/kbase/internals/qemu-migration.rst
@@ -79,7 +79,7 @@ The sequence of calling ``qemuMigrationJob*`` helper methods is as follows:
   it active::
 
       qemuMigrationJobStart(driver, vm, VIR_JOB_MIGRATION_{IN,OUT});
-      qemuMigrationJobSetPhase(driver, vm, QEMU_MIGRATION_PHASE_*);
+      qemuMigrationJobSetPhase(vm, QEMU_MIGRATION_PHASE_*);
       ...do work...
       qemuMigrationJobContinue(vm);
 
@@ -97,9 +97,9 @@ The sequence of calling ``qemuMigrationJob*`` helper methods is as follows:
           return;
       qemuMigrationJobStartPhase(driver, vm, QEMU_MIGRATION_PHASE_*);
       ...do work...
-      qemuMigrationJobFinish(driver, vm);
+      qemuMigrationJobFinish(vm);
 
 While migration job is running (i.e., after ``qemuMigrationJobStart*`` but before
 ``qemuMigrationJob{Continue,Finish}``), migration phase can be advanced using::
 
-      qemuMigrationJobSetPhase(driver, vm, QEMU_MIGRATION_PHASE_*);
+      qemuMigrationJobSetPhase(vm, QEMU_MIGRATION_PHASE_*);