<?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 Re: vMotion of 1 specific VM is stuck at 72 % in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721404#M268080</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;are these database VMs only in that said host or cluster?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Oct 2018 04:26:00 GMT</pubDate>
    <dc:creator>lalitsharma</dc:creator>
    <dc:date>2018-10-05T04:26:00Z</dc:date>
    <item>
      <title>vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721394#M268070</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;i can do a vmotion of all my vms except one (an Microsoft exchange 2010-vm)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Migration of this vm was no problem in esxi 5.5, but is no stuck at 72% (see screenshot).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can only break this migration by restarting the vcenter-services.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why is the problem happening and what is the problem?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="vmotion.JPG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/60652i909467051015C4D5/image-size/large?v=v2&amp;amp;px=999" role="button" title="vmotion.JPG" alt="vmotion.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jul 2015 11:34:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721394#M268070</guid>
      <dc:creator>mauser_</dc:creator>
      <dc:date>2015-07-27T11:34:41Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721395#M268071</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also attached the vmkernel.log !&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jul 2015 11:58:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721395#M268071</guid>
      <dc:creator>mauser_</dc:creator>
      <dc:date>2015-07-27T11:58:28Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721396#M268072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have developed this same issue on multiple machines in 6.0.&amp;nbsp; They stall and die at 72%&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Mar 2016 15:51:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721396#M268072</guid>
      <dc:creator>JLackman</dc:creator>
      <dc:date>2016-03-09T15:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721397#M268073</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have the same issue this morning with a View vm stuck at 72% for the past 19 hours.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Apr 2016 16:33:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721397#M268073</guid>
      <dc:creator>jdargie</dc:creator>
      <dc:date>2016-04-15T16:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721398#M268074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same Problem here. I have two VMs stucking at 72%. My ESXi hosts are on Version 6.0&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2016 16:29:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721398#M268074</guid>
      <dc:creator>eddilimp</dc:creator>
      <dc:date>2016-05-10T16:29:08Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721399#M268075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had a similar issue while upgrading my hosts from 5.5 to 6.0.&amp;nbsp; I had four VM's stuck at 72%, all of which were originating from the same 5.5 host.&amp;nbsp; I was able to stop the stuck migrations by restarting the management services on the host in question.&amp;nbsp; When the host reconnected to vcenter the VM's that were stuck were no longer in that hosts inventory.&amp;nbsp; I was then able to put the host into maintenance mode and continue my upgrades.&amp;nbsp; Out of 15 identical hosts, this was the only one that had this issue.&amp;nbsp; I have about 60 more to upgrade, so we will see if it reoccurs.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Aug 2016 22:35:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721399#M268075</guid>
      <dc:creator>cashlatham</dc:creator>
      <dc:date>2016-08-06T22:35:13Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721400#M268076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had same problem.&lt;/P&gt;&lt;P&gt;I try the following things , and I had solved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 1. move datastore&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I think the virtual machine have mismatch datastore statement.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; So I tried storage vMotion to another datastore, and back to original datastore.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; After that , Some virtual machine solved vMotion problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 2. use VSS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; In my case , problem virtual machine use VDS, So , I migrate to VSS from VDS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Some virtual machine solved vMotion problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope for your help&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2016 02:36:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721400#M268076</guid>
      <dc:creator>yamamoty</dc:creator>
      <dc:date>2016-08-16T02:36:57Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721401#M268077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I faced the same problem at customer site and unfortunately it was production VM.&lt;/P&gt;&lt;P&gt;It was migrated by DRS then stuck at 72 % and couldn't cancel the migration task also.&lt;/P&gt;&lt;P&gt;Here is my resolution&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Resolution : &lt;/STRONG&gt; 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. &lt;/P&gt;&lt;P&gt;Run these commands via SSH to restart the mgmt agent&lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI&gt;/etc/init.d/hostd restart&lt;/LI&gt;&lt;LI&gt;/etc/init.d/vpxa restart&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;After restarting the Host will be lost connection and become responsive again and will connect to the vcenter.&lt;/P&gt;&lt;P&gt;After reconnecting the host in vCenter, the VM is fully operational.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Impact :&lt;/STRONG&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Apr 2017 04:46:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721401#M268077</guid>
      <dc:creator>honeylay199</dc:creator>
      <dc:date>2017-04-06T04:46:24Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721402#M268078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use web client instead of VC-client or attach vmware.log for further investigation&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Apr 2017 05:02:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721402#M268078</guid>
      <dc:creator>RajeevVCP4</dc:creator>
      <dc:date>2017-04-06T05:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721403#M268079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That works for me. Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Aug 2017 11:34:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721403#M268079</guid>
      <dc:creator>joaorafaelassis</dc:creator>
      <dc:date>2017-08-24T11:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721404#M268080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;are these database VMs only in that said host or cluster?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2018 04:26:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721404#M268080</guid>
      <dc:creator>lalitsharma</dc:creator>
      <dc:date>2018-10-05T04:26:00Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721405#M268081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Had this issue for the longest time, until I realized there was CPU and Memory Reservations on the VMs that where having issues.&amp;nbsp; Remove the reservation, migrate, re-apply reservations.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2019 18:09:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2721405#M268081</guid>
      <dc:creator>TraMed</dc:creator>
      <dc:date>2019-12-17T18:09:36Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion of 1 specific VM is stuck at 72 %</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2852883#M276635</link>
      <description>&lt;P&gt;Thanks , this work for me &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jun 2021 23:08:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vMotion-of-1-specific-VM-is-stuck-at-72/m-p/2852883#M276635</guid>
      <dc:creator>rohanrob</dc:creator>
      <dc:date>2021-06-15T23:08:59Z</dc:date>
    </item>
  </channel>
</rss>

