kubev2v · RichardHoch · Sep 5, 2024
diff --git a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc
@@ -146,6 +146,7 @@ You can add a source provider by using the {ocp} web console.
 :context: vmware
 :vmware:
 include::modules/adding-source-provider.adoc[leveloffset=+4]
+include::modules/selecting-migration-network-for-vmware-source-provider.adoc[leveloffset=+5]
 :vmware!:
 :context: rhv
 :rhv:

diff --git a/documentation/modules/migrating-virtual-machines-cli.adoc b/documentation/modules/migrating-virtual-machines-cli.adoc
@@ -137,6 +137,8 @@ EOF
 <1> Specify the name of the VMware `Provider` CR.
 <2> Specify the managed object reference (MOR) of the VMware host.
 <3> Specify the IP address of the VMware migration network.
++
+include::snip_vmware-esxi-nfc.adoc[]
 
 . Create a `NetworkMap` manifest to map the source and destination networks:
 +

diff --git a/documentation/modules/selecting-migration-network-for-vmware-source-provider.adoc b/documentation/modules/selecting-migration-network-for-vmware-source-provider.adoc
@@ -10,6 +10,8 @@ You can select a migration network in the {ocp} web console for a source provide
 
 Using the default network for migration can result in poor performance because the network might not have sufficient bandwidth. This situation can have a negative effect on the source platform because the disk transfer operation might saturate the network.
 
+include::snip_vmware-esxi-nfc.adoc[]
+
 .Prerequisites
 
 * The migration network must have sufficient throughput, minimum speed of 10 Gbps, for disk transfer.

diff --git a/documentation/modules/snip_vmware-esxi-nfc.adoc b/documentation/modules/snip_vmware-esxi-nfc.adoc
@@ -0,0 +1,6 @@
+:_content-type: SNIPPET
+
+[NOTE]
+====
+You can also control the network from which disks are transferred from a host by using the Network File Copy (NFC) service in vSphere.
+====
diff --git a/documentation/modules/vmware-prerequisites.adoc b/documentation/modules/vmware-prerequisites.adoc
@@ -42,6 +42,7 @@ The following minimal set of VMware privileges is required to migrate virtual ma
 2+|`Virtual machine.Interaction` privileges:
 |`Virtual machine.Interaction.Power Off`   |Allows powering off a powered-on virtual machine. This operation powers down the guest operating system.
 |`Virtual machine.Interaction.Power On`  |Allows powering on a powered-off virtual machine and resuming a suspended virtual machine.
+|`Virtual machine.Guest operating system management by VIX API`  |Allows managing a virtual machine by the VMware VIX API.
 2+a|`Virtual machine.Provisioning` privileges:
 [NOTE]
 ====
@@ -80,4 +81,12 @@ All `Virtual machine.Provisioning` privileges are required.
 2+|`Virtual machine.Snapshot management` privileges:
 |`Virtual machine.Snapshot management.Create snapshot` |Allows creation of a snapshot from the virtual machine’s current state.
 |`Virtual machine.Snapshot management.Remove Snapshot`   |Allows removal of a snapshot from the snapshot history.
+2+|`Datastore` privileges:
+|`Datastore.Browse datastore` |Allows exploring the contents of a datastore.
+|`Datastore.Low level file operations` |Allows performing low-level file operations - read, write, delete, and rename - in a datastore.
+2+|`Sessions` privileges:
+|`Sessions.Validate session` |Allows verification of the validity of a session.
+2+|`Cryptographic` privileges:
+|`Cryptographic.Decrypt` |Allows decryption of an encrypted virtual machine.
+|`Cryptographic.Direct access` |Allows access to encrypted resources.
 |===