Разница в Vmotion при power on - power off

Как написано в документации и многочисленных статьях, за интерфейс, через который производится VMotion, отвечает соответствующая настройка. Однако для холодных данных используется настройка provisioning или management vmkernel port, что описано в статье
Understand vMotion networking requirements (59232)

VMKernel Port for Cold Data Transfer
If any vmkernel port is configured for provisioning traffic, either through setting up a provisioning netstack, or simply enable provisioning traffic on a particular port, cold data would traverse through this port. If no vmkernel port is configured for provisioning traffic, cold data would traverse through the management vmkernel port.

VMKernel Port for Hot Data Transfer
If any vmkernel port is configured for vMotion traffic, either through setting up a vMotion netstack, or simply enable vMotion traffic on a particular port, hot data would traverse through this port. Some vmkernel port must be configured for vMotion traffic in order to perform vMotion.
Understand vMotion networking requirements (59232) - https://kb.vmware.com/s/article/59232

И даыным давно в статье WHY IS VMOTION USING THE MANAGEMENT NETWORK INSTEAD OF THE VMOTION NETWORK?
https://frankdenneman.nl/2013/02/07/why-is-vmotion-using-the-management-network-instead-of-the-vmotion-network/

Однако в версии 8 произошли изменения в протоколе - описанные в статьях
vSphere 8 vMotion Improvements
https://nielshagoort.com/2022/09/20/vsphere-8-vmotion-improvements/

VSPHERE 8 VMOTION UNIFIED DATA TRANSPORT
https://www.virtualbytes.io/vsphere-8-vmotion-unified-data-transport/

Why cold migrations of VMs in vSphere 8.0 is over 3times faster?
https://www.starwindsoftware.com/blog/why-cold-migrations-of-vms-in-vsphere-8-0-is-over-3times-faster