<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic vMotion problem &amp;amp; VMware ESXi, 7.0.3, 19482537 - 20% - timeout? in vSphere™ vNetwork Discussions</title>
    <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/vMotion-problem-amp-VMware-ESXi-7-0-3-19482537-20-timeout/m-p/2915170#M14531</link>
    <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;We've recently switched from 6.7 to &lt;STRONG&gt;7.0.3, 19482537&lt;/STRONG&gt; and we had never had any similar problems with vMotion before. When a network failure occurs and it affects ESXi hosts, they go back to normal as soon as Cisco ports or the entire network environment re-balances.&lt;/P&gt;&lt;P&gt;Yesterday we had a problem to vMotion several VMs onto two ESXi hosts after such network incidents. I looked through vpxa, hostd and vmkernel logs and found:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;EM&gt;Failed waiting for data. Error 195887167. Connection closed by &lt;/EM&gt;remote&lt;EM&gt; host, possibly due to timeout.&lt;/EM&gt;&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;VMotionStream [-1407778881:4151649780786036937] failed to read stream keepalive: Connection closed by &lt;/EM&gt;remote&lt;EM&gt; host, possibly due to timeout&lt;/EM&gt;&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;cpu34:2591196)WARNING: &lt;/EM&gt;Migrate:&lt;EM&gt; 6460: 4151649780786036937 &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@B699825BEA7B9353BA12C688F8C7000B/emoticons/1f627.png" alt=":anguished_face:" title=":anguished_face:" /&gt; Migration &lt;/EM&gt;considered&lt;EM&gt; a failure by the VMX. It is most likely a timeout, but check the VMX log for the true error.&lt;/EM&gt;&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;There are a lot of entries including: Cannot open file "/vmfs/volumes/5ed12ccc-e4651386-16a9-bc97e148c8ec/VMXXX/VMXXX.vmx": Device or resource busy OR: il3: 4994: Lock failed on file: VMXXX.vmx on vol 'ST0CML1-VMFS2' with FD: &amp;lt;FD c57 r1&amp;gt;&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Based on some Cisco log entries I decided to replace SFP modules in one ESXi host (also replaced the corresponding module in Cisco) - still, was not able to vMotion any VMs.&lt;/P&gt;&lt;P&gt;The only workaround seems to be a reboot - after the reboot, problems with vMotion are gone. It means that there are no configuration problems (MTU mismatch, etc.). Not a single VM stucks at 20% again while moving it onto another host. At this moment, it's the only workaround - maybe there's a bug in 7.0.3?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Tue, 21 Jun 2022 12:38:48 GMT</pubDate>
    <dc:creator>msiem</dc:creator>
    <dc:date>2022-06-21T12:38:48Z</dc:date>
    <item>
      <title>vMotion problem &amp; VMware ESXi, 7.0.3, 19482537 - 20% - timeout?</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/vMotion-problem-amp-VMware-ESXi-7-0-3-19482537-20-timeout/m-p/2915170#M14531</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;We've recently switched from 6.7 to &lt;STRONG&gt;7.0.3, 19482537&lt;/STRONG&gt; and we had never had any similar problems with vMotion before. When a network failure occurs and it affects ESXi hosts, they go back to normal as soon as Cisco ports or the entire network environment re-balances.&lt;/P&gt;&lt;P&gt;Yesterday we had a problem to vMotion several VMs onto two ESXi hosts after such network incidents. I looked through vpxa, hostd and vmkernel logs and found:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;EM&gt;Failed waiting for data. Error 195887167. Connection closed by &lt;/EM&gt;remote&lt;EM&gt; host, possibly due to timeout.&lt;/EM&gt;&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;VMotionStream [-1407778881:4151649780786036937] failed to read stream keepalive: Connection closed by &lt;/EM&gt;remote&lt;EM&gt; host, possibly due to timeout&lt;/EM&gt;&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;cpu34:2591196)WARNING: &lt;/EM&gt;Migrate:&lt;EM&gt; 6460: 4151649780786036937 &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@B699825BEA7B9353BA12C688F8C7000B/emoticons/1f627.png" alt=":anguished_face:" title=":anguished_face:" /&gt; Migration &lt;/EM&gt;considered&lt;EM&gt; a failure by the VMX. It is most likely a timeout, but check the VMX log for the true error.&lt;/EM&gt;&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;There are a lot of entries including: Cannot open file "/vmfs/volumes/5ed12ccc-e4651386-16a9-bc97e148c8ec/VMXXX/VMXXX.vmx": Device or resource busy OR: il3: 4994: Lock failed on file: VMXXX.vmx on vol 'ST0CML1-VMFS2' with FD: &amp;lt;FD c57 r1&amp;gt;&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Based on some Cisco log entries I decided to replace SFP modules in one ESXi host (also replaced the corresponding module in Cisco) - still, was not able to vMotion any VMs.&lt;/P&gt;&lt;P&gt;The only workaround seems to be a reboot - after the reboot, problems with vMotion are gone. It means that there are no configuration problems (MTU mismatch, etc.). Not a single VM stucks at 20% again while moving it onto another host. At this moment, it's the only workaround - maybe there's a bug in 7.0.3?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 12:38:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/vMotion-problem-amp-VMware-ESXi-7-0-3-19482537-20-timeout/m-p/2915170#M14531</guid>
      <dc:creator>msiem</dc:creator>
      <dc:date>2022-06-21T12:38:48Z</dc:date>
    </item>
  </channel>
</rss>

