i can do a vmotion of all my vms except one (an Microsoft exchange 2010-vm)
Migration of this vm was no problem in esxi 5.5, but is no stuck at 72% (see screenshot).
I can only break this migration by restarting the vcenter-services.
Why is the problem happening and what is the problem?
Same Problem here. I have two VMs stucking at 72%. My ESXi hosts are on Version 6.0
Last days I had one VM for days in that Status, suddenly the Task disappeard and I couldn't migrate the VM anymore. The VM was a virtual Desktop so I decided to recompose it again. I was able to delete it from the view Manager, but on the storage the machine was still there. manually deleting Fails with error: connot delete file
I had a similar issue while upgrading my hosts from 5.5 to 6.0. I had four VM's stuck at 72%, all of which were originating from the same 5.5 host. I was able to stop the stuck migrations by restarting the management services on the host in question. When the host reconnected to vcenter the VM's that were stuck were no longer in that hosts inventory. I was then able to put the host into maintenance mode and continue my upgrades. Out of 15 identical hosts, this was the only one that had this issue. I have about 60 more to upgrade, so we will see if it reoccurs.
I had same problem.
I try the following things , and I had solved.
1. move datastore
I think the virtual machine have mismatch datastore statement.
So I tried storage vMotion to another datastore, and back to original datastore.
After that , Some virtual machine solved vMotion problem.
2. use VSS
In my case , problem virtual machine use VDS, So , I migrate to VSS from VDS.
Some virtual machine solved vMotion problem.
I hope for your help
I faced the same problem at customer site and unfortunately it was production VM.
It was migrated by DRS then stuck at 72 % and couldn't cancel the migration task also.
Here is my resolution
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
After restarting the Host will be lost connection and become responsive again and will connect to the vcenter.
After reconnecting the host in vCenter, the VM is fully operational.
Impact :There will be 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.
Use web client instead of VC-client or attach vmware.log for further investigation
Had this issue for the longest time, until I realized there was CPU and Memory Reservations on the VMs that where having issues. Remove the reservation, migrate, re-apply reservations.