|
 |
ffd6ed |
From 6d1d399ecb2016f12a6bdd6440cd4b5111050098 Mon Sep 17 00:00:00 2001
|
|
|
ffd6ed |
From: "Richard W.M. Jones" <rjones@redhat.com>
|
|
|
ffd6ed |
Date: Mon, 13 Apr 2015 12:01:22 +0100
|
|
|
ffd6ed |
Subject: [PATCH] v2v: Add a man page section on importing from OVA files.
|
|
|
ffd6ed |
|
|
|
ffd6ed |
(cherry picked from commit e062093881d66b56c4935054ad409ecf2531880b)
|
|
|
ffd6ed |
---
|
|
|
ffd6ed |
v2v/virt-v2v.pod | 49 ++++++++++++++++++++++++++++++++++++++++++++-----
|
|
|
ffd6ed |
1 file changed, 44 insertions(+), 5 deletions(-)
|
|
|
ffd6ed |
|
|
|
ffd6ed |
diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod
|
|
|
ffd6ed |
index 7de265b..91e8f3e 100644
|
|
|
ffd6ed |
--- a/v2v/virt-v2v.pod
|
|
|
ffd6ed |
+++ b/v2v/virt-v2v.pod
|
|
|
ffd6ed |
@@ -202,7 +202,8 @@ Set the input method to I<ova>.
|
|
|
ffd6ed |
|
|
|
ffd6ed |
In this mode you can read a VMware ova file. Virt-v2v will read the
|
|
|
ffd6ed |
ova manifest file and check the vmdk volumes for validity (checksums)
|
|
|
ffd6ed |
-as well as analyzing the ovf file, and then convert the guest.
|
|
|
ffd6ed |
+as well as analyzing the ovf file, and then convert the guest. See
|
|
|
ffd6ed |
+L</INPUT FROM VMWARE OVA> below
|
|
|
ffd6ed |
|
|
|
ffd6ed |
=item B<-ic> libvirtURI
|
|
|
ffd6ed |
|
|
|
ffd6ed |
@@ -744,10 +745,9 @@ 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 |
+vCenter E<ge> 5.0 is required. Virt-v2v B<cannot> import guests
|
|
|
ffd6ed |
+directly from an ESXi hypervisor. If you don't have vCenter, using
|
|
|
ffd6ed |
+OVA is recommended instead (see L</INPUT FROM VMWARE OVA> below).
|
|
|
ffd6ed |
|
|
|
ffd6ed |
Virt-v2v uses libvirt for access to vCenter, and therefore the input
|
|
|
ffd6ed |
mode should be I<-i libvirt>. As this is the default, you don't need
|
|
|
ffd6ed |
@@ -884,6 +884,45 @@ In this case the output flags are set to write the converted guest to
|
|
|
ffd6ed |
a temporary directory as this is just an example, but you can also
|
|
|
ffd6ed |
write to libvirt or any other supported target.
|
|
|
ffd6ed |
|
|
|
ffd6ed |
+=head1 INPUT FROM VMWARE OVA
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+Virt-v2v is able to import guests from VMware's OVA (Open
|
|
|
ffd6ed |
+Virtualization Appliance) files. Only OVAs exported from VMware
|
|
|
ffd6ed |
+vSphere will work.
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+=head2 OVA: REMOVE VMWARE TOOLS FROM WINDOWS GUESTS
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+For Windows guests, you should remove VMware tools before conversion.
|
|
|
ffd6ed |
+Although this is not strictly necessary, and the guest will still be
|
|
|
ffd6ed |
+able to run, if you don't do this then the converted guest will
|
|
|
ffd6ed |
+complain on every boot. The tools cannot be removed after conversion
|
|
|
ffd6ed |
+because the uninstaller checks if it is running on VMware and refuses
|
|
|
ffd6ed |
+to start (which is also the reason that virt-v2v cannot remove them).
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+This is not necessary for Linux guests, as virt-v2v is able to remove
|
|
|
ffd6ed |
+VMware tools.
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+=head2 OVA: CREATE OVA
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+To create an OVA in vSphere, use the "Export OVF Template" option
|
|
|
ffd6ed |
+(from the VM context menu, or from the File menu). Either "Folder of
|
|
|
ffd6ed |
+files" (OVF) or "Single file" (OVA) will work, but OVA is probably
|
|
|
ffd6ed |
+easier to deal with. OVA files are really just uncompressed tar
|
|
|
ffd6ed |
+files, so you can use commands like C<tar tf VM.ova> to view their
|
|
|
ffd6ed |
+contents.
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+=head2 OVA: IMPORTING A GUEST
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+To import an OVA file called C<VM.ova>, do;
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+ $ virt-v2v -i ova VM.ova -o local -os /var/tmp
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+If you exported the guest as a "Folder of files", I<or> if you
|
|
|
ffd6ed |
+unpacked the OVA tarball yourself, then you can point virt-v2v at the
|
|
|
ffd6ed |
+directory containing the files:
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
+ $ virt-v2v -i ova /path/to/files -o local -os /var/tmp
|
|
|
ffd6ed |
+
|
|
|
ffd6ed |
=head1 INPUT FROM RHEL 5 XEN
|
|
|
ffd6ed |
|
|
|
ffd6ed |
Virt-v2v is able to import Xen guests from RHEL 5 Xen hosts.
|
|
|
ffd6ed |
--
|
|
|
ffd6ed |
1.8.3.1
|
|
|
ffd6ed |
|