From 34b2da989021994389b6392fca06590424b7c975 Mon Sep 17 00:00:00 2001

From: Pino Toscano <ptoscano@redhat.com>

Date: Wed, 18 Dec 2019 12:12:26 +0100

Subject: [PATCH] docs: remove paragraph about VMware tools on Windows

 (RHBZ#1785528)

Starting from libguestfs/virt-v2v 1.39.12, virt-v2v attempts to

uninstall the VMware tools from Windows guests, so there is no need to

remove them manually before the conversion.

Thanks to: Ming Xie.

(cherry picked from commit 397b4a90d16f4eb116d55605cbdf3bd844108315

in virt-v2v)

---

 v2v/virt-v2v-input-vmware.pod | 36 -----------------------------------

 1 file changed, 36 deletions(-)

diff --git a/v2v/virt-v2v-input-vmware.pod b/v2v/virt-v2v-input-vmware.pod

index 3acdd773e..16ddb045f 100644

--- a/v2v/virt-v2v-input-vmware.pod

+++ b/v2v/virt-v2v-input-vmware.pod

@@ -106,18 +106,6 @@ If you find a folder of files called F<I<guest>.vmx>,

 F<I<guest>.vmxf>, F<I<guest>.nvram> and one or more F<.vmdk> disk

 images, then you can use this method.

-=head2 VMX: Remove VMware tools from Windows guests

-

-For Windows guests, you should remove VMware tools before conversion.

-Although this is not strictly necessary, and the guest will still be

-able to run, if you don't do this then the converted guest will

-complain on every boot.  The tools cannot be removed after conversion

-because the uninstaller checks if it is running on VMware and refuses

-to start (which is also the reason that virt-v2v cannot remove them).

-

-This is not necessary for Linux guests, as virt-v2v is able to remove

-VMware tools.

-

 =head2 VMX: Guest must be shut down

 B<The guest must be shut down before conversion starts>.  If you don't

@@ -319,18 +307,6 @@ Virt-v2v is able to import guests from VMware’s OVA (Open

 Virtualization Appliance) files.  Only OVAs exported from VMware

 vSphere will work.

-=head2 OVA: Remove VMware tools from Windows guests

-

-For Windows guests, you should remove VMware tools before conversion.

-Although this is not strictly necessary, and the guest will still be

-able to run, if you don't do this then the converted guest will

-complain on every boot.  The tools cannot be removed after conversion

-because the uninstaller checks if it is running on VMware and refuses

-to start (which is also the reason that virt-v2v cannot remove them).

-

-This is not necessary for Linux guests, as virt-v2v is able to remove

-VMware tools.

-

 =head2 OVA: Create OVA

 To create an OVA in vSphere, use the "Export OVF Template" option

@@ -383,18 +359,6 @@ Virt-v2v uses libvirt for access to vCenter, and therefore the input

 mode should be I<-i libvirt>.  As this is the default, you don't need

 to specify it on the command line.

-=head2 vCenter: Remove VMware tools from Windows guests

-

-For Windows guests, you should remove VMware tools before conversion.

-Although this is not strictly necessary, and the guest will still be

-able to run, if you don't do this then the converted guest will

-complain on every boot.  The tools cannot be removed after conversion

-because the uninstaller checks if it is running on VMware and refuses

-to start (which is also the reason that virt-v2v cannot remove them).

-

-This is not necessary for Linux guests, as virt-v2v is able to remove

-VMware tools.

-

 =head2 vCenter: URI

 The libvirt URI of a vCenter server looks something like this:

-- 

2.26.2