<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities : All Content - Virtual Disk Development Kit</title>
    <link>http://communities.vmware.com/community/developer/forums/vddk</link>
    <description>All Content in Virtual Disk Development Kit</description>
    <language>en</language>
    <pubDate>Fri, 20 Nov 2009 15:46:31 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-11-20T15:46:31Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>How do I find the VixVolumeInfo.inGuestMountPoints for volumes that are mounted on a clean NTSF folder</title>
      <link>http://communities.vmware.com/message/1422222</link>
      <description>I have a vm guest with 2 disks… the boot disk is mounted at C: but the second disk it mounted on a founder in the C: file system. &lt;br /&gt;
&lt;br /&gt;
E.g.&lt;br /&gt;
C:\drivef is a mount point for my second disk.&lt;br /&gt;
&lt;br /&gt;
The VixVolumeInfo for the inGuestMountPoints is null so is there another way I can determine that the mound point is C:\drivef&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
-Ron</description>
      <pubDate>Fri, 20 Nov 2009 15:46:31 GMT</pubDate>
      <author>red0mark</author>
      <guid>http://communities.vmware.com/message/1422222</guid>
      <dc:date>2009-11-20T15:46:31Z</dc:date>
      <clearspace:dateToText>3 days, 12 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>VixDiskLib_Open on RDM (Raw Device Mapping) always returns VIX_E_FILE_ALREADY_LOCKED</title>
      <link>http://communities.vmware.com/message/1420232</link>
      <description>Will this be fixed in an up coming VDDK release? We don't want to power off all our vm's just to take snapshots and backup the files.&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
-Ron</description>
      <pubDate>Wed, 18 Nov 2009 15:11:35 GMT</pubDate>
      <author>red0mark</author>
      <guid>http://communities.vmware.com/message/1420232</guid>
      <dc:date>2009-11-18T15:11:35Z</dc:date>
      <clearspace:dateToText>5 days, 12 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>How to use VixDiskLib_Attach?</title>
      <link>http://communities.vmware.com/message/1414515</link>
      <description>When I want to open a delta file for writing, what is the recommended flag to use then:&lt;br /&gt;
&lt;br /&gt;
VIXDISKLIB_FLAG_OPEN_UNBUFFERED or VIXDISKLIB_FLAG_OPEN_SINGLE_LINK ? What is the difference? Where is documentation on that? &lt;br /&gt;
&lt;br /&gt;
Will the data be handled correctly by the ESX, or will the ESX write the data "directly" to the delta file specified??&lt;br /&gt;
&lt;br /&gt;
Tos2k</description>
      <pubDate>Wed, 11 Nov 2009 15:48:42 GMT</pubDate>
      <author>tos2k</author>
      <guid>http://communities.vmware.com/message/1414515</guid>
      <dc:date>2009-11-11T15:48:42Z</dc:date>
      <clearspace:dateToText>1 week, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>vmdk specification with vsphere</title>
      <link>http://communities.vmware.com/message/1413745</link>
      <description>Thin provisioned disks are a different disk type noted in disk types for VDDK 1.1.</description>
      <pubDate>Tue, 10 Nov 2009 21:10:11 GMT</pubDate>
      <author>RColbert</author>
      <guid>http://communities.vmware.com/message/1413745</guid>
      <dc:date>2009-11-10T21:10:11Z</dc:date>
      <clearspace:dateToText>1 week, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Limit on the number of mounted disks</title>
      <link>http://communities.vmware.com/message/1412818</link>
      <description>Is there a limit on the number of simultaneous virtual disk that can be mounted with vmware-mount ?&lt;br /&gt;
