<?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: VSC 2.01 + Cloning trouble in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-2-01-Cloning-trouble/m-p/5409#M503</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you try logging into the VI client using an administrator account?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 25 Jan 2011 14:11:51 GMT</pubDate>
    <dc:creator>costea</dc:creator>
    <dc:date>2011-01-25T14:11:51Z</dc:date>
    <item>
      <title>VSC 2.01 + Cloning trouble</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-2-01-Cloning-trouble/m-p/5405#M502</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 am trying out the VSC plugin and having some trouble doing a cloning of my VMs...everything works until the VM is supposed to be powered on. Then I get this : "Reason Insufficient Permission to access file, Cannot open the disk /vmfs/volumes/308947293487298374/VMNAME/vmimage.vmdk"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We use NFS with Unix security and read/write access is enabled in vmware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what are we doing wrong?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:01:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-2-01-Cloning-trouble/m-p/5405#M502</guid>
      <dc:creator>destgotit</dc:creator>
      <dc:date>2025-06-05T07:01:43Z</dc:date>
    </item>
    <item>
      <title>Re: VSC 2.01 + Cloning trouble</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-2-01-Cloning-trouble/m-p/5409#M503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you try logging into the VI client using an administrator account?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jan 2011 14:11:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-2-01-Cloning-trouble/m-p/5409#M503</guid>
      <dc:creator>costea</dc:creator>
      <dc:date>2011-01-25T14:11:51Z</dc:date>
    </item>
    <item>
      <title>Re: VSC 2.01 + Cloning trouble</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-2-01-Cloning-trouble/m-p/5414#M505</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yes, I am loggod on as an administrator...however, we just found out that if I am moving the VM to another storage (nfs also) it starts up just fine...so the problem must be on that specifik storage...will check and report back..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jan 2011 18:19:03 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-2-01-Cloning-trouble/m-p/5414#M505</guid>
      <dc:creator>destgotit</dc:creator>
      <dc:date>2011-01-25T18:19:03Z</dc:date>
    </item>
  </channel>
</rss>

