<?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: Opening a child disk fails in Virtual Disk Development Kit Discussions</title>
    <link>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278227#M165</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is a bug already on this filed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 30 Oct 2009 14:37:20 GMT</pubDate>
    <dc:creator>rahqa</dc:creator>
    <dc:date>2009-10-30T14:37:20Z</dc:date>
    <item>
      <title>Opening a child disk fails</title>
      <link>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278221#M159</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using vixDiskLibSample program provided with Windows VDDK to open a child disk and getting following error. Any suggestions what is wrong here?&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;Thanks,&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;Rajesh&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;C:\&amp;amp;gt;"C:\Program Files\VMware\VMware Virtual Disk Development Kit\bin\vixDiskLibSample.exe" -host abc -user user -password password -single -info /vmfs/volumes/voltron-storage2/rtlnxvm/rtlnxvm-000001.vmdk&lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;INFO: VixDiskLibVim: TicketLogin&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;INFO: VixDiskLibVim: TicketLogout&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;A certificate in the host's chain is based on an untrusted root.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;SSLVerifyIsEnabled: failed to open the product registry key. Assuming verification is disabled. LastError = 0&lt;/P&gt;&lt;P&gt;SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error&lt;/P&gt;&lt;P&gt;&lt;A href="NFC ERROR"&gt;&lt;/A&gt; NfcFssrvr_DiskOpen: received diskLib error 5 from server: NfcFssrvrO&lt;/P&gt;&lt;P&gt;pen: Failed to get geometry for disk '/vmfs/volumes/voltron-storage2/rtlnxvm/rtlnxvm-000001.vmdk': An error was detected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Error: &lt;A href="c:\program files\vmware\vmware virtual disk development kit\doc\sample\vixdisklibsample.cpp:388"&gt;&lt;/A&gt;  500003e83 The called function cannot be performed on partial chains. Please open the parent virtual disk&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jun 2008 17:43:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278221#M159</guid>
      <dc:creator>rtalwar</dc:creator>
      <dc:date>2008-06-24T17:43:55Z</dc:date>
    </item>
    <item>
      <title>Re: Opening a child disk fails</title>
      <link>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278222#M160</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I  think -single is what is causing the trouble, try without it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sudarsan&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>Thu, 26 Jun 2008 15:19:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278222#M160</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2008-06-26T15:19:38Z</dc:date>
    </item>
    <item>
      <title>Re: Opening a child disk fails</title>
      <link>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278223#M161</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's correct. If I do not specify -single, it will work. But I'm trying to open the child disk only by specifying VIXDISKLIB_FLAG_OPEN_SINGLE_LINK flag as mentioned in the API documentation. When I give "-single" option, program will set this flag in the Open command.&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;Rajesh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jun 2008 18:26:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278223#M161</guid>
      <dc:creator>rtalwar</dc:creator>
      <dc:date>2008-06-26T18:26:39Z</dc:date>
    </item>
    <item>
      <title>Re: Opening a child disk fails</title>
      <link>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278224#M162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Opening a remote child disk as single link does not work. Please file an SR if you have a TAM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sudarsan &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>Thu, 26 Jun 2008 21:23:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278224#M162</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2008-06-26T21:23:06Z</dc:date>
    </item>
    <item>
      <title>Re: Opening a child disk fails</title>
      <link>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278225#M163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any news on that issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tos2k&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Oct 2009 10:00:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278225#M163</guid>
      <dc:creator>tos2k</dc:creator>
      <dc:date>2009-10-14T10:00:25Z</dc:date>
    </item>
    <item>
      <title>Re: Opening a child disk fails</title>
      <link>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278226#M164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rajesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your query is answered,  please mark it as "Answered"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Oct 2009 08:04:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278226#M164</guid>
      <dc:creator>Lakshmi_Gayatri</dc:creator>
      <dc:date>2009-10-20T08:04:46Z</dc:date>
    </item>
    <item>
      <title>Re: Opening a child disk fails</title>
      <link>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278227#M165</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is a bug already on this filed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Oct 2009 14:37:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278227#M165</guid>
      <dc:creator>rahqa</dc:creator>
      <dc:date>2009-10-30T14:37:20Z</dc:date>
    </item>
    <item>
      <title>Re: Opening a child disk fails</title>
      <link>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278228#M166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Opening delta files does not work for me either:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use VixDiskLib to open vmdk files. That works for parent vmdk with both read and single. I can also open delta vmdks with read permission, but it fails with VIXDISKLIB_FLAG_OPEN_SINGLE_LINK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the status on that? Can we expect to fix that soon? Or is it an issue? Should we file a SR too?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tos2k&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Nov 2009 10:38:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Disk-Development-Kit/Opening-a-child-disk-fails/m-p/278228#M166</guid>
      <dc:creator>tos2k</dc:creator>
      <dc:date>2009-11-09T10:38:08Z</dc:date>
    </item>
  </channel>
</rss>

