|
 |
5ce0c7 |
From 14c456c0f5d9caad9aedc5abb7b6a025ac09e7bd Mon Sep 17 00:00:00 2001
|
|
|
46b2f6 |
From: Pino Toscano <ptoscano@redhat.com>
|
|
|
46b2f6 |
Date: Wed, 18 Dec 2019 12:12:26 +0100
|
|
|
46b2f6 |
Subject: [PATCH] docs: remove paragraph about VMware tools on Windows
|
|
|
46b2f6 |
(RHBZ#1785528)
|
|
|
46b2f6 |
|
|
|
46b2f6 |
Starting from libguestfs/virt-v2v 1.39.12, virt-v2v attempts to
|
|
|
46b2f6 |
uninstall the VMware tools from Windows guests, so there is no need to
|
|
|
46b2f6 |
remove them manually before the conversion.
|
|
|
46b2f6 |
|
|
|
46b2f6 |
Thanks to: Ming Xie.
|
|
|
46b2f6 |
|
|
|
46b2f6 |
(cherry picked from commit 397b4a90d16f4eb116d55605cbdf3bd844108315
|
|
|
46b2f6 |
in virt-v2v)
|
|
|
46b2f6 |
---
|
|
|
46b2f6 |
v2v/virt-v2v-input-vmware.pod | 36 -----------------------------------
|
|
|
46b2f6 |
1 file changed, 36 deletions(-)
|
|
|
46b2f6 |
|
|
|
46b2f6 |
diff --git a/v2v/virt-v2v-input-vmware.pod b/v2v/virt-v2v-input-vmware.pod
|
|
|
46b2f6 |
index 3acdd773e..16ddb045f 100644
|
|
|
46b2f6 |
--- a/v2v/virt-v2v-input-vmware.pod
|
|
|
46b2f6 |
+++ b/v2v/virt-v2v-input-vmware.pod
|
|
|
46b2f6 |
@@ -106,18 +106,6 @@ If you find a folder of files called F<I<guest>.vmx>,
|
|
|
46b2f6 |
F<I<guest>.vmxf>, F<I<guest>.nvram> and one or more F<.vmdk> disk
|
|
|
46b2f6 |
images, then you can use this method.
|
|
|
46b2f6 |
|
|
|
46b2f6 |
-=head2 VMX: Remove VMware tools from Windows guests
|
|
|
46b2f6 |
-
|
|
|
46b2f6 |
-For Windows guests, you should remove VMware tools before conversion.
|
|
|
46b2f6 |
-Although this is not strictly necessary, and the guest will still be
|
|
|
46b2f6 |
-able to run, if you don't do this then the converted guest will
|
|
|
46b2f6 |
-complain on every boot. The tools cannot be removed after conversion
|
|
|
46b2f6 |
-because the uninstaller checks if it is running on VMware and refuses
|
|
|
46b2f6 |
-to start (which is also the reason that virt-v2v cannot remove them).
|
|
|
46b2f6 |
-
|
|
|
46b2f6 |
-This is not necessary for Linux guests, as virt-v2v is able to remove
|
|
|
46b2f6 |
-VMware tools.
|
|
|
46b2f6 |
-
|
|
|
46b2f6 |
=head2 VMX: Guest must be shut down
|
|
|
46b2f6 |
|
|
|
46b2f6 |
B<The guest must be shut down before conversion starts>. If you don't
|
|
|
46b2f6 |
@@ -319,18 +307,6 @@ Virt-v2v is able to import guests from VMware’s OVA (Open
|
|
|
46b2f6 |
Virtualization Appliance) files. Only OVAs exported from VMware
|
|
|
46b2f6 |
vSphere will work.
|
|
|
46b2f6 |
|
|
|
46b2f6 |
-=head2 OVA: Remove VMware tools from Windows guests
|
|
|
46b2f6 |
-
|
|
|
46b2f6 |
-For Windows guests, you should remove VMware tools before conversion.
|
|
|
46b2f6 |
-Although this is not strictly necessary, and the guest will still be
|
|
|
46b2f6 |
-able to run, if you don't do this then the converted guest will
|
|
|
46b2f6 |
-complain on every boot. The tools cannot be removed after conversion
|
|
|
46b2f6 |
-because the uninstaller checks if it is running on VMware and refuses
|
|
|
46b2f6 |
-to start (which is also the reason that virt-v2v cannot remove them).
|
|
|
46b2f6 |
-
|
|
|
46b2f6 |
-This is not necessary for Linux guests, as virt-v2v is able to remove
|
|
|
46b2f6 |
-VMware tools.
|
|
|
46b2f6 |
-
|
|
|
46b2f6 |
=head2 OVA: Create OVA
|
|
|
46b2f6 |
|
|
|
46b2f6 |
To create an OVA in vSphere, use the "Export OVF Template" option
|
|
|
46b2f6 |
@@ -383,18 +359,6 @@ Virt-v2v uses libvirt for access to vCenter, and therefore the input
|
|
|
46b2f6 |
mode should be I<-i libvirt>. As this is the default, you don't need
|
|
|
46b2f6 |
to specify it on the command line.
|
|
|
46b2f6 |
|
|
|
46b2f6 |
-=head2 vCenter: Remove VMware tools from Windows guests
|
|
|
46b2f6 |
-
|
|
|
46b2f6 |
-For Windows guests, you should remove VMware tools before conversion.
|
|
|
46b2f6 |
-Although this is not strictly necessary, and the guest will still be
|
|
|
46b2f6 |
-able to run, if you don't do this then the converted guest will
|
|
|
46b2f6 |
-complain on every boot. The tools cannot be removed after conversion
|
|
|
46b2f6 |
-because the uninstaller checks if it is running on VMware and refuses
|
|
|
46b2f6 |
-to start (which is also the reason that virt-v2v cannot remove them).
|
|
|
46b2f6 |
-
|
|
|
46b2f6 |
-This is not necessary for Linux guests, as virt-v2v is able to remove
|
|
|
46b2f6 |
-VMware tools.
|
|
|
46b2f6 |
-
|
|
|
46b2f6 |
=head2 vCenter: URI
|
|
|
46b2f6 |
|
|
|
46b2f6 |
The libvirt URI of a vCenter server looks something like this:
|
|
|
46b2f6 |
--
|
|
|
5ce0c7 |
2.18.4
|
|
|
46b2f6 |
|