[Libguestfs] [v2v PATCH] docs: remove paragraph about VMware tools on Windows
Richard W.M. Jones
rjones at redhat.com
Thu Jan 9 13:32:32 UTC 2020
On Wed, Dec 18, 2019 at 12:15:40PM +0100, Pino Toscano wrote:
> 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.
Maybe a fixes commit in the message here?
ACK.
Rich.
> docs/virt-v2v-input-vmware.pod | 36 ----------------------------------
> 1 file changed, 36 deletions(-)
>
> diff --git a/docs/virt-v2v-input-vmware.pod b/docs/virt-v2v-input-vmware.pod
> index 11adf1b6..ec905376 100644
> --- a/docs/virt-v2v-input-vmware.pod
> +++ b/docs/virt-v2v-input-vmware.pod
> @@ -107,18 +107,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
> @@ -320,18 +308,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
> @@ -384,18 +360,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.24.1
>
> _______________________________________________
> Libguestfs mailing list
> Libguestfs at redhat.com
> https://www.redhat.com/mailman/listinfo/libguestfs
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
More information about the Libguestfs
mailing list