Blame SOURCES/0074-p2v-Refer-to-virt-v2v-resource-requirements-in-virt-.patch

0d20ef
From d36f16809954ab7af7e2c9f0662abeda8d47ce98 Mon Sep 17 00:00:00 2001
0d20ef
From: "Richard W.M. Jones" <rjones@redhat.com>
0d20ef
Date: Sat, 29 Nov 2014 18:20:52 +0000
0d20ef
Subject: [PATCH] p2v: Refer to virt-v2v resource requirements in virt-p2v man
0d20ef
 page.
0d20ef
0d20ef
(cherry picked from commit 391d90d9e7b86890c3de3cd5fc200375fb8c6b0a)
0d20ef
---
0d20ef
 p2v/virt-p2v.pod | 3 ++-
0d20ef
 1 file changed, 2 insertions(+), 1 deletion(-)
0d20ef
0d20ef
diff --git a/p2v/virt-p2v.pod b/p2v/virt-p2v.pod
0d20ef
index 1ff1130..744e8d4 100644
0d20ef
--- a/p2v/virt-p2v.pod
0d20ef
+++ b/p2v/virt-p2v.pod
0d20ef
@@ -59,7 +59,8 @@ L<sshd_config(5)> file on the conversion server).
0d20ef
 The conversion server does not need to be a physical machine.  It
0d20ef
 could be a virtual machine, as long as it has sufficient memory and
0d20ef
 disk space to do the conversion, and as long as the physical machine
0d20ef
-can connect directly to its SSH port.
0d20ef
+can connect directly to its SSH port.  (See also
0d20ef
+L<virt-v2v(1)/RESOURCE REQUIREMENTS>).
0d20ef
 
0d20ef
 Because all of the data on the physical server's hard drive(s) has to
0d20ef
 be copied over the network, the speed of conversion is largely
0d20ef
-- 
0d20ef
1.8.3.1
0d20ef