What about mounting VDDK ?&lt;br /&gt;
&lt;br /&gt;
Assuming I am mounting the disks on a Linux machine, is there a limit from the Linux side ?</description>
      <pubDate>Mon, 09 Nov 2009 21:42:37 GMT</pubDate>
      <author>giladb</author>
      <guid>http://communities.vmware.com/message/1412818</guid>
      <dc:date>2009-11-09T21:42:37Z</dc:date>
      <clearspace:dateToText>2 weeks, 6 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>VixDiskLib Opening delta disks (snapshots</title>
      <link>http://communities.vmware.com/message/1412291</link>
      <description>Hi!&lt;br /&gt;
I think there is nothing to fix according to the error codes.&lt;br /&gt;
Everything worx like expected:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;opening files for READ only (no limitation concerning vmdk files!)&lt;/li&gt;
&lt;li&gt;opening (parent/base) vmdk files for WRITE (SINGLE_LINK)&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
The only thing that is crashing is opening delta files with SINGLE_LINK.&lt;br /&gt;
I am assuming that this is due the format of delta files: Is there any documentation about that? Or is write access limited due undocumented format of delta files?&lt;br /&gt;
&lt;br /&gt;
Tos2k</description>
      <pubDate>Mon, 09 Nov 2009 13:29:15 GMT</pubDate>
      <author>tos2k</author>
      <guid>http://communities.vmware.com/message/1412291</guid>
      <dc:date>2009-11-09T13:29:15Z</dc:date>
      <clearspace:dateToText>2 weeks, 14 hours ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Opening a child disk fails</title>
      <link>http://communities.vmware.com/message/1412217</link>
      <description>Opening delta files does not work for me either:&lt;br /&gt;
&lt;br /&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;br /&gt;
&lt;br /&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;br /&gt;
&lt;br /&gt;
Tos2k</description>
      <pubDate>Mon, 09 Nov 2009 10:38:08 GMT</pubDate>
      <author>tos2k</author>
      <guid>http://communities.vmware.com/message/1412217</guid>
      <dc:date>2009-11-09T10:38:08Z</dc:date>
      <clearspace:dateToText>2 weeks, 17 hours ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Which version of 'fuse/libfuse' will work with VMware vMA 4.0 &amp;#38; VDDK 1.1 ?</title>
      <link>http://communities.vmware.com/message/1409869</link>
      <description>Hi,&lt;br /&gt;
&lt;br /&gt;
I have the same issue. I am working on linux suse 10 SP 1.&lt;br /&gt;
&lt;br /&gt;
I have installed fuse version 2.8.1 (and the 2.7.4 just to try).&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
&lt;pre class="jive-pre"&gt;&lt;code class="jive-code jive-plain"&gt;sles10SP164bit:~ # /etc/init.d/fuse status
Checking fuse filesystem ok.
&lt;/code&gt;&lt;/pre&gt;&lt;br /&gt;
&lt;p /&gt;
If I try to start vmware-mount I have this message:&lt;br /&gt;
&lt;br /&gt;
&lt;pre class="jive-pre"&gt;&lt;code class="jive-code jive-plain"&gt;sles10SP164bit:~ # vmware-mount -h 10.1.1.38 -u adm &amp;quot;[cbst03_lun_F] VM_for_backup/VM_for_backup.vmdk&amp;quot; /mnt/disk/
Failed to mount disk '[cbst03_lun_F] VM_for_backup/VM_for_backup.vmdk': The VMware fuse daemon failed to start

sles10SP164bit:~ # vmware-mount -h 10.1.1.38 -u adm &amp;quot;[cbst03_lun_F] VM_for_backup/VM_for_backup.vmdk&amp;quot; /mnt/disk/
Failed to mount disk '[cbst03_lun_F] VM_for_backup/VM_for_backup.vmdk': A system call has failed
&lt;/code&gt;&lt;/pre&gt;&lt;br /&gt;
&lt;p /&gt;
Any ideas?&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
&lt;br /&gt;
Mario</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">libfuse</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">fuse</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vma</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vma4.0</category>
      <pubDate>Thu, 05 Nov 2009 15:55:52 GMT</pubDate>
      <author>Tashi</author>
      <guid>http://communities.vmware.com/message/1409869</guid>
      <dc:date>2009-11-05T15:55:52Z</dc:date>
      <clearspace:dateToText>2 weeks, 20 hours ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>vmware-install.pl empty</title>
      <link>http://communities.vmware.com/message/1410617</link>
      <description>Yahoooo! That was the problem.&lt;br /&gt;
Thank you a lot for your help!&lt;br /&gt;
Mario</description>
      <pubDate>Fri, 06 Nov 2009 09:09:25 GMT</pubDate>
      <author>Tashi</author>
      <guid>http://communities.vmware.com/message/1410617</guid>
      <dc:date>2009-11-06T09:09:25Z</dc:date>
      <clearspace:dateToText>2 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>What is tmpdir used for ?</title>
      <link>http://communities.vmware.com/message/1410379</link>
      <description>You won't see these files on Linux. Perhaps rather than X days, an upper limit may be more apt ?&lt;br /&gt;
&lt;br /&gt;
On Linux, this directory is used to create partition mount points. Of course, you should not delete them while stuff is mounted.&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
Sudarsan</description>
      <pubDate>Thu, 05 Nov 2009 23:43:18 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1410379</guid>
      <dc:date>2009-11-05T23:43:18Z</dc:date>
      <clearspace:dateToText>2 weeks, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Failed to open vmdk</title>
      <link>http://communities.vmware.com/message/1409655</link>
      <description>&lt;br /&gt;
Hi, &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
   Thanks for your reply. After testing, the real connection happens at VixDiskLib_Open, but not VixDiskLib_Connect.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
   For another question, I found that I can connect to Virtual-Center, but not LAN-connect with my ESXi server.&lt;br /&gt;
&lt;p /&gt;
   After I checked the log of vmware-mount.exe(_vmount.log_), I found that it would try to access &lt;b&gt;ESXi server&lt;/b&gt; but not only &lt;b&gt;Virtual-Center&lt;/b&gt;.&lt;br /&gt;
&lt;p /&gt;
   I check the appendix section of &lt;b&gt;VDDK programming guide&lt;/b&gt;, I think this is because I tried to mount disk in LAN-mode.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
   But there is no way for vmware-mount.exe to change mount-mode. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Mission.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk1.1</category>
      <pubDate>Thu, 05 Nov 2009 12:22:20 GMT</pubDate>
      <author>MissionaryLiao</author>
      <guid>http://communities.vmware.com/message/1409655</guid>
      <dc:date>2009-11-05T12:22:20Z</dc:date>
      <clearspace:dateToText>2 weeks, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>VixDiskLib_Cleanup</title>
      <link>http://communities.vmware.com/message/1408100</link>
      <description>VixDiskLib_Cleanup : Remove leftover transports.&lt;br /&gt;
&lt;br /&gt;
If virtual machine state was not cleaned up correctly after connection shut down, VixDiskLib_Cleanup() removes extra state for each virtual machine. Its three parameters specify connection, and pass back the number of virtual machines cleaned up, and the number remaining to be cleaned up. int numCleanedUp, numRemaining; VixError vixError = VixDiskLib_Cleanup(&amp;#38;cnxParams,&amp;#38;numCleanedUp,&lt;br /&gt;
&amp;#38;numRemaining);&lt;br /&gt;
&lt;br /&gt;
-&amp;gt; VixDiskLib_Disconnect() near the end of program, and for safety add a VixDiskLib_Cleanup() call immediately afterwards.</description>
      <pubDate>Wed, 04 Nov 2009 04:39:46 GMT</pubDate>
      <author>rahqa</author>
      <guid>http://communities.vmware.com/message/1408100</guid>
      <dc:date>2009-11-04T04:39:46Z</dc:date>
      <clearspace:dateToText>2 weeks, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Writing via SAN</title>
      <link>http://communities.vmware.com/message/1407446</link>
      <description>The backup guide has some example code - we are working on an expanded sample to show some of these capabilities. &lt;br /&gt;
&lt;br /&gt;
To answer your other question, SAN does need a snapshot because of an implementation quirk. Writing via SAN is supported. &lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
-Sudarsan</description>
      <pubDate>Tue, 03 Nov 2009 16:45:35 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1407446</guid>
      <dc:date>2009-11-03T16:45:35Z</dc:date>
      <clearspace:dateToText>2 weeks, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Mapping disk to drive letter</title>
      <link>http://communities.vmware.com/message/1407445</link>
      <description>It is a bit convoluted, hopefully you can make it all work:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;You need libraries to parse the NTFS and / or FAT&lt;/li&gt;
&lt;li&gt;You also need code to parse the mbr and get the offsets for the volumes&lt;/li&gt;
&lt;li&gt;Looking at the MBR, you can find which is the system volume - and from here get either boot.ini or boot bcd.&lt;/li&gt;
&lt;li&gt;Once you have the volume offsets, you can parse the ntfs / fat file system structures to get to the boot.ini (or bcd hive) and look for the boot volume (the one that has windows directory)&lt;/li&gt;
&lt;li&gt;You can then read the registry file and parse it in anyway you like&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
There are some additional issues with dynamic volumes - but once you have the above working, it is not that difficult.&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
Sudarsan</description>
      <pubDate>Tue, 03 Nov 2009 16:42:43 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1407445</guid>
      <dc:date>2009-11-03T16:42:43Z</dc:date>
      <clearspace:dateToText>2 weeks, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>VixDiskLib Reading/Writing</title>
      <link>http://communities.vmware.com/message/1404705</link>
      <description>Probably missing "times j" in the sentence ....&lt;br /&gt;
&lt;br /&gt;
-Sudarsan</description>
      <pubDate>Fri, 30 Oct 2009 21:11:49 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1404705</guid>
      <dc:date>2009-10-30T21:11:49Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>vmware-mount of vmdk in ovf</title>
      <link>http://communities.vmware.com/message/1404421</link>
      <description>OVF format does not allow random read/write access. So mount would not work. The only way I can think of is to convert to a flat / sparse disk and mount the disk, do your modifications and re-compress it to OVF.&lt;br /&gt;
&lt;br /&gt;
Thanks.&lt;br /&gt;
Sudarsan&lt;br /&gt;
&lt;br /&gt;
PS: vmware-mount should really detect the disk to be of OVF format but goes ahead and mounts the disk, but it does not.</description>
      <pubDate>Fri, 30 Oct 2009 16:36:31 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1404421</guid>
      <dc:date>2009-10-30T16:36:31Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VDDK Logging</title>
      <link>http://communities.vmware.com/message/1403289</link>
      <description>When calling both VixDiskLib_InitEx and VixMntapi_Init my code provides all three logging functions.&lt;br /&gt;
Yet, there are still messages written to standard output, such as &lt;br /&gt;
&lt;p /&gt;
   [2009-10-29 11:51:47.209 B763BB30 info 'App'] Current working directory: /mnt/disk2/home/devel/trunk&lt;br /&gt;
   [2009-10-29 11:26:10.017 B75A3B30 trivia 'SOAP'] Sending soap request to [TCP:10.10.42.200:443]: retrieveContent&lt;br /&gt;
   [2009-10-29 11:26:10.021 B75A3B30 trivia 'SOAP'] Received soap response from [TCP:10.10.42.200:443]: retrieveContent&lt;br /&gt;
   [2009-10-29 11:26:10.022 B75A3B30 trivia 'SOAP'] Sending soap request to [TCP:10.10.42.200:443]: GetConfig&lt;br /&gt;
   [2009-10-29 11:26:10.032 B75A3B30 trivia 'SOAP'] Received soap response from [TCP:10.10.42.200:443]: GetConfig&lt;br /&gt;
&lt;p /&gt;
How can these messages be prevented, or redirected to my own logging functions ?</description>
      <pubDate>Thu, 29 Oct 2009 19:04:03 GMT</pubDate>
      <author>giladb</author>
      <guid>http://communities.vmware.com/message/1403289</guid>
      <dc:date>2009-10-29T19:04:03Z</dc:date>
      <clearspace:dateToText>3 weeks, 4 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Virtual Appliance deployment degradation on vSphere4</title>
      <link>http://communities.vmware.com/message/1398325</link>
      <description>&lt;br /&gt;
Hello esloof,&lt;br /&gt;
&lt;p /&gt;
  I use cygwin.</description>
      <pubDate>Mon, 26 Oct 2009 10:47:00 GMT</pubDate>
      <author>diego2</author>
      <guid>http://communities.vmware.com/message/1398325</guid>
      <dc:date>2009-10-26T10:47:00Z</dc:date>
      <clearspace:dateToText>4 weeks, 17 hours ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>VixDiskLib_Read/Write performance</title>
      <link>http://communities.vmware.com/message/1397234</link>
      <description>I can reproduce this behavior, I will update with status once we decide on what next.&lt;br /&gt;
&lt;br /&gt;
Thanks for pointing this out,&lt;br /&gt;
Sudarsan</description>
      <pubDate>Fri, 23 Oct 2009 17:45:40 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1397234</guid>
      <dc:date>2009-10-23T17:45:40Z</dc:date>
      <clearspace:dateToText>1 month, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>Connecting via Virtual Center</title>
      <link>http://communities.vmware.com/message/1396645</link>
      <description>Moref formats can vary from version to version and from VC to esx. As for the best way to get this during development, I use the managed object viewer, &lt;a class="jive-link-external" href="https://"&gt;https://&lt;/a&gt;&amp;lt;esx|vc&amp;gt;/mob - which gives you enough detail.&lt;br /&gt;
&lt;br /&gt;
Snapshot is required if you are planning on using SAN transport (I am not 100% sure about hotadd) - if not, you can safely ignore this parameter.&lt;br /&gt;
&lt;br /&gt;
Sudarsan</description>
      <pubDate>Fri, 23 Oct 2009 06:56:51 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1396645</guid>
      <dc:date>2009-10-23T06:56:51Z</dc:date>
      <clearspace:dateToText>1 month, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>Creating disks with type VIXDISKLIB_DISK_VMFS_THIN</title>
      <link>http://communities.vmware.com/message/1396612</link>
      <description>&lt;br /&gt;
True,&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
This has been already reported as a bug.</description>
      <pubDate>Fri, 23 Oct 2009 05:05:21 GMT</pubDate>
      <author>Lakshmi Gayatri</author>
      <guid>http://communities.vmware.com/message/1396612</guid>
      <dc:date>2009-10-23T05:05:21Z</dc:date>
      <clearspace:dateToText>1 month, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>VDDK Redistribution questions</title>
      <link>http://communities.vmware.com/message/1396240</link>
      <description>Is that a response to the files needed for Linux or for the curl question ?&lt;br /&gt;
I assume the latter.&lt;br /&gt;
Could you please answer the other question as well ?&lt;br /&gt;
&lt;br /&gt;
Thanks</description>
      <pubDate>Thu, 22 Oct 2009 19:03:23 GMT</pubDate>
      <author>giladb</author>
      <guid>http://communities.vmware.com/message/1396240</guid>
      <dc:date>2009-10-22T19:03:23Z</dc:date>
      <clearspace:dateToText>1 month, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Next VDDK Version ?</title>
      <link>http://communities.vmware.com/message/1396131</link>
      <description>Thanks!&lt;br /&gt;
&lt;br /&gt;
Some of these are on our list already. Supporting GetOSInfo on Linux will involve ntfs / registry understanding code on Linux - and is not something high on the list.&lt;br /&gt;
&lt;br /&gt;
-Sudarsan</description>
      <pubDate>Thu, 22 Oct 2009 17:45:21 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1396131</guid>
      <dc:date>2009-10-22T17:45:21Z</dc:date>
      <clearspace:dateToText>1 month, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>How to monitor vmware-mount.</title>
      <link>http://communities.vmware.com/message/1395575</link>
      <description>Hi Ayrus,&lt;br /&gt;
&lt;br /&gt;
vmware-mount doesn't show any such progress on the VI client task bar as they are related to the disk APIs (VDDK : VixMntApi) and the tasks showing progress on VI are linked with VISDK API calls. So i guess when you use the VixMntAPi API with any mount utility you program, you should be able to print out the progress within that itself.Hope that helps.&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
&lt;br /&gt;
Rahul</description>
      <pubDate>Thu, 22 Oct 2009 06:37:37 GMT</pubDate>
      <author>rahul_bck</author>
      <guid>http://communities.vmware.com/message/1395575</guid>
      <dc:date>2009-10-22T06:37:37Z</dc:date>
      <clearspace:dateToText>1 month, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VixMntapi_GetOsInfo Fails</title>
      <link>http://communities.vmware.com/message/1394995</link>
      <description>Thanks.&lt;br /&gt;
It would be helpful if you could include it in future documentation and/or header files.&lt;br /&gt;
Even better would be to simply not expose it, so it fails compilation and saves the developer a lot of precious time</description>
      <pubDate>Wed, 21 Oct 2009 16:44:52 GMT</pubDate>
      <author>giladb</author>
      <guid>http://communities.vmware.com/message/1394995</guid>
      <dc:date>2009-10-21T16:44:52Z</dc:date>
      <clearspace:dateToText>1 month, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Multiple threads created by VDDK</title>
      <link>http://communities.vmware.com/message/1394984</link>
      <description>The transport parameter I am supplying for VixDiskLib_ConnectEx is NULL.&lt;br /&gt;
All storage is local on the ESX.&lt;br /&gt;
I am running a Linux app which connects to the ESX; I prefer connecting to the VC but that's a different issue</description>
      <pubDate>Wed, 21 Oct 2009 16:04:46 GMT</pubDate>
      <author>giladb</author>
      <guid>http://communities.vmware.com/message/1394984</guid>
      <dc:date>2009-10-21T16:04:46Z</dc:date>
      <clearspace:dateToText>1 month, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>can't mount remote vmdk</title>
      <link>http://communities.vmware.com/message/1394915</link>
      <description>Hi,&lt;br /&gt;
&lt;br /&gt;
I'd like to use vmware-mount to remotely mount a vmdk on our ESX 4 server,&lt;br /&gt;
but can't seem to be able to:&lt;br /&gt;
&lt;br /&gt;
bash-3.2# vmware-mount -h esx -u root -F /root/infoblox '&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=Storage1"&gt;Storage1&lt;/a&gt;Ubuntu/Ubuntu.vmdk' /tmp/vmdk&lt;br /&gt;
Failed to open disk: Unknown error (1)&lt;br /&gt;
Failed to mount disk '&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=Storage1"&gt;Storage1&lt;/a&gt;Ubuntu/Ubuntu.vmdk': Cannot open the virtual disk&lt;br /&gt;
bash-3.2# vmware-mount -h esx -u root -F /root/infoblox '&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=Storage1"&gt;Storage1&lt;/a&gt;VMware Studio/VMware Studio.vmdk' /tmp/vmdk&lt;br /&gt;
Failed to open disk: Unknown error (1)&lt;br /&gt;
Failed to mount disk '&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=Storage1"&gt;Storage1&lt;/a&gt;VMware Studio/VMware Studio.vmdk': Cannot open the virtual disk&lt;br /&gt;
bash-3.2# vmware-mount -h esx -u root -F /root/infoblox '&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=Storage1"&gt;Storage1&lt;/a&gt;rsp-esx.vmdk' /tmp/vmdk&lt;br /&gt;
Failed to open disk: Unknown error (1)&lt;br /&gt;
Failed to mount disk '&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=Storage1"&gt;Storage1&lt;/a&gt;rsp-esx.vmdk': Cannot open the virtual disk&lt;br /&gt;
bash-3.2# &lt;br /&gt;
&lt;br /&gt;
On our ESX server, the name of the datastore is Storage1, and I can see the&lt;br /&gt;
vmdk's there:&lt;br /&gt;
&lt;br /&gt;
&lt;strike&gt;root@localhost /&lt;/strike&gt;# find /vmfs/volumes/ | grep vmdk&lt;br /&gt;
/vmfs/volumes/4ad3c6c2-bdf33934-0aaf-00304834fd8a/esxconsole-4ad3c62b-d3d4-4d04-a6f9-00304834fd8a/esxconsole-flat.vmdk&lt;br /&gt;
/vmfs/volumes/4ad3c6c2-bdf33934-0aaf-00304834fd8a/esxconsole-4ad3c62b-d3d4-4d04-a6f9-00304834fd8a/esxconsole.vmdk&lt;br /&gt;
/vmfs/volumes/4ad3c6c2-bdf33934-0aaf-00304834fd8a/Ubuntu/Ubuntu-flat.vmdk&lt;br /&gt;
/vmfs/volumes/4ad3c6c2-bdf33934-0aaf-00304834fd8a/Ubuntu/Ubuntu.vmdk&lt;br /&gt;
/vmfs/volumes/4ad3c6c2-bdf33934-0aaf-00304834fd8a/VMware Studio/VMware Studio-flat.vmdk&lt;br /&gt;
/vmfs/volumes/4ad3c6c2-bdf33934-0aaf-00304834fd8a/VMware Studio/VMware Studio.vmdk&lt;br /&gt;
/vmfs/volumes/4ad3c6c2-bdf33934-0aaf-00304834fd8a/rsp-esx-flat.vmdk&lt;br /&gt;
/vmfs/volumes/4ad3c6c2-bdf33934-0aaf-00304834fd8a/rsp-esx.vmdk&lt;br /&gt;
&lt;strike&gt;root@localhost /&lt;/strike&gt;# &lt;br /&gt;
&lt;br /&gt;
This is the vmware-mount I used:&lt;br /&gt;
&lt;br /&gt;
bash-3.2# vmware-mount -v&lt;br /&gt;
vmware-mount: option requires an argument -- 'v'&lt;br /&gt;
VMware DiskMount Utility version 2.0.1, build-156745&lt;br /&gt;
...&lt;br /&gt;
&lt;p /&gt;
Any help is appreciated.&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
&lt;br /&gt;
Kin</description>
      <pubDate>Wed, 21 Oct 2009 15:37:37 GMT</pubDate>
      <author>kinc</author>
      <guid>http://communities.vmware.com/message/1394915</guid>
      <dc:date>2009-10-21T15:37:37Z</dc:date>
      <clearspace:dateToText>1 month, 3 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>VDDK 1.0 Managed Wrapper</title>
      <link>http://communities.vmware.com/docs/DOC-9510</link>
      <description />
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">.net</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">managed</category>
      <pubDate>Wed, 11 Feb 2009 20:59:14 GMT</pubDate>
      <author>fixitchris</author>
      <guid>http://communities.vmware.com/docs/DOC-9510</guid>
      <dc:date>2009-02-11T20:59:14Z</dc:date>
      <clearspace:dateToText>1 month, 3 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>VDDK .NET wrapper?</title>
      <link>http://communities.vmware.com/message/1394749</link>
      <description>Thanks for the extra sigs.&lt;br /&gt;
&lt;br /&gt;
tos2k, can you post some code?  Are you incrementing the array by 512, keeping in mind that VB defines the upper bound instead of the array size?</description>
      <pubDate>Wed, 21 Oct 2009 13:31:11 GMT</pubDate>
      <author>fixitchris</author>
      <guid>http://communities.vmware.com/message/1394749</guid>
      <dc:date>2009-10-21T13:31:11Z</dc:date>
      <clearspace:dateToText>1 month, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>42</clearspace:replyCount>
    </item>
    <item>
      <title>VDDK redistributable size and installation</title>
      <link>http://communities.vmware.com/message/1393429</link>
      <description>The question is moved &lt;a class="jive-link-thread" href="http://communities.vmware.com/thread/237836"&gt;here.&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">installation</category>
      <pubDate>Tue, 20 Oct 2009 08:46:25 GMT</pubDate>
      <author>Lexus16</author>
      <guid>http://communities.vmware.com/message/1393429</guid>
      <dc:date>2009-10-20T08:46:25Z</dc:date>
      <clearspace:dateToText>1 month, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Open multiple disks with SAN transport</title>
      <link>http://communities.vmware.com/message/1393390</link>
      <description>&lt;br /&gt;
Vladimir,&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
you can  use VixDiskLib_Open() to open disks inside a VM(one call for one disk) and then use VixMntapi_OpenDiskSet().&lt;br /&gt;
&lt;p /&gt;
Hope this helps. &lt;br /&gt;
&lt;p /&gt;
If your query is answered, please mark as "Answered".</description>
      <pubDate>Tue, 20 Oct 2009 07:49:51 GMT</pubDate>
      <author>Lakshmi Gayatri</author>
      <guid>http://communities.vmware.com/message/1393390</guid>
      <dc:date>2009-10-20T07:49:51Z</dc:date>
      <clearspace:dateToText>1 month, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Bytes/sector for vmdk</title>
      <link>http://communities.vmware.com/message/1390812</link>
      <description>There is also a definition in vixDiskLib.h &lt;br /&gt;
&lt;br /&gt;
#define VIXDISKLIB_SECTOR_SIZE 512&lt;br /&gt;
&lt;br /&gt;
-Sudarsan</description>
      <pubDate>Thu, 15 Oct 2009 22:18:26 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1390812</guid>
      <dc:date>2009-10-15T22:18:26Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>SISTEMISTI SENIOR WINDOWS / WMWARE</title>
      <link>http://communities.vmware.com/message/1389474</link>
      <description>&lt;span class="newbb_plus_css"&gt;Salve a tutti!&lt;br /&gt;
&lt;br /&gt;
Si ricercano urgentemente due Sistemisti Senior Windows / Wmware per l'area di Verona.&lt;br /&gt;
&lt;br /&gt;
Durata del contratto: un anno.&lt;br /&gt;
&lt;br /&gt;
Gli interessati sono pregati di mandare il Curriculum Vitae a &lt;a class="jive-link-email" href="mailto:job@adfor.it"&gt;job@adfor.it&lt;/a&gt; specificando in oggetto "Candidatura Sistemista Vmware".&lt;br /&gt;
&lt;br /&gt;
Grazie e a presto.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">sistemista</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">senior</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmware</category>
      <pubDate>Wed, 14 Oct 2009 16:05:05 GMT</pubDate>
      <author>GeRiKoOnE</author>
      <guid>http://communities.vmware.com/message/1389474</guid>
      <dc:date>2009-10-14T16:05:05Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>VDDK Implementation Difficulty Question</title>
      <link>http://communities.vmware.com/message/1387943</link>
      <description>&lt;br /&gt;
I wasn't particularly concerned about trying to boot from vmdk (though that would be an awesome feature).&lt;br /&gt;
&lt;p /&gt;
Being a novice at this, I was thinking that the block level read/write capabilities of the VDDK would be enough for the MS Virtual Disk Service stack to pick up. If that were true, then it would (hopefully) be fairly easy to write a provider mode driver. I know that Paragon Software has a partitioning manager that can work with the raw VMDK format to do the internal partitioning. My hope was to integrate that same feature into the native tools provided by the host OS.&lt;br /&gt;
&lt;p /&gt;
 I'll poke around and see if I can put something together creating a VDS capable driver for VDDK.</description>
      <pubDate>Tue, 13 Oct 2009 02:05:14 GMT</pubDate>
      <author>RColbert</author>
      <guid>http://communities.vmware.com/message/1387943</guid>
      <dc:date>2009-10-13T02:05:14Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>vss-manifest.zip file  on ESX 4.0?</title>
      <link>http://communities.vmware.com/message/1387154</link>
      <description>&lt;br /&gt;
Ashwin,&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
The snapshot taken from the VI client by default does not cause VSS to get engaged while snasphotting unless you select the check box "Quiesce File system" .&lt;br /&gt;
&lt;p /&gt;
 You can do the snapshotting even via VI SDK.</description>
      <pubDate>Mon, 12 Oct 2009 10:15:50 GMT</pubDate>
      <author>Lakshmi Gayatri</author>
      <guid>http://communities.vmware.com/message/1387154</guid>
      <dc:date>2009-10-12T10:15:50Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>VxDiskLib_Create problem on non-standard filesystem</title>
      <link>http://communities.vmware.com/message/1385528</link>
      <description>Great you figured it out.&lt;br /&gt;
&lt;br /&gt;
Just so you know, that list of attributes might change from release to release.&lt;br /&gt;
&lt;br /&gt;
Also, are you sure you tried both faking the name as NTFS and mapping to drive letter at the same time - that should work.&lt;br /&gt;
&lt;br /&gt;
I agree with you about the max size property, we won't be having this conversation then.&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
Sudarsan</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vixdisklib_create</category>
      <pubDate>Fri, 09 Oct 2009 07:24:55 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1385528</guid>
      <dc:date>2009-10-09T07:24:55Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>vixDiskLib &amp;gt; Managed</title>
      <link>http://communities.vmware.com/message/1382561</link>
      <description>Do you know what is the right port to use for VixDiskLib calls?&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/message/897988"&gt;http://communities.vmware.com/message/897988&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Looks like using your wrapper worx for both, 443 as 902???&lt;br /&gt;
&lt;br /&gt;
How can I overwride the logging of VixDiskLib functions with your wrapper?&lt;br /&gt;
&lt;br /&gt;
Tos2k</description>
      <pubDate>Tue, 06 Oct 2009 14:03:41 GMT</pubDate>
      <author>tos2k</author>
      <guid>http://communities.vmware.com/message/1382561</guid>
      <dc:date>2009-10-06T14:03:41Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Changed Block Tracking</title>
      <link>http://communities.vmware.com/message/1381796</link>
      <description>&lt;br /&gt;
Another thing i would want you to confirm from the VI client front is that, when you add the line ctkEnabled (value = true), under VM edit settings -&amp;gt; options -&amp;gt; advanced -&amp;gt; configuration parameters -&amp;gt; you need to ensure that you need to add lines for the individual VMDKs. I e along with the line ctkEnabled = true, there should be other lines for the VMDKs as well. For ex : scsi0:0.ctkEnabled = true; scsi0:1.ctkEnables = true and so on.&lt;br /&gt;
&lt;p /&gt;
hope this helps&lt;br /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
Rahul &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Mon, 05 Oct 2009 19:19:50 GMT</pubDate>
      <author>rahqa</author>
      <guid>http://communities.vmware.com/message/1381796</guid>
      <dc:date>2009-10-05T19:19:50Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Can`t find best way of remote management</title>
      <link>http://communities.vmware.com/message/1375749</link>
      <description>Thanks for all of your responses guys! All the responses about using SttarWind are very helpfull. I like it cause of its reliability, high functionality and simplicity.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">iscsi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">server</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">core</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">r2</category>
      <pubDate>Mon, 28 Sep 2009 15:50:49 GMT</pubDate>
      <author>DinoPozzo</author>
      <guid>http://communities.vmware.com/message/1375749</guid>
      <dc:date>2009-09-28T15:50:49Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>12</clearspace:replyCount>
    </item>
    <item>
      <title>Using VixMntApi to create files</title>
      <link>http://communities.vmware.com/message/1370031</link>
      <description>If you are using VixMntapi to write to a powered off snapshot, it would work - of course, you should be aware that you are writing outside the control of the guest OS, so it is like taking the disk and inserting into another machine.&lt;br /&gt;
&lt;br /&gt;
So, note a few complications:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;If there are any storage / file system filter drivers in the guest, they will not be aware of these changes - so they may react badly to such changes (VSS, backup software etc.). As another example, there is no longer A/V protection for these 'off-line' writes or at least the protection is different from that provided by the guest os.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;If NTFS versions do not match, some versions of Windows will try to upgrade the new volume's NTFS. This might or might not be what you want - the same may apply to other file systems.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
-Sudarsan</description>
      <pubDate>Tue, 22 Sep 2009 01:45:23 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1370031</guid>
      <dc:date>2009-09-22T01:45:23Z</dc:date>
      <clearspace:dateToText>2 months, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Create vmdk on ESX using VDDK</title>
      <link>http://communities.vmware.com/message/1367974</link>
      <description>&lt;br /&gt;
Hello there,&lt;br /&gt;
&lt;p /&gt;
I guess you are using API to clone your disk. You specify the vmxSpec in the _Connect function, then you call _Clone method. There must be a .vmdk file existed, the _Clone method will over-write the existed .vmdk. If there is no .vmdk file existed, the _Clone method will not create the new .vmdk file for you.  &lt;br /&gt;
&lt;p /&gt;
The workaround would be &lt;br /&gt;
&lt;p /&gt;
1) you make a dummy .vmdk with the same .vmdk filename you would  clone, then call the _Clone method. &lt;br /&gt;
&lt;p /&gt;
2) use the vmware-vdiskmanger.exe to clone the vmdk, which can by-pass the vmxSpec.&lt;br /&gt;
&lt;p /&gt;
 Hope that helps! &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Fri, 18 Sep 2009 20:44:52 GMT</pubDate>
      <author>wendyxiao</author>
      <guid>http://communities.vmware.com/message/1367974</guid>
      <dc:date>2009-09-18T20:44:52Z</dc:date>
      <clearspace:dateToText>2 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>What contents are returned by VixDiskLib_Read?</title>
      <link>http://communities.vmware.com/message/1367716</link>
      <description>&lt;br /&gt;
Yvs,&lt;br /&gt;
&lt;p /&gt;
Yes, that is as I suspected.&lt;br /&gt;
&lt;p /&gt;
 Thank you for taking the time to reply.&lt;br /&gt;
&lt;p /&gt;
 Rick</description>
      <pubDate>Fri, 18 Sep 2009 16:21:09 GMT</pubDate>
      <author>RickMeier</author>
      <guid>http://communities.vmware.com/message/1367716</guid>
      <dc:date>2009-09-18T16:21:09Z</dc:date>
      <clearspace:dateToText>2 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>how to access individual file in vmdk</title>
      <link>http://communities.vmware.com/message/1367207</link>
      <description>Thanks a lot.</description>
      <pubDate>Fri, 18 Sep 2009 05:26:31 GMT</pubDate>
      <author>ashiag</author>
      <guid>http://communities.vmware.com/message/1367207</guid>
      <dc:date>2009-09-18T05:26:31Z</dc:date>
      <clearspace:dateToText>2 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Mount Support for Windows 7 and Windows 8 Server R2 Guests</title>
      <link>http://communities.vmware.com/message/1366809</link>
      <description>Cool.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">windows_7</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">windows_8_server_r2</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">mount</category>
      <pubDate>Thu, 17 Sep 2009 18:42:40 GMT</pubDate>
      <author>fixitchris</author>
      <guid>http://communities.vmware.com/message/1366809</guid>
      <dc:date>2009-09-17T18:42:40Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Running Virtualdisk mount</title>
      <link>http://communities.vmware.com/message/1366440</link>
      <description>Just to clarify, when you're working with local virtual disks (on local storage or nfs/cifs shares) vmware-mount will allow the disk to be mounted (provided to host operating system can mount it) when the VM is running. If you're using the remote capabilities of vmware-mount the VM must not be running.</description>
      <pubDate>Thu, 17 Sep 2009 13:20:09 GMT</pubDate>
      <author>jstockall</author>
      <guid>http://communities.vmware.com/message/1366440</guid>
      <dc:date>2009-09-17T13:20:09Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>Bootable vmdk file from</title>
      <link>http://communities.vmware.com/message/1366184</link>
      <description>&lt;br /&gt;
You can use the vmware converter.&lt;br /&gt;
&lt;p /&gt;
Select the option to create a physical online machine to a VM and Select only volume c:&lt;br /&gt;
&lt;p /&gt;
Vmware Converter will create a VM that contains a bootable VMDK file.&lt;br /&gt;
&lt;p /&gt;
Hope this resolved your problem&lt;br /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
Yvs</description>
      <pubDate>Thu, 17 Sep 2009 07:37:22 GMT</pubDate>
      <author>yvsvmware</author>
      <guid>http://communities.vmware.com/message/1366184</guid>
      <dc:date>2009-09-17T07:37:22Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VMX file for virtual disk</title>
      <link>http://communities.vmware.com/message/1366149</link>
      <description>&lt;br /&gt;
VDDK is used only for Virtual disk management. Through VDDK we can't get the VMX file.&lt;br /&gt;
&lt;p /&gt;
 we can't get the VMX file even through VIX. VIX has more power for getting files from guest and manage guest.&lt;br /&gt;
&lt;p /&gt;
So the only option that I know is to use HTTP APIS, there is a sample in VI SDK named getVMfiles. &lt;br /&gt;
&lt;p /&gt;
It contains the sample code for formation of http request url.  We need to form the vmxspec like ?dcPath=dataCenter&amp;#38;dsName=dataStoreName which will be recognised as a http resource&lt;br /&gt;
&lt;p /&gt;
example httpurl: &lt;a class="jive-link-external" href="https://hostname/folder/vmname?dcPath=ha-datacenter/&amp;#38;dsName=Storage"&gt;https://hostname/folder/vmname?dcPath=ha-datacenter/&amp;#38;dsName=Storage&lt;/a&gt; is used for listing the folder.&lt;br /&gt;
&lt;p /&gt;
and example httpurl: &lt;a class="jive-link-external" href="https://hostname/folder/vmname/vmname.vmx?dcPath=ha-datacenter&amp;#38;dsName=LocalStorage"&gt;https://hostname/folder/vmname/vmname.vmx?dcPath=ha-datacenter&amp;#38;dsName=LocalStorage&lt;/a&gt; is used for getting the vmx file.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Note: the new way of conveying the vmxspec using VM moref is not supported as a http resource by VI webservice  yet.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
Yvs&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Thu, 17 Sep 2009 07:12:29 GMT</pubDate>
      <author>yvsvmware</author>
      <guid>http://communities.vmware.com/message/1366149</guid>
      <dc:date>2009-09-17T07:12:29Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Virtual disk virus signature scanning</title>
      <link>http://communities.vmware.com/message/1366105</link>
      <description>&lt;br /&gt;
There are two stages of virus scan here.&lt;br /&gt;
&lt;p /&gt;
1. Virus infection in virtual disk (VMDK file):&lt;br /&gt;
&lt;p /&gt;
For this, the entire virtual disk(VMDK file) has to be scanned. This is the step that you are currently doing. &lt;br /&gt;
&lt;p /&gt;
Writing each buffer to a temporary file and then scanning that file will not be correct and will not be efficient.&lt;br /&gt;
&lt;p /&gt;
To do this you should either get the entire VMDK file locally and scan the file. Or the best way is pass the sector buffers to the AV engine. one has to live with this performance until unless the AV engine has a special support to scan huge files in mulit-threaded appraoch. &lt;br /&gt;
&lt;p /&gt;
But to boost the performance you can use reader threads and scanner thread approach where there will be no wait time for scanner thread. i..e reader threads get the data and put it ready in a buffer for scanner thread.&lt;br /&gt;
&lt;p /&gt;
But this method will not detect a virus if the virus signature is in one of the  'files' in virtual disk. Since the file layout could not be contiguous.&lt;br /&gt;
&lt;p /&gt;
2. Virtus infection in a file in virtual disk:&lt;br /&gt;
&lt;p /&gt;
The best approach here is to do a file mode mount of the VMDK file and scan the mounted file system.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
Yvs</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vm</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">disk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">image</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">virus</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">signature</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">scan</category>
      <pubDate>Thu, 17 Sep 2009 06:15:15 GMT</pubDate>
      <author>yvsvmware</author>
      <guid>http://communities.vmware.com/message/1366105</guid>
      <dc:date>2009-09-17T06:15:15Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>mounting a vmdk</title>
      <link>http://communities.vmware.com/message/1366124</link>
      <description>&lt;br /&gt;
You can also mount the remote disk. For that you atleast need a snapshot of that disk. so you can mount a remote disk of a running vm this way&lt;br /&gt;
&lt;p /&gt;
1. Take a snapshot&lt;br /&gt;
&lt;p /&gt;
2.Mount it in non-persistant mode.&lt;br /&gt;
&lt;p /&gt;
3.Unmount it.&lt;br /&gt;
&lt;p /&gt;
4.Remove the snapshot if you want.  &lt;br /&gt;
&lt;p /&gt;
This is what I was doing. Is there any other better way  to scan a running vmdk??&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
~ayrus</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmware-mount</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmdk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">disk</category>
      <pubDate>Thu, 17 Sep 2009 05:47:35 GMT</pubDate>
      <author>ayrus</author>
      <guid>http://communities.vmware.com/message/1366124</guid>
      <dc:date>2009-09-17T05:47:35Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>VDDK on Chinese system fails</title>
      <link>http://communities.vmware.com/message/1366100</link>
      <description>The current locale and  the locale of the host file system could be different.&lt;br /&gt;
&lt;br /&gt;
You can try the following:&lt;br /&gt;
&lt;p /&gt;
Convert the VDDK file name from the current locale of simplified chinese to the locale of the host file system. And pass the converted ASCII string to VDDK API.&lt;br /&gt;
&lt;p /&gt;
Also if you copy the VMDK file to the local machine and trying with the filename encoded in current locale might work fine.&lt;br /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
Yvs</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">developer</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">encoding</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">error</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">localized</category>
      <pubDate>Thu, 17 Sep 2009 05:46:32 GMT</pubDate>
      <author>yvsvmware</author>
      <guid>http://communities.vmware.com/message/1366100</guid>
      <dc:date>2009-09-17T05:46:32Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>VDDK bin/AMD64/vstor2-mntapi10.sys?</title>
      <link>http://communities.vmware.com/message/1363410</link>
      <description>Sudarsan,&lt;br /&gt;
&lt;br /&gt;
We are working on a 64 bit redistribution package.. we just don't know which version of the 64 bit vstor2-mntapi10.sys to bundle with our install.&lt;br /&gt;
&lt;br /&gt;
-Ron&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
From:   sudarsan &amp;lt;communities-emailer@vmware.com&amp;gt;&lt;br /&gt;
To:     Ron Edmark/Austin/IBM@IBMUS&lt;br /&gt;
Date:   09/14/2009 02:52 PM&lt;br /&gt;
Subject:        &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=Virtual+Disk+Development+Kit"&gt;Virtual Disk Development Kit&lt;/a&gt; New message: "VDDK bin/AMD64/vstor2-mntapi10.sys?" &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=24UTlj-2DtI-5IGf"&gt;24UTlj-2DtI-5IGf&lt;/a&gt;</description>
      <pubDate>Mon, 14 Sep 2009 20:09:29 GMT</pubDate>
      <author>red0mark</author>
      <guid>http://communities.vmware.com/message/1363410</guid>
      <dc:date>2009-09-14T20:09:29Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>VixDiskLib_Clone() Error</title>
      <link>http://communities.vmware.com/message/1357529</link>
      <description>Ok, I cant use vCenter Clone() API because source and remote host arent in the same vCenter. &lt;br /&gt;
&lt;br /&gt;
It would be nice to have this feature in future releases to avoid using ssh/scp, as waiting for copy from source to local and then local to remote is too slow.</description>
      <pubDate>Tue, 08 Sep 2009 07:52:34 GMT</pubDate>
      <author>Alberto Gonzalez</author>
      <guid>http://communities.vmware.com/message/1357529</guid>
      <dc:date>2009-09-08T07:52:34Z</dc:date>
      <clearspace:dateToText>2 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Advanced Transport Modes</title>
      <link>http://communities.vmware.com/message/1357325</link>
      <description>&lt;br /&gt;
Can you open disks with other transport modes?&lt;br /&gt;
&lt;p /&gt;
 -Sudarsan</description>
      <pubDate>Tue, 08 Sep 2009 01:12:12 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1357325</guid>
      <dc:date>2009-09-08T01:12:12Z</dc:date>
      <clearspace:dateToText>2 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>linux vmdk mount</title>
      <link>http://communities.vmware.com/message/1357324</link>
      <description>&lt;br /&gt;
Sorry, the answer is linux does not support this feature yet. VDDK comes with vixMntapi which you can use to mount a vvirtual disk in non-presistent mode.&lt;br /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
Sudarsan</description>
      <pubDate>Tue, 08 Sep 2009 01:03:33 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1357324</guid>
      <dc:date>2009-09-08T01:03:33Z</dc:date>
      <clearspace:dateToText>2 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VDDK utilities on esxi</title>
      <link>http://communities.vmware.com/message/1354413</link>
      <description>You will also have to have at least a Foundation license of ESXi(3.5). The free version does not allow this type of write access.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vixdisklib</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmware-mount</category>
      <pubDate>Thu, 03 Sep 2009 15:32:07 GMT</pubDate>
      <author>madhadr</author>
      <guid>http://communities.vmware.com/message/1354413</guid>
      <dc:date>2009-09-03T15:32:07Z</dc:date>
      <clearspace:dateToText>2 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>VMDK newbie question</title>
      <link>http://communities.vmware.com/message/1347363</link>
      <description>&lt;br /&gt;
vmware-mount on Windows mounts volumes and not disks. So simply creating a raw disk and trying to mount will fail. Perhaps that Is what is hapenning?&lt;br /&gt;
&lt;p /&gt;
-Sudarsan</description>
      <pubDate>Wed, 26 Aug 2009 18:37:42 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1347363</guid>
      <dc:date>2009-08-26T18:37:42Z</dc:date>
      <clearspace:dateToText>2 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Failed to load shared object file vixDiskLib.so</title>
      <link>http://communities.vmware.com/message/1344511</link>
      <description>&lt;br /&gt;
VixDiskLib_Init and _Connect are from vixDiskLib.so, so I am not sure what is going on here. Is the error reported really 'vixDiskLib.so' (perhaps vixDiskLibVim.so?)&lt;br /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
Sudarsan</description>
      <pubDate>Sun, 23 Aug 2009 20:46:37 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1344511</guid>
      <dc:date>2009-08-23T20:46:37Z</dc:date>
      <clearspace:dateToText>3 months, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Technology Exchange Developer Day - Demo on VDDK, a part of vStorage APIs</title>
      <link>http://communities.vmware.com/message/1340993</link>
      <description>Hello,&lt;br /&gt;
&lt;br /&gt;
We are happy to announce about our hands-on demo at Technology Exchange Developer Day 2009, Demo on VDDK(Virtual Disk Development Kit), a part of vStorage APIs&lt;br /&gt;
Presenter: Sudarsan Piduri&lt;br /&gt;
&lt;br /&gt;
Demo ID: DS-07&lt;br /&gt;
&lt;br /&gt;
Time: 5:45 - 6:45 PM&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
VixDiskLib and VixMntapi libraries can be used to manipulate virtual disks in both hosted and virtual infrastructure environments. &lt;br /&gt;
These libraries can be used to enable on-line backups of running VMs from outside the VM. This demo will illustrate some &lt;br /&gt;
additional use cases, like the use of these libraries to perform disk and file level tasks such as checking for presence of a file &lt;br /&gt;
on a powered off vm. The demo is implemented using standard C.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmworld</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">technology_exchange</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">developer_day</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vstorage</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">apis</category>
      <pubDate>Wed, 19 Aug 2009 01:58:03 GMT</pubDate>
      <author>navadavuluri</author>
      <guid>http://communities.vmware.com/message/1340993</guid>
      <dc:date>2009-08-19T01:58:03Z</dc:date>
      <clearspace:dateToText>3 months, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>VDDK logs</title>
      <link>http://communities.vmware.com/message/1339890</link>
      <description>You can provide logging callback functions in VixDiskLib_Init(Ex). &lt;br /&gt;
&lt;br /&gt;
-Sudarsan</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vixdisklib_open</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">failed</category>
      <pubDate>Tue, 18 Aug 2009 00:57:31 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1339890</guid>
      <dc:date>2009-08-18T00:57:31Z</dc:date>
      <clearspace:dateToText>3 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VixDiskLib_Cleanup always return vixError (6) - The operation is not supported for the specified parameters</title>
      <link>http://communities.vmware.com/message/1338225</link>
      <description>Ron,&lt;br /&gt;
&lt;p /&gt;
I think your connection is probably not using any advanced transports, in which case _Cleanup does not do anything. If you  are connecting without using advanced transports, cleanup returns 6 - there is nothing to cleanup.&lt;br /&gt;
&lt;br /&gt;
Thanks&lt;br /&gt;
Sudarsan</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk1.1</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vixdisklib</category>
      <pubDate>Sat, 15 Aug 2009 02:37:31 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1338225</guid>
      <dc:date>2009-08-15T02:37:31Z</dc:date>
      <clearspace:dateToText>3 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VixMntapi_GetVolumeInfo is not returning inGuestMountPoints for additional disks</title>
      <link>http://communities.vmware.com/message/1337440</link>
      <description>&lt;br /&gt;
Even I get the empty value for diskSetInfo&lt;br /&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;&amp;#38;diskSetInfo    0x0012fd88    VixDiskSetInfo * *&lt;/li&gt;
&lt;li&gt;0x016fb340 {openFlags=0 mountPath=0x00000000 &amp;lt;Bad Ptr&amp;gt; }    VixDiskSetInfo *&lt;/li&gt;
&lt;/ul&gt;
        openFlags    0    unsigned int&lt;br /&gt;
+        mountPath    0x00000000 &amp;lt;Bad Ptr&amp;gt;    char *&lt;br /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk1.1</category>
      <pubDate>Fri, 14 Aug 2009 06:51:54 GMT</pubDate>
      <author>kumars17</author>
      <guid>http://communities.vmware.com/message/1337440</guid>
      <dc:date>2009-08-14T06:51:54Z</dc:date>
      <clearspace:dateToText>3 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>17</clearspace:replyCount>
    </item>
    <item>
      <title>V Disk install on esxi - clarification needed</title>
      <link>http://communities.vmware.com/message/1334809</link>
      <description>&lt;br /&gt;
Sudarsan, &lt;br /&gt;
&lt;br /&gt;
many thanks for that. I will download the win32 version tomorrow and try that. &lt;br /&gt;
&lt;p /&gt;
I am looking to convert some pre-allocated thick vm's to be growable and then shrink them. I assume this is possible ?&lt;br /&gt;
&lt;p /&gt;
Do I have to download the vm's out of the datastore onto the xp machine before I convert them or can it do it all over the network ? For some reason some of the vm's were pre-allocated 70GB space when in fact they need nowhere near this.&lt;br /&gt;
&lt;p /&gt;
thanks again,&lt;br /&gt;
&lt;p /&gt;
Richard</description>
      <pubDate>Tue, 11 Aug 2009 19:32:01 GMT</pubDate>
      <author>richard999</author>
      <guid>http://communities.vmware.com/message/1334809</guid>
      <dc:date>2009-08-11T19:32:01Z</dc:date>
      <clearspace:dateToText>3 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>vmware-vdiskmanager.exe -p hangs</title>
      <link>http://communities.vmware.com/message/1329475</link>
      <description>&lt;br /&gt;
Hi Wendy,&lt;br /&gt;
&lt;p /&gt;
what about a fix for the problem? Is there any chance it will be fixed in the near future? &lt;br /&gt;
&lt;p /&gt;
We are planing to patch/optimize about 100 vms. Because it is run automaticaly and takes some days to complete, it would be nice to have a few as possible crashes.&lt;br /&gt;
&lt;p /&gt;
Is there any chance to get a hotfix for the vmware-diskmanager.exe? What support package would be needed to get a hotfix?&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Wed, 05 Aug 2009 09:18:40 GMT</pubDate>
      <author>killermachine188</author>
      <guid>http://communities.vmware.com/message/1329475</guid>
      <dc:date>2009-08-05T09:18:40Z</dc:date>
      <clearspace:dateToText>3 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>cannot mount vmdk (in linux) with write-permissions</title>
      <link>http://communities.vmware.com/message/1329136</link>
      <description>Thanks!!! I'll investigate converting ... I should have posted here before wasting my entire day trying to mount a vmdk that is unmountable &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmware-mount</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmdk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">mount</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">fuse</category>
      <pubDate>Tue, 04 Aug 2009 21:18:19 GMT</pubDate>
      <author>draygen</author>
      <guid>http://communities.vmware.com/message/1329136</guid>
      <dc:date>2009-08-04T21:18:19Z</dc:date>
      <clearspace:dateToText>3 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Serious Memory Leaks with VDDK 1.1 on Linux</title>
      <link>http://communities.vmware.com/message/1328680</link>
      <description>&lt;br /&gt;
Any update on this issue?  I'm seeing even more memory leaks on further calls to this library.&lt;br /&gt;
&lt;p /&gt;
  ==9440== LEAK SUMMARY:&lt;br /&gt;
==9440==    definitely lost: 17,202 bytes in 36 blocks.&lt;br /&gt;
==9440==    indirectly lost: 422,229 bytes in 9,384 blocks.&lt;br /&gt;
==9440==      possibly lost: 0 bytes in 0 blocks.&lt;br /&gt;
==9440==    still reachable: 82,564 bytes in 90 blocks.&lt;br /&gt;
==9440==         suppressed: 0 bytes in 0 blocks.&lt;br /&gt;
==9440== Reachable blocks (those to which a pointer was found) are not shown.&lt;br /&gt;
==9440== To see them, rerun with: --leak-check=full --show-reachable=yes&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
The biggest difference between my test program and Mitch's above is that I also called  VixDiskLib_GetInfo() after the VixDiskLib_Open() call, and then a corresponding VixDiskLib_FreeInfo() call right before the  VixDiskLib_Close() call.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
I haven't run valgrind against IO calls yet, but that's a lot of memory to lose on just an init, connect, getinfo, freeinfo, close, disconnet,  exit chain of function calls.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">memory</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">leak</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk</category>
      <pubDate>Tue, 04 Aug 2009 14:52:13 GMT</pubDate>
      <author>UniBill</author>
      <guid>http://communities.vmware.com/message/1328680</guid>
      <dc:date>2009-08-04T14:52:13Z</dc:date>
      <clearspace:dateToText>3 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Windows volume mount warning for BCD &amp;#38; boot.ini?</title>
      <link>http://communities.vmware.com/message/1326361</link>
      <description>All,&lt;br /&gt;
&lt;br /&gt;
What is this error and how does one correct it? I've run chkdsk &amp;#38; fixmbr on the virtual machine and my local machine but on luck so far. I see&lt;br /&gt;
this only on one on my vm systems. The VDDK 1.1 host system is XP Pro SP3 and the vm guest is also XP Pro SP3 on an ESXi server.&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
-Ron&lt;br /&gt;
&lt;br /&gt;
Warning: Unable to copyfile \\.\vstor2-mntapi10-AAC5AAC5007E00000000000002000000\\Boot\BCD to C:\DOCUME~1\edmark\LOCALS~1\Temp\vmware-edmark-1007\vixmntapi2, error = 3.&lt;br /&gt;
Warning: Error reading boot.ini file \\.\vstor2-mntapi10-AAC5AAC5007E00000000000002000000&lt;br clear="all" /&gt;boot.ini&lt;br /&gt;
type: VIXMNTAPI_BASIC_PARTITION=1&lt;br /&gt;
symbolicLink: \\.\vstor2-mntapi10-AAC5AAC5007E00000000000002000000\&lt;br /&gt;
isMounted: True&lt;br /&gt;
inGuestMountPoints: C:</description>
      <pubDate>Fri, 31 Jul 2009 15:49:04 GMT</pubDate>
      <author>red0mark</author>
      <guid>http://communities.vmware.com/message/1326361</guid>
      <dc:date>2009-07-31T15:49:04Z</dc:date>
      <clearspace:dateToText>3 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Problem installing VDDK on Vista 64-bit</title>
      <link>http://communities.vmware.com/message/1318935</link>
      <description>net start vstor2-mntapi10 -&amp;gt; err 2185, "The service name is invalid."&lt;br /&gt;
 Yahoo, catch-22.&lt;br /&gt;
&lt;br /&gt;
A reboot hadn't helped, I had tried that.&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://..."&gt;http://...&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Ok, after running devmgmt and uninstalling the device, then running&lt;br /&gt;
through the registry with regedit and a registry cleaner and removing&lt;br /&gt;
anything that has anything to do with "vstor2" and then rebooting, the&lt;br /&gt;
install succeeded.&lt;br /&gt;
&lt;br /&gt;
Thanks, Sudarsan.&lt;br /&gt;
&lt;br /&gt;
&lt;ul class="jive-dash"&gt;

&lt;ul class="jive-dash"&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/ul&gt;
Clark</description>
      <pubDate>Thu, 23 Jul 2009 14:10:07 GMT</pubDate>
      <author>tcjarvis</author>
      <guid>http://communities.vmware.com/message/1318935</guid>
      <dc:date>2009-07-23T14:10:07Z</dc:date>
      <clearspace:dateToText>4 months, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Creation of VMFS file system taking longer time on ESX server 3.5 Update 3</title>
      <link>http://communities.vmware.com/message/1318556</link>
      <description>&lt;br /&gt;
Hi All,&lt;br /&gt;
&lt;p /&gt;
I need help on to identify the issue while creating the datastore on ESX server 3.5 with Update 3. The issue is it is taking very long time to create VMFS file system. I am using third party vendor SAN, created VDisk and mapped the VDisk using FC to the esx server. I am using this LUN and creating datastore.It is taking longer time to create datastore and sometimes it is failing also. What might be the issue? Is the LUN and VPort are not good state, if so how to identify the state of the path?&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks,&lt;br /&gt;
&lt;p /&gt;
--Satya.</description>
      <pubDate>Thu, 23 Jul 2009 06:11:01 GMT</pubDate>
      <author>satyakada</author>
      <guid>http://communities.vmware.com/message/1318556</guid>
      <dc:date>2009-07-23T06:11:01Z</dc:date>
      <clearspace:dateToText>4 months, 3 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>vmware-mount behaviour</title>
      <link>http://communities.vmware.com/message/1318364</link>
      <description>&lt;br /&gt;
No copy is made during vmware-mount operation so there is no space requirement based on the size of the disk/volume. Are the machines connected to the esx in the same way? Perhaps logs would be helpful in diagnosing.&lt;br /&gt;
&lt;p /&gt;
 -Sudarsan</description>
      <pubDate>Wed, 22 Jul 2009 21:21:54 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1318364</guid>
      <dc:date>2009-07-22T21:21:54Z</dc:date>
      <clearspace:dateToText>4 months, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>How to do mapping between disks(OS level) and vmdks?</title>
      <link>http://communities.vmware.com/message/1318362</link>
      <description>&lt;br /&gt;
The 'mount point' of the new volume is returned through the symbolic link. You can use it to create a mount point / map to a drive letter or simply open the volume device and start using the volume.&lt;br /&gt;
&lt;p /&gt;
Thanks &lt;br /&gt;
&lt;p /&gt;
 -Sudarsan</description>
      <pubDate>Wed, 22 Jul 2009 21:17:31 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1318362</guid>
      <dc:date>2009-07-22T21:17:31Z</dc:date>
      <clearspace:dateToText>4 months, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>File name and sector number</title>
      <link>http://communities.vmware.com/message/1318310</link>
      <description>&lt;br /&gt;
Sorry for the delay, but to get the file's extents, the utility needs to understand the file system.VDDK does not have any file system knowledge. &lt;br /&gt;
&lt;p /&gt;
 If you are working on Windows you can mount the volume and use WIN32 api's to get the extents of a file. On Linux, you will need to use the file system specific libraries to do this.&lt;br /&gt;
&lt;p /&gt;
-Sudarsan&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Wed, 22 Jul 2009 21:04:50 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1318310</guid>
      <dc:date>2009-07-22T21:04:50Z</dc:date>
      <clearspace:dateToText>4 months, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Prepare to shrink. it's not working in offline mode</title>
      <link>http://communities.vmware.com/message/1316502</link>
      <description>Hi all &lt;br /&gt;
&lt;br /&gt;
I'm using these commands to shrink my 4 GB dynamic vmdk disk:&lt;br /&gt;
&lt;br /&gt;
vmware-vdiskmanager -d "C:\Virtual Machines\w2kpro\w2kpro.vmdk"&lt;br /&gt;
vmware-mount J: "C:\Virtual Machines\w2kpro\w2kpro.vmdk" /v:1&lt;br /&gt;
vmware-vdiskmanager -p J:&lt;br /&gt;
vmware-mount J: /d&lt;br /&gt;
vmware-vdiskmanager -k "C:\Virtual Machines\w2kpro\w2kpro.vmdk"&lt;br /&gt;
&lt;br /&gt;
and the size for reduces with about 200 MB every time I run the batch&lt;br /&gt;
&lt;br /&gt;
If I start the gust OS and Prepare to shrink through VMware tool manually in the control panel and just power off guest OS with out the shrink option and run&lt;br /&gt;
vmware-vdiskmanager -k "C:\Virtual Machines\w2kpro\w2kpro.vmdk" then the vmdk file resize from 4 GB to 1,6 GB, in offline mode.&lt;br /&gt;
it must be something with the mapping of vmdk file.&lt;br /&gt;
&lt;br /&gt;
Is there anyone ho know what the problem is?</description>
      <pubDate>Tue, 21 Jul 2009 11:20:29 GMT</pubDate>
      <author>Kim76</author>
      <guid>http://communities.vmware.com/message/1316502</guid>
      <dc:date>2009-07-21T11:20:29Z</dc:date>
      <clearspace:dateToText>4 months, 5 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Virtual Disk Development Kit -  Session Abstract for Technology Exchange - Developer Day</title>
      <link>http://communities.vmware.com/message/1314019</link>
      <description>Folks, &lt;br /&gt;
&lt;br /&gt;
This is one of most popular sessions. In case you did not catch Sudarsan in our last &lt;a class="jive-link-external" href="http://communities.vmware.com/blogs/DeveloperCenter/2009/07/01/announcing-the-vmware-coffee-talk-live-webinars-first-wed-of-the-month-900-am-1000-am-pst"&gt;Coffee Talk Webinar&lt;/a&gt;this is a great opportunity to meet him and ask questions, or find out what he has planned for future versions of the VDDK. &lt;br /&gt;
&lt;br /&gt;
{youtube}&lt;a class="jive-link-external" href="http://www.youtube.com/watch?v=_wghgHpbuhc"&gt;http://www.youtube.com/watch?v=_wghgHpbuhc&lt;/a&gt;{youtube}&lt;br /&gt;
&lt;p /&gt;
Register for the VMware Technology Exchange - Developer Day &lt;a class="jive-link-external" href="http://communities.vmware.com/community/developer/techexchange"&gt;http://communities.vmware.com/community/developer/techexchange&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Session ID&lt;/b&gt;: VS-06&lt;br /&gt;
&lt;b&gt;Title&lt;/b&gt;: Introduction to Virtual Disk Development Kit (Key part of vStorage APIs solution)&lt;br /&gt;
VMware Virtual Disk Development Kit (VDDK) is a C API targeted at software developers. Part of vStorage APIs, the VDDK provides location transparent access to virtual disks – well suited for use cases such as backup, offline compliance checking and management / manipulation of virtual disks.  This session will focus on Virtual Disk basics, VDDK APIs and the new features of VDDK 1.1 release.&lt;br /&gt;
&lt;b&gt;Level&lt;/b&gt;: Beginner&lt;br /&gt;
&lt;br /&gt;
Speaker: &lt;br /&gt;
Sudarsan Piduri Staff Engineer R&amp;#38;D Virtual Infrastructure has been working at VMware for the last three years - in addition to VDDK, I work on VMware Converter. Before VMware, I was developing backup/restore software. I enjoy hiking and running.&lt;br /&gt;
&lt;br /&gt;
Added Sudarsan's video</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">technology_exchange</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">developer</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">day</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">sdk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">virtual</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">disk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmworld</category>
      <pubDate>Fri, 17 Jul 2009 16:02:47 GMT</pubDate>
      <author>heyitspablo</author>
      <guid>http://communities.vmware.com/message/1314019</guid>
      <dc:date>2009-07-17T16:02:47Z</dc:date>
      <clearspace:dateToText>4 months, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>Unable to get a VIM ticket for this virtual disk.</title>
      <link>http://communities.vmware.com/message/1309660</link>
      <description>&lt;br /&gt;
Got it! You're the best! I was reading some of your post before I added mine... I found the VM in question under the "Discovered Virtual Machines" I just moved them under the datacenter, and it worked....Thanks for the help!!!</description>
      <pubDate>Mon, 13 Jul 2009 17:26:39 GMT</pubDate>
      <author>cesarmc3</author>
      <guid>http://communities.vmware.com/message/1309660</guid>
      <dc:date>2009-07-13T17:26:39Z</dc:date>
      <clearspace:dateToText>4 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>VixDiskLib_Clone() just for conversion?</title>
      <link>http://communities.vmware.com/message/1309132</link>
      <description>&lt;br /&gt;
I actually want to just create a copy of a virtual disk on the same ESX.&lt;br /&gt;
&lt;p /&gt;
When I do that I get an error that it could not find the file. From the logs it seems it triws to open the vmdk locally on the machine where I run my application.&lt;br /&gt;
&lt;p /&gt;
Any thoughts?</description>
      <pubDate>Mon, 13 Jul 2009 08:00:58 GMT</pubDate>
      <author>nicok</author>
      <guid>http://communities.vmware.com/message/1309132</guid>
      <dc:date>2009-07-13T08:00:58Z</dc:date>
      <clearspace:dateToText>4 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Multithreading Clone</title>
      <link>http://communities.vmware.com/message/1308748</link>
      <description>&lt;br /&gt;
For local vmdk's, there should be no problem. For vmdk's on datastores, clone has the same limitations as open.&lt;br /&gt;
&lt;p /&gt;
-Sudarsan&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk1.1</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">developer</category>
      <pubDate>Sun, 12 Jul 2009 06:22:33 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1308748</guid>
      <dc:date>2009-07-12T06:22:33Z</dc:date>
      <clearspace:dateToText>4 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Prevent vmware-mount.exe run as daemon</title>
      <link>http://communities.vmware.com/message/1308742</link>
      <description>&lt;br /&gt;
You are right about not needing to leave the binary running. It is a fairly small footprint however.&lt;br /&gt;
&lt;p /&gt;
Regarding Pyhton script,  it may be a problem of the script integration rather than not flushing, we had a similar issue with perl earlier - but was fixed in perl script itself.&lt;br /&gt;
&lt;p /&gt;
-Sudarsan</description>
      <pubDate>Sun, 12 Jul 2009 06:02:47 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1308742</guid>
      <dc:date>2009-07-12T06:02:47Z</dc:date>
      <clearspace:dateToText>4 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>VixDiskLib_Open fails while connecting through vCenter</title>
      <link>http://communities.vmware.com/message/1300617</link>
      <description>&lt;br /&gt;
In "vmPath=ha-datacenter/vm/Win 2k3 -x86" try replacing "ha-datacenter" with the name of the datacenter that you created in vCenter.&lt;br /&gt;
&lt;p /&gt;
The string "ha-datacenter" is a place holder when connecting directly to a ESX/ESXi host.&lt;br /&gt;
&lt;p /&gt;
In vCenter, ESX/ESXi hosts are part of datacenters.&lt;br /&gt;
&lt;p /&gt;
Hopefully this should solve the problem. &lt;br /&gt;
&lt;p /&gt;
Regards&lt;br /&gt;
&lt;p /&gt;
Swapnil D.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk</category>
      <pubDate>Thu, 02 Jul 2009 01:09:39 GMT</pubDate>
      <author>Swapnil D</author>
      <guid>http://communities.vmware.com/message/1300617</guid>
      <dc:date>2009-07-02T01:09:39Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VixDiskLibGenericLogFunc</title>
      <link>http://communities.vmware.com/message/1300420</link>
      <description>&lt;br /&gt;
#define VDDK_LOG_FILE "c:\\temp&lt;br clear="all" /&gt;LogFunc.log"&lt;br /&gt;
&lt;p /&gt;
#define VDDK_WARN_FILE "c:\\temp&lt;br clear="all" /&gt;WarnFunc.log"&lt;br /&gt;
&lt;p /&gt;
#define VDDK_PANIC_FILE "c:\\temp&lt;br clear="all" /&gt;PanicFunc.log"&lt;br /&gt;
&lt;p /&gt;
CRITICAL_SECTION g_arrCriticalSections[3];&lt;br /&gt;
&lt;p /&gt;
somewhere at the beginning ...&lt;br /&gt;
&lt;p /&gt;
::InitializeCriticalSection(&amp;#38;g_arrCriticalSections[0]); &lt;br /&gt;
&lt;p /&gt;
::InitializeCriticalSection(&amp;#38;g_arrCriticalSections[1]); &lt;br /&gt;
&lt;p /&gt;
::InitializeCriticalSection(&amp;#38;g_arrCriticalSections[2]); &lt;br /&gt;
&lt;p /&gt;
somewhere at the end...&lt;br /&gt;
&lt;p /&gt;
::DeleteCriticalSection(&amp;#38;g_arrCriticalSections[0]); &lt;br /&gt;
&lt;p /&gt;
::DeleteCriticalSection(&amp;#38;g_arrCriticalSections[1]); &lt;br /&gt;
&lt;p /&gt;
::DeleteCriticalSection(&amp;#38;g_arrCriticalSections[2]); &lt;br /&gt;
&lt;p /&gt;
void LogFunc(const char *format, va_list info)&lt;br /&gt;
&lt;p /&gt;
{&lt;br /&gt;
&lt;p /&gt;
FILE* stream;&lt;br /&gt;
&lt;p /&gt;
errno_t err;&lt;br /&gt;
&lt;p /&gt;
::EnterCriticalSection(&amp;#38;g_arrCriticalSections[0]); &lt;br /&gt;
&lt;p /&gt;
if((err = fopen_s( &amp;#38;stream, VDDK_LOG_FILE, "a" )) !=0 )&lt;br /&gt;
&lt;p /&gt;
std::cout&amp;lt;&amp;lt;"The file "&amp;lt;&amp;lt;VDDK_LOG_FILE&amp;lt;&amp;lt;" was not opened."&amp;lt;&amp;lt;std::endl;&lt;br /&gt;
&lt;p /&gt;
else&lt;br /&gt;
&lt;p /&gt;
{&lt;br /&gt;
&lt;p /&gt;
vfprintf(stream, format, info);&lt;br /&gt;
&lt;p /&gt;
fclose(stream);&lt;br /&gt;
&lt;p /&gt;
}&lt;br /&gt;
&lt;p /&gt;
::LeaveCriticalSection(&amp;#38;g_arrCriticalSections[0]);&lt;br /&gt;
&lt;p /&gt;
}&lt;br /&gt;
&lt;p /&gt;
void WarnFunc(const char *format, va_list info)&lt;br /&gt;
&lt;p /&gt;
{&lt;br /&gt;
&lt;p /&gt;
FILE* stream;&lt;br /&gt;
&lt;p /&gt;
errno_t err;&lt;br /&gt;
&lt;p /&gt;
::EnterCriticalSection(&amp;#38;g_arrCriticalSections[1]); &lt;br /&gt;
&lt;p /&gt;
if((err = fopen_s( &amp;#38;stream, VDDK_WARN_FILE, "a" )) !=0 )&lt;br /&gt;
&lt;p /&gt;
std::cout&amp;lt;&amp;lt;"The file "&amp;lt;&amp;lt;VDDK_WARN_FILE&amp;lt;&amp;lt;" was not opened."&amp;lt;&amp;lt;std::endl;&lt;br /&gt;
&lt;p /&gt;
else&lt;br /&gt;
&lt;p /&gt;
{&lt;br /&gt;
&lt;p /&gt;
vfprintf(stream, format, info);&lt;br /&gt;
&lt;p /&gt;
fclose(stream);&lt;br /&gt;
&lt;p /&gt;
}&lt;br /&gt;
&lt;p /&gt;
::LeaveCriticalSection(&amp;#38;g_arrCriticalSections[1]);&lt;br /&gt;
&lt;p /&gt;
}&lt;br /&gt;
&lt;p /&gt;
void PanicFunc(const char *format, va_list info)&lt;br /&gt;
&lt;p /&gt;
{&lt;br /&gt;
&lt;p /&gt;
FILE* stream;&lt;br /&gt;
&lt;p /&gt;
errno_t err;&lt;br /&gt;
&lt;p /&gt;
::EnterCriticalSection(&amp;#38;g_arrCriticalSections[2]); &lt;br /&gt;
&lt;p /&gt;
if((err = fopen_s( &amp;#38;stream, VDDK_PANIC_FILE, "a" )) !=0 )&lt;br /&gt;
&lt;p /&gt;
std::cout&amp;lt;&amp;lt;"The file "&amp;lt;&amp;lt;VDDK_PANIC_FILE&amp;lt;&amp;lt;" was not opened."&amp;lt;&amp;lt;std::endl;&lt;br /&gt;
&lt;p /&gt;
else&lt;br /&gt;
&lt;p /&gt;
{&lt;br /&gt;
&lt;p /&gt;
vfprintf(stream, format, info);&lt;br /&gt;
&lt;p /&gt;
fclose(stream);&lt;br /&gt;
&lt;p /&gt;
}&lt;br /&gt;
&lt;p /&gt;
::LeaveCriticalSection(&amp;#38;g_arrCriticalSections[2]);&lt;br /&gt;
&lt;p /&gt;
}</description>
      <pubDate>Wed, 01 Jul 2009 20:04:00 GMT</pubDate>
      <author>Swapnil D</author>
      <guid>http://communities.vmware.com/message/1300420</guid>
      <dc:date>2009-07-01T20:04:00Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VDDK and Visual Studio</title>
      <link>http://communities.vmware.com/message/1300412</link>
      <description>&lt;br /&gt;
vixDiskLib.lib is just to satisfy the link time dependencies.&lt;br /&gt;
&lt;p /&gt;
Try executing the app from the directory that has the vixDiskLib.dll or adding the path to the VDDK bin folder (C:\Program Files\VMware\VMware Virtual Disk Development Kit\bin)  to your environment PATH variable.&lt;br /&gt;
&lt;p /&gt;
Hope this helps&lt;br /&gt;
&lt;p /&gt;
Regards&lt;br /&gt;
&lt;p /&gt;
Swapnil D. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Wed, 01 Jul 2009 19:54:48 GMT</pubDate>
      <author>Swapnil D</author>
      <guid>http://communities.vmware.com/message/1300412</guid>
      <dc:date>2009-07-01T19:54:48Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VMware Coffee Talk Bio - Sudarsan Piduri</title>
      <link>http://communities.vmware.com/docs/DOC-10291</link>
      <description>&lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/6161/sudarsan.bmp" alt="http://communities.vmware.com/servlet/JiveServlet/downloadImage/6161/sudarsan.bmp" class="jive-image"  /&gt; &lt;br /&gt;
&lt;br /&gt;
Sudarsan Piduri&lt;br /&gt;
Staff Engineer, R&amp;#38;D: Virtual Infrastructure Management&lt;br /&gt;
I have been working at VMware for the last three years - in addition to VDDK, I work on VMware Converter. Before VMware, I was developing backup/restore software. I enjoy hiking and running. BTW, I use 'Suda' when at a coffee shop &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">coffee_talk_bio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk</category>
      <pubDate>Wed, 01 Jul 2009 18:28:12 GMT</pubDate>
      <author>heyitspablo</author>
      <guid>http://communities.vmware.com/docs/DOC-10291</guid>
      <dc:date>2009-07-01T18:28:12Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Virtual Disk Development Kit - Coffee Talk Webinar July 1st 2009 - 9:00AM  - 10:00AM PST</title>
      <link>http://communities.vmware.com/message/1268441</link>
      <description>Folks, &lt;br /&gt;
&lt;br /&gt;
VDDK - PDF Attached &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt; &lt;br /&gt;
&lt;br /&gt;
We are happy to have Sudarsan Piduri present on the Virtual Disk Development Kit 1.1. Please join use July 1, 2009 &lt;br /&gt;
&lt;p /&gt;
Presentation PDF and Recording will be posted on our &lt;a class="jive-link-blogpost" href="http://communities.vmware.com/blogs/DeveloperCenter/2009/08/07/announcing-the-vmware-coffee-talk-live-webinars-first-wed-of-the-month-900-am-1000-am-pst"&gt;Coffee Talk Webinar Blog&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;Where:&lt;/b&gt; Web Ex Con-Call - Details Below &lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;Session Title&lt;/b&gt;: Virtual Disk Development Kit 1.1 &lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;Abstract:&lt;/b&gt; VMware Virtual Disk Development Kit (VDDK) is primarily a C API targeted to software developers. It provides location transparent access to virtual disks &amp;ndash; well suited for use cases like backup, offline compliance checking and management / manipulation of virtual disks. This talk will focus on Virtual Disk basics, VDDK API&amp;rsquo;s and the new features of 1.1 release. &lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;Audience level&lt;/b&gt;: Beginner &lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;Pre-reqs&lt;/b&gt; : Some programming experience and VMware experience desirable. Some knowledge of hard disk terms like MBR, partition, volume will be helpful.  &lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;Date:&lt;/b&gt; Wednesday, July 1, 2009 &lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;Time:&lt;/b&gt; 9:00 am, Pacific Daylight Time (GMT -07:00, San Francisco) &lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;Meeting Number&lt;/b&gt;: 929 140 533 Meeting Password: (This meeting does not require a password.) &lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;Web Ex Link: &lt;a class="jive-link-external" href="https://vmware.webex.com/vmware/j.php?ED=118609487&amp;#38;UID=0"&gt;https://vmware.webex.com/vmware/j.php?ED=118609487&amp;#38;UID=0&lt;/a&gt;&lt;/b&gt;&lt;br /&gt;
&lt;p /&gt;
More details about the webex session below.&lt;hr /&gt;
&lt;br /&gt;
To join the online meeting (Now from iPhones too!)&lt;hr /&gt;
&lt;br /&gt;
1. Go to &lt;a class="jive-link-external" href="https://vmware.webex.com/vmware/j.php?ED=118609487&amp;#38;UID=0"&gt;https://vmware.webex.com/vmware/j.php?ED=118609487&amp;#38;UID=0&lt;/a&gt; 2. Enter your name and email address. 3. Enter the meeting password: (This meeting does not require a password.) 4. Click "Join Now".&lt;hr /&gt;
&lt;br /&gt;
To join the teleconference only&lt;hr /&gt;
&lt;br /&gt;
Call-in toll-free number (US/Canada): 866-469-3239 Call-in toll number (US/Canada): 1-650-429-3300 Global call-in numbers: &lt;a class="jive-link-external" href="https://vmware.webex.com/vmware/globalcallin.php?serviceType=MC&amp;#38;ED=118609487&amp;#38;tollFree=1"&gt;https://vmware.webex.com/vmware/globalcallin.php?serviceType=MC&amp;#38;ED=118609487&amp;#38;tollFree=1&lt;/a&gt; Toll-free dialing restrictions: &lt;a class="jive-link-external" href="http://www.webex.com/pdf/tollfree_restrictions.pdf"&gt;http://www.webex.com/pdf/tollfree_restrictions.pdf&lt;/a&gt;&lt;hr /&gt;
&lt;br /&gt;
To add this meeting to your calendar program (for example Microsoft Outlook), click this link: &lt;a class="jive-link-external" href="https://vmware.webex.com/vmware/j.php?ED=118609487&amp;#38;UID=0&amp;#38;ICS=MI&amp;#38;LD=1&amp;#38;RD=2&amp;#38;ST=1&amp;#38;SHA2=cQA01NYykVYjdN16oP7vx6dxs5--vr8Wj8oqVrVw8W8="&gt;https://vmware.webex.com/vmware/j.php?ED=118609487&amp;#38;UID=0&amp;#38;ICS=MI&amp;#38;LD=1&amp;#38;RD=2&amp;#38;ST=1&amp;#38;SHA2=cQA01NYykVYjdN16oP7vx6dxs5--vr8Wj8oqVrVw8W8=&lt;/a&gt; The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to &lt;a class="jive-link-external" href="https://vmware.webex.com/vmware/systemdiagnosis.php"&gt;https://vmware.webex.com/vmware/systemdiagnosis.php&lt;/a&gt; IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, do not join the session.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">virtual</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">disk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">live_webinar_coffee_talk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">apis</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">developer</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmware</category>
      <pubDate>Mon, 01 Jun 2009 19:45:36 GMT</pubDate>
      <author>heyitspablo</author>
      <guid>http://communities.vmware.com/message/1268441</guid>
      <dc:date>2009-06-01T19:45:36Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Dynamic expansion of Virtual Disk</title>
      <link>http://communities.vmware.com/message/1299696</link>
      <description>&lt;br /&gt;
You can use VI sdk to add / modify disks - Checkout VI sdk's reconfigure function. If you need help,post in the VI sdk forum.&lt;br /&gt;
&lt;p /&gt;
 -Sudarsan</description>
      <pubDate>Wed, 01 Jul 2009 07:17:59 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1299696</guid>
      <dc:date>2009-07-01T07:17:59Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Shrink (-k) fails</title>
      <link>http://communities.vmware.com/message/1297416</link>
      <description>Nevermind, first of all I was trying to run &lt;b&gt;Vdisdmanager -k m:&lt;/b&gt; and not on the VMDK, second of all I had a mapped drive to m: and after &lt;b&gt;net use m: /delete&lt;/b&gt; I got this error:&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;
FILE: CreateEntryDirectory creation failure on 'M:\.lck': No such file or directory&lt;br /&gt;
FILE: FileIO_Lock on 'm:' failed: No such file or directory&lt;br /&gt;
Failed to open the disk 'm:' : A file was not found (0x3000900000004).&lt;br /&gt;
Failed to shrink the disk 'm:' : A file was not found (0x3000900000004).&lt;br /&gt;
&lt;/div&gt;
&lt;br /&gt;
This is on Server 2008, so the confusion lied in that I had two command prompts open to get the right privilage on the fs, one with my regular user token and the other with the admin token...</description>
      <pubDate>Mon, 29 Jun 2009 12:33:50 GMT</pubDate>
      <author>fixitchris</author>
      <guid>http://communities.vmware.com/message/1297416</guid>
      <dc:date>2009-06-29T12:33:50Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Incremental backup with Defrag</title>
      <link>http://communities.vmware.com/message/1290223</link>
      <description>Defrag inside VM will change the blocks.&lt;br /&gt;
So the blocks will be take by the backup process as new blocks.&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <pubDate>Sat, 20 Jun 2009 16:42:27 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1290223</guid>
      <dc:date>2009-06-20T16:42:27Z</dc:date>
      <clearspace:dateToText>5 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>cannot connect to host</title>
      <link>http://communities.vmware.com/message/1289050</link>
      <description>&lt;br /&gt;
Hi&lt;br /&gt;
&lt;p /&gt;
Everything set in LD_LIBRARY_PATH . Infact I can see the info of hosted disk (local disk). But wen i try to get info abt remote disk . it shows that error. Works perfectly fine in windows. :o&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks in advance.&lt;br /&gt;
&lt;p /&gt;
Surya</description>
      <pubDate>Fri, 19 Jun 2009 06:26:23 GMT</pubDate>
      <author>ayrus</author>
      <guid>http://communities.vmware.com/message/1289050</guid>
      <dc:date>2009-06-19T06:26:23Z</dc:date>
      <clearspace:dateToText>5 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>How to delete a child disk and submit the change to its parent in the parenet-disk chain with VixDiskLib?</title>
      <link>http://communities.vmware.com/message/1286140</link>
      <description>VixDiskLib does not currently have a function which does the 'combining'.&lt;br /&gt;
&lt;br /&gt;
-Sudarsan</description>
      <pubDate>Tue, 16 Jun 2009 23:03:51 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1286140</guid>
      <dc:date>2009-06-16T23:03:51Z</dc:date>
      <clearspace:dateToText>5 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>what are the requirements for san transport mode</title>
      <link>http://communities.vmware.com/message/1281028</link>
      <description>The SAN / HotAdd configuration that you have for VCB should work without change. Can you post the log thru a private message?&lt;br /&gt;
&lt;br /&gt;
Sudarsan</description>
      <pubDate>Thu, 11 Jun 2009 17:13:22 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1281028</guid>
      <dc:date>2009-06-11T17:13:22Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Using an unmodified VHD file as a VMDK file</title>
      <link>http://communities.vmware.com/message/1274760</link>
      <description>Hey Guys,&lt;br /&gt;
&lt;br /&gt;
Not sure is this would be of interest, my company (StarWind Software) just released a free utility that aids in these types of conversions.  I thought you might want to check it out &lt;a class="jive-link-external" href="http://www.starwindsoftware.com/converter"&gt;http://www.starwindsoftware.com/converter&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Hope you find it helpful!&lt;br /&gt;
&lt;br /&gt;
Bob</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmdk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vmware-mount.exe</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">esx</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vhd</category>
      <pubDate>Fri, 05 Jun 2009 21:47:41 GMT</pubDate>
      <author>bboule</author>
      <guid>http://communities.vmware.com/message/1274760</guid>
      <dc:date>2009-06-05T21:47:41Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Mounting Linux VG /w LVM on remote system</title>
      <link>http://communities.vmware.com/message/1273439</link>
      <description>As of now, there is no read-only mounting support on Linux. So you could just use the default flags (0)&lt;br /&gt;
&lt;br /&gt;
-Sudarsan</description>
      <pubDate>Fri, 05 Jun 2009 00:08:22 GMT</pubDate>
      <author>sudarsan</author>
      <guid>http://communities.vmware.com/message/1273439</guid>
      <dc:date>2009-06-05T00:08:22Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>diskLib Multi threading</title>
      <link>http://communities.vmware.com/message/1270725</link>
      <description>&lt;br /&gt;
Yes you were right, I didnt follow the 3rd guideline. its working now.&lt;br /&gt;
&lt;p /&gt;
Thanks</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">multi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">threaded</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk1.1</category>
      <pubDate>Wed, 03 Jun 2009 10:26:23 GMT</pubDate>
      <author>arent_t</author>
      <guid>http://communities.vmware.com/message/1270725</guid>
      <dc:date>2009-06-03T10:26:23Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Got problems installing VDDK 1.1 onto VMware vMA 4.0? Solution here</title>
      <link>http://communities.vmware.com/message/1265517</link>
      <description>As the topic states, if you're trying to install VDDK 1.1 you'll notice there is a shared library package that is missing by default on VMware vMA 4.0, take a look here for the solution: &lt;a class="jive-link-thread" href="http://communities.vmware.com/thread/212352"&gt;How to install VDDK 1.1 on vMA 4.0 (libfuse.so.2 fix)&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
=========================================================================&lt;br /&gt;
William Lam&lt;br /&gt;
VMware vExpert 2009&lt;br /&gt;
VMware ESX/ESXi scripts and resources at: &lt;a class="jive-link-external" href="http://engineering.ucsb.edu/~duonglt/vmware/"&gt;http://engineering.ucsb.edu/~duonglt/vmware/&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-9852"&gt;vGhetto Script Repository&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-community" href="http://communities.vmware.com/community/private/bitbucket/developer/codecentral" title="Sample code for VMware vSphere SDKs and APIs"&gt;VMware Code Central - Scripts/Sample code for Developers and Administrators&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/lamw"&gt;http://twitter.com/lamw&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;img src="http://engineering.ucsb.edu/~duonglt/vmware/vexpert_silver_icon.jpg" alt="http://engineering.ucsb.edu/~duonglt/vmware/vexpert_silver_icon.jpg" class="jive-image"  /&gt;&lt;br /&gt;
&lt;br /&gt;
If you find this information useful, please award points for "correct" or "helpful".</description>
      <category domain="http://communities.vmware.com/tags?communityID=2655">libfuse.so.2</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vma4.0</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vma4</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk1.1</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vddk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2655">vima</category>
      <pubDate>Thu, 28 May 2009 19:10:03 GMT</pubDate>
      <author>lamw</author>
      <guid>http://communities.vmware.com/message/1265517</guid>
      <dc:date>2009-05-28T19:10:03Z</dc:date>
      <clearspace:dateToText>5 months, 4 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Limitations opening vmdk files of running guests</title>
      <link>http://communities.vmware.com/message/1264722</link>
      <description>&lt;br /&gt;
Very clear. I understood.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Many thanks again !</description>
      <pubDate>Thu, 28 May 2009 07:11:56 GMT</pubDate>
      <author>flatino</author>
      <guid>http://communities.vmware.com/message/1264722</guid>
      <dc:date>2009-05-28T07:11:56Z</dc:date>
      <clearspace:dateToText>5 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Cannot mount vmdk file</title>
      <link>http://communities.vmware.com/message/1264614</link>
      <description>Yes, the VMDK file is unmounted properly.</description>
      <pubDate>Thu, 28 May 2009 04:02:44 GMT</pubDate>
      <author>writetonikhil</author>
      <guid>http://communities.vmware.com/message/1264614</guid>
      <dc:date>2009-05-28T04:02:44Z</dc:date>
      <clearspace:dateToText>5 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>How can I mount a snapshot of a vm online to work in parallel with the same vm at the same time?</title>
      <link>http://communities.vmware.com/message/1263442</link>
      <description>&lt;br /&gt;
Hi Selaf.&lt;br /&gt;
&lt;p /&gt;
You cannot run two instances of the same vm parallel. &lt;br /&gt;
&lt;p /&gt;
You will have to clone the vm, revert to SNAP2 and start the cloned one, so you have two independet vms.  &lt;br /&gt;
&lt;p /&gt;
If you are done, you can delete the whole cloned vm.  &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
BTW: you are talking about mounting, but do not want to mount anything &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/wink.gif" alt=";)" /&gt;. You mount something  to access its file system.  &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Ciao Ciao &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Wed, 27 May 2009 09:44:27 GMT</pubDate>
      <author>killermachine188</author>
      <guid>http://communities.vmware.com/message/1263442</guid>
      <dc:date>2009-05-27T09:44:27Z</dc:date>
      <clearspace:dateToText>6 months, 18 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>HotAdd transfer mode using VDDK APis fails</title>
      <link>http://communities.vmware.com/message/1260450</link>
      <description>Hi,&lt;br /&gt;
I'm using VDDK's  Flexible transfer mode APIs VDIskLib_InitEx and VixDIskLIb_ConnectEx etc.  for HotAdd  transfer mode inside VM. But If I see logs, it fails and fall backs to nbd transfer mode.&lt;br /&gt;
I'm not sure what is issue here.&lt;br /&gt;
Is there any special configuration required for HotAdd transfer mode  inside VM ?&lt;br /&gt;
&lt;br /&gt;
Thanks in advance&lt;br /&gt;
dhd9</description>
      <pubDate>Sat, 23 May 2009 05:50:48 GMT</pubDate>
      <author>dhd9</author>
      <guid>http://communities.vmware.com/message/1260450</guid>
      <dc:date>2009-05-23T05:50:48Z</dc:date>
      <clearspace:dateToText>6 months, 4 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>troubles with vmware-mount "file not found" ??</title>
      <link>http://communities.vmware.com/message/1260048</link>
      <description>&lt;br /&gt;
Ugh, posted the wrong part of the fuseMount log in the last reply. Here it is:&lt;br /&gt;
&lt;p /&gt;
May 22 13:50:57.741: VMware VixDiskLib (1.1) Release build-163495&lt;br /&gt;
May 22 13:50:57.741: Using system libcrypto, version 90807F&lt;br /&gt;
May 22 13:50:57.743: &amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt; Starting FuseMount Process &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=PID%3A+21557"&gt;PID: 21557&lt;/a&gt; &amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;br /&gt;
May 22 13:50:57.743: --- Mounting Virtual Disk: &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=davenfs"&gt;davenfs&lt;/a&gt; cas2.ds.udel.edu/cas2.ds.udel.edu.vmdk ---&lt;br /&gt;
May 22 13:50:57.744: Disk flat file mounted under /var/run/vmware/fuse/15881202677672233625&lt;br /&gt;
May 22 13:50:57.748: LIBFUSE   :Opening disk - vmSpec -vmPath=ha-datacenter/vm/cas2.ds.udel.edu-, server -nd2cluster1.nss.udel.edu-, disk -&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=davenfs"&gt;davenfs&lt;/a&gt; cas2.ds.udel.edu/cas2.ds.udel.edu.vmdk-&lt;br /&gt;
May 22 13:50:57.749: TicketResolveHostName: Resolving IP address for hostname nd2cluster1.nss.udel.edu.&lt;br /&gt;
May 22 13:50:57.752: TicketResolveHostName: Resolved to 128.175.28.80.&lt;br /&gt;
May 22 13:50:57.754: VixDiskLibVim: TicketLogin&lt;br /&gt;
May 22 13:50:58.005: VixDiskLibVim: TicketFindVMByInvPath: vmxPath = -ha-datacenter/vm/cas2.ds.udel.edu-&lt;br /&gt;
May 22 13:50:58.044: VixDiskLibVim: TicketLoadVM&lt;br /&gt;
VixDiskLibVim: Unable to find key for disk &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=davenfs"&gt;davenfs&lt;/a&gt; cas2.ds.udel.edu/cas2.ds.udel.edu.vmdk&lt;br /&gt;
May 22 13:50:58.109: VixDiskLibVim: TicketLoadVMCb&lt;br /&gt;
VixDiskLibVim: TicketLoadVMCb failure - VixError = 4.&lt;br /&gt;
May 22 13:50:58.111: VixDiskLibVim: TicketLogout&lt;br /&gt;
May 22 13:50:58.154: LIBFUSE   : Failed to open disk: A file was not found (4)&lt;br /&gt;
May 22 13:50:58.154: Fuse initialization failed.&lt;br /&gt;
Failed to mount disk '&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=davenfs"&gt;davenfs&lt;/a&gt; cas2.ds.udel.edu/cas2.ds.udel.edu.vmdk': Cannot open the virtual disk</description>
      <pubDate>Fri, 22 May 2009 17:57:51 GMT</pubDate>
      <author>soonblue</author>
      <guid>http://communities.vmware.com/message/1260048</guid>
      <dc:date>2009-05-22T17:57:51Z</dc:date>
      <clearspace:dateToText>6 months, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Enable mutipath option for Raw Device Mapping in Virtual machine</title>
      <link>http://communities.vmware.com/message/1249141</link>
      <description>&lt;br /&gt;
I posted in appropriate forum.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
Karthi</description>
      <pubDate>Tue, 12 May 2009 04:40:16 GMT</pubDate>
      <author>karthimin</author>
      <guid>http://communities.vmware.com/message/1249141</guid>
      <dc:date>2009-05-12T04:40:16Z</dc:date>
      <clearspace:dateToText>6 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>[NFC ERROR] Network error</title>
      <link>http://communities.vmware.com/message/1248737</link>
      <description>Your logs on the eSX server should provide you more info on this client side error.</description>
      <pubDate>Mon, 11 May 2009 17:46:56 GMT</pubDate>
      <author>fixitchris</author>
      <guid>http://communities.vmware.com/message/1248737</guid>
      <dc:date>2009-05-11T17:46:56Z</dc:date>
      <clearspace:dateToText>6 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Child vdmk files can be opened only with ESX credentials ?</title>
      <link>http://communities.vmware.com/message/1243792</link>
      <description>&lt;br /&gt;
Hi Sudarsan,&lt;br /&gt;
&lt;p /&gt;
I must copy the VMDK files from the ESX server on another machine since I am not able to compile your sample code on the ESX server: a lot of libraries needs to be upgraded.&lt;br /&gt;
&lt;p /&gt;
So I am running your example on another Linux machine (where I setup the VDDK environment to compile your sample) and so I need to copy the VMDK files from the ESX locally to the Linux machine.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
You are right: a VMDK image snapshot created with VMWare workstation can be opened while an ESX one fails.&lt;br /&gt;
&lt;p /&gt;
I performed this test:&lt;br /&gt;
&lt;p /&gt;
Machine A = ESX server / Workstation &lt;br /&gt;
&lt;p /&gt;
Machine B = Linux machine runnign vix sample code&lt;br /&gt;
&lt;p /&gt;
1- On machine A create a snaphost ( file-000001.vmdk is created togheter with other files...)&lt;br /&gt;
&lt;p /&gt;
2- copy all the VMWare machine folder from MAchine A to Machine B (the Linux machine running your sample code)&lt;br /&gt;
&lt;p /&gt;
3- From Machine B run "vixDiskLibSample.exe -info &amp;lt;path_to_snapshot&amp;gt;"&lt;br /&gt;
&lt;p /&gt;
These steps work for a CHILD VMDK created by VMWare Workstation but they fails if the CHILD is created with ESX server...is this normal ?&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Tue, 05 May 2009 17:51:44 GMT</pubDate>
      <author>flatino</author>
      <guid>http://communities.vmware.com/message/1243792</guid>
      <dc:date>2009-05-05T17:51:44Z</dc:date>
      <clearspace:dateToText>6 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
  </channel>
</rss>

