Error : “Disconnected from virtual machine” during VM Power-On in VCD UI After Test Failover.

Products

• VMware Cloud Director

Issue/Introduction

• After performing a test failover in VCDA, VMware Cloud Director (VCD), the virtual machine failed to power on through the VCD UI.
• It was unable to power-on from the vCenter as well.
• It was throwing the error - "Disconnected from virtual machine. - Disconnected from virtual machine. - Disconnected from virtual machine"
• Error logs indicated the power-on operation was unsuccessful in vCenter:

<timestamp> info vpxd[####] [Originator@#### sub=vpxLro opID=vcd-########-####-####-####-############;activity=urn:uuid:########-####-####-####-############-##-##-##-##] [VpxLRO] -- BEGIN task-#### -- <vm_name> -- Drm.ExecuteVmPowerOnLRO -- 
<timestamp> info vpxd[####] [Originator@#### sub=vmmoVm opID=vcd-########-####-####-####-############;activity=urn:uuid:########-####-####-####-############-##-##-##-##] Powering on vm <vm_name> (ds:///vmfs/volumes/########-########/C4-########-####-####-####-############/<folder_name>/<vm_name>.vmx) in compute resource <compute_resource_name> on host <esx_name>
<timestamp> info vpxd[####] [Originator@#### sub=VdbOpJournal opID=vcd-########-####-####-####-############;activity=urn:uuid:########-####-####-####-############-##-##-##-##] Added new journal id=#### type=1
<timestamp> info vpxd[####] [Originator@#### sub=vpxLro opID=vcd-########-####-####-####-############;activity=urn:uuid:########-####-####-####-############-##-##-##-##-01] [VpxLRO] -- BEGIN lro-=#### --  -- VmWorkflow -- 
<timestamp> info vpxd[####] [Originator@#### sub=VmCheck opID=vcd-########-####-####-####-############;activity=urn:uuid:########-####-####-####-############-##-##-##-##-01] CompatCheck results: (vim.vm.check.Result) [
-->    (vim.vm.check.Result) {
-->       vm = 'vim.VirtualMachine:########-####-####-####-############:vm-=####', 
-->       host = 'vim.HostSystem:########-####-####-####-############:host-####', 
-->       warning = (vmodl.MethodFault) [
-->          (vim.fault.CannotAccessNetwork) {
-->             device = "Network adapter 1", 
-->             backing = "none", 
-->             connected = false, 
-->             network = 'vim.Network:########-####-####-####-############:network-####', 
-->             msg = "", 
-->          }
-->       ], 
-->    }
--> ]
<timestamp> info vpxd[####] [Originator@#### sub=vpxLro opID=vcd-########-####-####-####-############;activity=urn:uuid:########-####-####-####-############-##-##-##-##-01-01] [VpxLRO] -- BEGIN lro-#### --  -- SpecSyncLRO.Synchronize -- 
<timestamp> info vpxd[####] [Originator@#### sub=vpxLro opID=vcd-########-####-####-####-############;activity=urn:uuid:########-####-####-####-############-##-##-##-##-01-01] [VpxLRO] -- FINISH lro-####
<timestamp> info vpxd[####] [Originator@#### sub=Vmname opID=vcd-########-####-####-####-############;activity=urn:uuid:########-####-####-####-############-##-##-##-##-01] Powering on VM '[<vm_name>] C4-########-####-####-####-############/<folder_name>/<vm_name>.vmx' on host <esx_name>

Environment

VMware Cloud Director 10.x

VMware Cloud Director Availability 4.7.3

Cause

The VM couldn't connect to a valid network due to an invalid or missing mapping at the recovery site. During the test failover, the VM was assigned a network that either didn't exist or wasn't properly configured. Consequently, VCD couldn't validate the connection, blocking the power-on process—this is expected behavior when failover networks are unavailable or unmapped.

Resolution

• Power on the VM via vCenter UI — this bypasses VCD and establishes proper connectivity.
• Remove or detach the NIC from the VM using the VCD client.
• Re-add the correct network through VCD.
• Power on the VM successfully, confirming it is fully running in both vCenter and VCD interfaces.