Welcome to VirtuallyThatGuy – this is a quick blog about CBT and snapshot errors when vmotion from one host to the other with this error “vmotion fails the vm failed to resume on the destination during early power on”.

Resolution : This issue is only possible to fix via login to the specific host where the vm is residing which you can find out on the summary page of the VM. Run these commands via SSH to restart the mgmt agent

• /etc/init.d/hostd restart
• /etc/init.d/vpxa restart

After restarting the services, the host temporarily loses connection to vCenter and reconnects again. On reconnecting of the host to vCenter, the VM will still be fully operational.

Impact :There is no impact on residing VM when you restart the management agent on the host. Only current ongoing task like vMotion stops working and timeout error will popup.

## Connect to vCenters 
Connect-VIServer uk3p-vc01.lab.local, ntcp-vc01.lab.local -User "rboadi@lab.local" -Password "StandUpIfYouHateTottenham"
$vm = get-vm -name "uk3p-DC01", "uk3p-DC02", "uk3p-DC03"
$vmview = $vm | get-view
$vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec
$vmConfigSpec.changeTrackingEnabled = $false
$vmview.reconfigVM($vmConfigSpec)
$snap=$vm | New-Snapshot -Name 'Disable CBT'
$snap | Remove-Snapshot -confirm:$false