Have you seen this article and is it applicable to your situation-
If you found my answers useful please consider marking them as Correct OR Helpful
I saw that article. I checked and I have not run out of space or inodes.
What version of ESXi are you running? I had this exact same issue but years ago on either 5.1 or 5.5 and the cause was some of the agents HP puts in their customized ISO had a memory leak or some other issue. It was fixed with updated versions of that agent, but you had to reboot the host to get it to service vMotions. I looked for the HPE advisory but can't find it. It may not be the same issue at all, but the symptoms are exactly the same.
daphnissov, is this what you were referring to?:
Is it only live migration of this one VM from one host to one particular host?
Or from ANY host to one particular host?
Or any VMs from one host to one particular host?
Or any VMs from any host to one particular host?
Have you tried removing the ISO that is loaded as a CD/DVD device? And/or is this accessible from all hosts?:
That sounds very familiar...maybe it's it.
No, the version I am running is ESX6.5.
It only happens with live migrations.
I have the same symptoms, also not running out of space on the hosts. Mine is a cluster and Windows based vCenter that is only used by a Horizon 7.4 environment, issue started after the last round of patches. Interesting the build number on the hosts in this environment is 6.5 7388607 and according to VUM it's fully patched and compliant with 6.5U1 ESXi upgrade but on my mixed workload environment with a vCSA, all of the hosts are on build 7526125. Exact same model of server, exact same ESXi image profile, using standard not OEM images. Not sure if related to my issues but seems odd.
Did you ever get this resolved?
I have a ticket open with support, I will post the results of that once it's sorted. My guess is I need to rebuild the hosts.
I have the same problem.
Anyone have a solution?
I had to power off both of the hosts in the cluster that was affected by this issue to resolve it however since patching the hosts a month or so ago, I haven't had it occur again.
My hosts are currently on 6.5U1 build 8294253 which is not the latest build anymore but has been stable for me.
VMware support never came up with a root cause for this unfortunately.
Did you get any update from VMware support team.I am facing similar issue.
No unfortunately not but the issue has not reoccurred since I patched to those build levels so it does appear to be a bug in an older build.