<?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>din_007 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>din_007 Tracker</description>
    <pubDate>Wed, 15 Nov 2023 11:26:20 GMT</pubDate>
    <dc:date>2023-11-15T11:26:20Z</dc:date>
    <item>
      <title>Re: VMotion failed -- Failed to start migration pre-copy.  Help!</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/VMotion-failed-Failed-to-start-migration-pre-copy-Help/m-p/2093156#M31110</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had the same problem. My fix was network configuration for the vMotion VMkernal where the subnet mask was incorrect. Once both host were on the correct subnet, vMotion was working as it should.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2018 02:25:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/VMotion-failed-Failed-to-start-migration-pre-copy-Help/m-p/2093156#M31110</guid>
      <dc:creator>din_007</dc:creator>
      <dc:date>2018-01-31T02:25:07Z</dc:date>
    </item>
  </channel>
</rss>

