On Fri, Sep 02, 2016 at 07:52:13 -0400, Kothapally Madhu Pavan wrote:
--postcopy-after-precopy is just an aditional flag for postcopy migration.
Signed-off-by: Kothapally Madhu Pavan <kmp@linux.vnet.ibm.com> --- tools/virsh-domain.c | 6 +++--- tools/virsh.pod | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) ... diff --git a/tools/virsh.pod b/tools/virsh.pod index 1e36ee1..3670ace 100644 --- a/tools/virsh.pod +++ b/tools/virsh.pod @@ -1617,8 +1617,8 @@ migration. I<--postcopy> enables post-copy logic in migration, but does not actually start post-copy, i.e., migration is started in pre-copy mode. Once migration is running, the user may switch to post-copy using the B<migrate-postcopy> command sent from another virsh instance or use -I<--postcopy-after-precopy> to let libvirt automatically switch to -post-copy after the first pass of pre-copy is finished. +I<--postcopy-after-precopy> along with I<--postcopy> to let libvirt automatically
I just fixed this long line before pushing. Jirka