Blame SOURCES/0118-v2v-Document-that-vCenter-5.0-is-required-RHBZ-11742.patch

ffd6ed
From d80e43e17b37af214aa6e81904afc7b7b9c47247 Mon Sep 17 00:00:00 2001
ffd6ed
From: "Richard W.M. Jones" <rjones@redhat.com>
ffd6ed
Date: Mon, 13 Apr 2015 11:46:29 +0100
ffd6ed
Subject: [PATCH] v2v: Document that vCenter >= 5.0 is required (RHBZ#1174200).
ffd6ed
ffd6ed
vCenter 5.0 was released in 2011.  We have not tested against any
ffd6ed
earlier versions, but it was reported that it does not work with
ffd6ed
vCenter 4.
ffd6ed
ffd6ed
Thanks: Sokratis
ffd6ed
(cherry picked from commit abf23ece49972111e19147087664e7442d84fdfd)
ffd6ed
---
ffd6ed
 v2v/virt-v2v.pod | 2 ++
ffd6ed
 1 file changed, 2 insertions(+)
ffd6ed
ffd6ed
diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod
ffd6ed
index 033040e..7de265b 100644
ffd6ed
--- a/v2v/virt-v2v.pod
ffd6ed
+++ b/v2v/virt-v2v.pod
ffd6ed
@@ -744,6 +744,8 @@ I<--bridge> option instead.  For example:
ffd6ed
 
ffd6ed
 Virt-v2v is able to import guests from VMware vCenter Server.
ffd6ed
 
ffd6ed
+vCenter E<ge> 5.0 is required.
ffd6ed
+
ffd6ed
 Note that virt-v2v B<cannot> import guests directly from an ESXi
ffd6ed
 hypervisor.
ffd6ed
 
ffd6ed
-- 
ffd6ed
1.8.3.1
ffd6ed