<?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 issue - Migration Failed while copying data. Busy. in vCenter™ Server Discussions</title>
    <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vMotion-issue-Migration-Failed-while-copying-data-Busy/m-p/2538493#M84674</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I received an error while trying to vMotion today:&amp;nbsp; "A general system error occurred: Migration failed while copying data. Busy."&amp;nbsp; The issue turned out to be a swap file change in 4.1.&amp;nbsp; To get the machines to vMotion again I had to change an advanced setting:&amp;nbsp; Migrate.VMotionResolveSwapType from 1 to 0.&amp;nbsp; Then everything migrated after that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopefully this will save someone the hour I spent with vmware tech support figuring this out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 03 Feb 2011 02:12:24 GMT</pubDate>
    <dc:creator>JasonBurrell</dc:creator>
    <dc:date>2011-02-03T02:12:24Z</dc:date>
    <item>
      <title>vMotion issue - Migration Failed while copying data. Busy.</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vMotion-issue-Migration-Failed-while-copying-data-Busy/m-p/2538493#M84674</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I received an error while trying to vMotion today:&amp;nbsp; "A general system error occurred: Migration failed while copying data. Busy."&amp;nbsp; The issue turned out to be a swap file change in 4.1.&amp;nbsp; To get the machines to vMotion again I had to change an advanced setting:&amp;nbsp; Migrate.VMotionResolveSwapType from 1 to 0.&amp;nbsp; Then everything migrated after that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopefully this will save someone the hour I spent with vmware tech support figuring this out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Feb 2011 02:12:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vMotion-issue-Migration-Failed-while-copying-data-Busy/m-p/2538493#M84674</guid>
      <dc:creator>JasonBurrell</dc:creator>
      <dc:date>2011-02-03T02:12:24Z</dc:date>
    </item>
    <item>
      <title>Re: vMotion issue - Migration Failed while copying data. Busy.</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vMotion-issue-Migration-Failed-while-copying-data-Busy/m-p/2538494#M84675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for this work around. Are there any specific technical reason why this has to be changed? I am just trying to document why.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jun 2011 13:56:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vMotion-issue-Migration-Failed-while-copying-data-Busy/m-p/2538494#M84675</guid>
      <dc:creator>drwoodberry</dc:creator>
      <dc:date>2011-06-02T13:56:41Z</dc:date>
    </item>
  </channel>
</rss>

