Storage and Compute vMotion fails when triggered by vROPs Workload Placement, but succeeds when migration is manually triggered

Products

• VMware vCenter Server
• VMware Aria Operations (formerly vRealize Operations) 8.x

Issue/Introduction

Using Workload Management in Aria Operations will fail to migrate VMs across host clusters in the vCenter vpxd logs (/var/log/vmware/vpxd/vpxd.log) with error messages similar to:

Failed waiting for data. Error 195887107. Not found.
2025-07-23T09:12:32.764497Z
vMotion migration [175137030:263017964320432507] failed to read stream keepalive: Connection closed by remote host, possibly due to timeout
Migration to host <HOST_IP> failed with error Connection closed by remote host, possibly due to timeout (195887167).
2025-07-23T09:12:32.912083Z
vMotion migration [175137030:263017964320432507] failed to get DVS state in the restore phase from the source host <HOST_IP>

Migrations triggered by users manually in the vCenter for the same source and destination host will be successful.

Environment

• VMware vCenter 8.x
• ESXi 8.x
• Aria Operations 8.18.x

Cause

There is a datapath regression issue that omits the vnicIsConnected field during the Workload Migration actions in ESXi 8.x that will cause the destination host to fail to receive the correct NIC data to boot the VM at the destination. This causes the migration to fail back to the source host.

Resolution

Engineering is aware of the issue and is actively working on a resolution.