A Long-Distance vMotion migration cannot complete.
Which three situations could cause this? (Choose three.)
A.
The license currently in use for the two hosts in vSphere Enterprise Edition.
B.
The round-trip time between the hosts is greater than 150 milliseconds.
C.
The virtual machine is configured to use Virtual NVMe disks.
D.
The vMotion traffic to the destination host is on the default TCP/IP stack.
E.
The license currently in use for the two hosts is vSphere Enterprise Plus Edition.
Incorrect,
this is A, B and D
See https://kb.vmware.com/s/article/2106949
BDE – Enterprise Plus Edition vice
It should be A instead of D as it’s required Enterprise Plus Edition.
Don’t understand why all other places are showing the answer C, D and E. Is there a wording trick?
Its A, B and D
I think BDE.
https://kb.vmware.com/s/article/2106949
Long Distance vMotion requirements in VMware vSphere 6.0 (2106949)
Which three situations could cause this?
A B C
* B
– The round-trip time between the hosts is greater than 150 milliseconds.
A RTT (round-trip time) latency of 150 milliseconds or less, between hosts.
* D E
– Your license must cover vMotion across long distances. The cross vCenter and long distance vMotion features require an Enterprise Plus license. For more information, see Compare vSphere Editions.
You must place the traffic related to virtual machine files transfer to the destination host on the provisioning TCP/IP stack. For more information, see the Place Traffic for Cold Migration, Cloning, and Snapshots on the Provisioning TCP/IP Stack section in the vCenter Server Host Management guide.
A, B, D are correct because E states “The license currently in use” is vSphere Enterprise Plus Edition & C Virtual NVMe disks are supported for vMotion.
I think ABD, https://kb.vmware.com/s/article/2106949