Blame SOURCES/0032-p2v-Explain-in-the-man-page-why-the-virt-p2v-ISO-is-.patch

0d20ef
From 96dd0999819b0efdea763c66d11cbf99684cdbd1 Mon Sep 17 00:00:00 2001
0d20ef
From: "Richard W.M. Jones" <rjones@redhat.com>
0d20ef
Date: Sun, 26 Oct 2014 19:35:36 +0000
0d20ef
Subject: [PATCH] p2v: Explain in the man page why the virt-p2v ISO is used.
0d20ef
0d20ef
(cherry picked from commit fab95a52bd307e6be699681de67134788687bf13)
0d20ef
---
0d20ef
 p2v/virt-p2v.pod | 5 ++++-
0d20ef
 1 file changed, 4 insertions(+), 1 deletion(-)
0d20ef
0d20ef
diff --git a/p2v/virt-p2v.pod b/p2v/virt-p2v.pod
0d20ef
index 2dfe0a4..6e7a77d 100644
0d20ef
--- a/p2v/virt-p2v.pod
0d20ef
+++ b/p2v/virt-p2v.pod
0d20ef
@@ -18,7 +18,10 @@ L<virt-v2v(1)>.
0d20ef
 Normally you don't run the virt-p2v program directly.  Instead you
0d20ef
 have to boot the physical machine using the bootable CD-ROM, ISO or
0d20ef
 PXE image.  This bootable image contains the virt-p2v binary and runs
0d20ef
-it automatically.
0d20ef
+it automatically.  Booting from a CD-ROM/etc is required because the
0d20ef
+disks which are being converted must be quiescent.  It is not safe to
0d20ef
+try to convert a running physical machine where other programs may be
0d20ef
+modifying the disk content at the same time.
0d20ef
 
0d20ef
 This manual page documents running the virt-p2v program.  To create
0d20ef
 the bootable image you should look at L<virt-p2v-make-disk(1)> or
0d20ef
-- 
0d20ef
1.8.3.1
0d20ef