To work around this issue, temporarily disable the large page promotion path on destination host during vMotion, and enable the same after vMotion.
Note: After the vMotion has completed, and the large pages have been re-enabled on the destination Host, the small memory pages will be remapped to large pages as the guest touches the memory. How fast this conversion takes place is dependent on the guest workload. But every time the guest touches the page, vmkernel/monitor will opportunistically convert these small pages to large page mappings. This is all transparent to the guest.