<?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: Issues with VMotioning VMs on local storage but not cold VMotion in VI: VMware ESX® 3.0 Discussions</title>
    <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Issues-with-VMotioning-VMs-on-local-storage-but-not-cold-VMotion/m-p/214490#M3656</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Shared storage is a requirement for vmotion.  Both hosts have to have access to the same volume as only the memory, cpu and network connections are moved in a vmotion.  The actual disk stays in place.  So to do a vmotion you have to have either a SAN, or iScsi or NFS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Sep 2008 19:18:18 GMT</pubDate>
    <dc:creator>TCronin</dc:creator>
    <dc:date>2008-09-10T19:18:18Z</dc:date>
    <item>
      <title>Issues with VMotioning VMs on local storage but not cold VMotion</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Issues-with-VMotioning-VMs-on-local-storage-but-not-cold-VMotion/m-p/214489#M3655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 2 ESX servers utilizng a x-over cable for VMotion for testing purposes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The local VMFS storage was setup on both. When I cold VMotion it moves the VM and disk files over. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I try to hot VMotion I get errors regarding the following: The VM has no real OS at this point as it just has a 8GB HD1. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Unable to access the file xxx.vswp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HD1 is not accessible to the destination host. Unable to access file xxx.vmdk&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Same happens with VM that has an OS on the VMDK. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 19:11:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Issues-with-VMotioning-VMs-on-local-storage-but-not-cold-VMotion/m-p/214489#M3655</guid>
      <dc:creator>chicagovm</dc:creator>
      <dc:date>2008-09-10T19:11:59Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with VMotioning VMs on local storage but not cold VMotion</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Issues-with-VMotioning-VMs-on-local-storage-but-not-cold-VMotion/m-p/214490#M3656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Shared storage is a requirement for vmotion.  Both hosts have to have access to the same volume as only the memory, cpu and network connections are moved in a vmotion.  The actual disk stays in place.  So to do a vmotion you have to have either a SAN, or iScsi or NFS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 19:18:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Issues-with-VMotioning-VMs-on-local-storage-but-not-cold-VMotion/m-p/214490#M3656</guid>
      <dc:creator>TCronin</dc:creator>
      <dc:date>2008-09-10T19:18:18Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with VMotioning VMs on local storage but not cold VMotion</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Issues-with-VMotioning-VMs-on-local-storage-but-not-cold-VMotion/m-p/214491#M3657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vmotion only works with shared SAN storage.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;duh! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thnks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 19:19:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Issues-with-VMotioning-VMs-on-local-storage-but-not-cold-VMotion/m-p/214491#M3657</guid>
      <dc:creator>chicagovm</dc:creator>
      <dc:date>2008-09-10T19:19:00Z</dc:date>
    </item>
    <item>
      <title>Re: Issues with VMotioning VMs on local storage but not cold VMotion</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Issues-with-VMotioning-VMs-on-local-storage-but-not-cold-VMotion/m-p/214492#M3658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Means Vmotion not worked with ISCSI and NFS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It only works with SAN am I correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Vijay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 23 Feb 2014 04:56:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Issues-with-VMotioning-VMs-on-local-storage-but-not-cold-VMotion/m-p/214492#M3658</guid>
      <dc:creator>vijayalka</dc:creator>
      <dc:date>2014-02-23T04:56:26Z</dc:date>
    </item>
  </channel>
</rss>

