Are there any examples that use VixDiskLibSessionIdCreds based authentication ?

What is the key field supposed to represent ?

It seems weird that given the great documentation for the vSphere APIs that VDDK seems to be treated like a red-headed step child. The documentation and examples are very poor.

r.

(using 5.1.1)

Hello Guys,

I am using VDDK 5.5.4 version, creating vmdk file for managed disk type.

About Managed disk:-
VixDiskLib_Create() locally creates a new virtual disk, after being 
connected to the host(). In createParams, you must specify the disk type, 
adapter, hardware version, and capacity as a number of sectors. 
This function supports hosted disk.
For managed disk, first create a hosted type virtual disk, then use 
VixDiskLib_Clone() to convert the virtual disk to managed disk.

Currently existing VMware API - VixDiskLib_Create is failing in virtual disk 
creation with disk type VIXDISKLIB_DISK_MONOLITHIC_SPARSE  when user 
requests for size =>2TB

I am exploring over virtual disk creation to managed disk with below virtual 
disk type supported by VMWare VDDK. 

I have tried to create virtual disk with type for >2TB.
Prerequisites:-
Have backup of a machine having NTFS drive with size 2.2TB.
Machine with NTFS drive with size 2.5TB for temporary destination to for vmdk.
ESXi 6.0 with data store formatted with VMFS5 and has 4TB free space.

VMware API - VixDiskLib_Create with virtual disk type.
1.) VIXDISKLIB_DISK_MONOLITHIC_SPARSE fails to create vmdk with size -2.2TB.
2.) VIXDISKLIB_DISK_MONOLITHIC_FLAT able to create vmdk but pre allocates complete 2.2TB size irrespective of actual data and took more than 8hours.
3.) VIXDISKLIB_DISK_VMFS_THIN fails to create vmdk file.
4.) VIXDISKLIB_DISK_VMFS_FLAT able to create vmdk but pre allocates complete 2.2TB size irrespective of actual data and took more than 8hours.
Note:- In case of managed disk creation, even though we create vmdk any type but while cloning to ESXi host it will be VIXDISKLIB_DISK_VMFS_FLAT.

I am not sure why VixDiskLib_Create is failing for VIXDISKLIB_DISK_MONOLITHIC_SPARSE when size >=2TB? 

Please help in resolving this issue.

Thanks,
Basavaraj.

To start, if there's a better way to accomplish this, I would welcome that info.

I am running ESXi 6.0.0, 3620759 and have VDDK 6.0.2-3566099 x86_64.

I want to mount a virtual hard drive of a VM on my ESXi server to a mount point I prescribe locally on the ESXi server - not remotely. I typically connect to the ESXi server using the SSH service and wish to perform this action locally on the ESX sever.

e.g. mount <path to.vmdk> /mnt/mymountpoint

As I cannot find the vmware-mount utility anymore for Linux (i.e. the ESXi environment) I am examining the VDDK to accompish this.

I am compiling straight C with:

# gcc -Wall -Wl, -R$(SODIR) -o vixMntApi -I$(INCLUDEDIR) -L$(LIBDIR) vixMntApi.c -ldl -lvixDiskLib -pthread

I have the VDDK libs installed in $(SODIR) on the ESXi server on a volume mounted at /vmfs/volumes/diskstore1/VDDK/lib64

I have placed a vddk.conf file in a tmp folder at /vmfs/volumes/diskstore1/VDDK/tmp.

However, when using the vixDiskLib_InitEx() api I get the following runtime error:

GThread-ERROR **: file gthread-posix.c: line 140 (g_thread_impl_init): error 'Operation not permitted' during 'pthread_getschedparam (pthread_self(), &policy, &sched)'

aborting...

Aborted

Question #1: what am I doing wrong here?

Question #2: does it matter what values I am providing the VixDiskLib_Init() function for MAJOR and MINOR versions? I've tried 5,5 and 6,0 but neither seem to make a difference.

Question #3: is there a tool available to mount and unmount virtual hard disks on the ESX server itself? I only need RO access at a mount point I can prescribe and I need to be able to read NTFS partitions (usually only one per VM).

Thanks in advance!

when i run the vddk sample ,

./vix-disklib-sample -info -host 192.168.2.xx -user root -password xx "/datastore1 (1)/redhat-6.5oracle11g-192.168.17.21.vmdk"

console show

VixDiskLibVim:Login failure - VixError = 0.

Error:[vixDiskLibSample.cpp:612] 4650 Cannot connect to the host

someone can help me?

thank you very much

 ./vix-disklib-sample -info -host 192.168.2.53 -user root -password xxx -initex config -mode san -libdir "/usr/lib/vmware-vix-disklib" -thumb "2E:41:B8:CB:81:07:69:87:30:B1:DB:D4:9D:98:4C:D3:DD:41:52:4A" "[datastore1 (1)] redhat-6.5oracle11g-192.168.17.21/redhat-6.5oracle11g-192.168.17.21.vmdk"
Log: VixDiskLib: linuxVerifySSLCertificates is 1
Log: VixDiskLib: config options: libdir '/usr/lib/vmware-vix-disklib', tmpDir '/tmp/vmware-root'.
Log: OBJLIB-LIB : Objlib initialized.
Log: VixDiskLib: Attempting to locate advanced transport module in "/usr/lib/vmware-vix-disklib".
Log: VixDiskLib: Advanced transport plugin was successfully loaded into vixDiskLib.
Log: VixDiskLib: Enabling advanced transport modes.
Log: OBJLIB-LIB : Objlib initialized.
Log: VixDiskLib: Transport modes available: file:nbdssl:nbd:san.
Log: VMware VixDiskLib (5.1) Release build-774844
Log: VixDiskLib:  VixDiskLibResolveHostName: resolving 192.168.2.53
Log: VixDiskLib:  VixDiskLibResolveHostName: returned 192.168.2.53
Log: VixDiskLib: Added thumbprint 2E:41:B8:CB:81:07:69:87:30:B1:DB:D4:9D:98:4C:D3:DD:41:52:4A to sslIdDb for 192.168.2.53
Log: VixDiskLibVimResolveHostName: Resolving IP address for hostname 192.168.2.53.
Log: VixDiskLibVimResolveHostName: Resolved to 192.168.2.53.
Log: VixDiskLibVim: VixDiskLibVimLogin
Log: VixDiskLibVim: VixDiskLibVimLogout
Segmentation fault (core dumped)

someone can help me,thanks

I scanned VirtualDiskAPIprogramming,but I am not find how to use clone such as  ./vix-disklib-sample -clone -option,someone can help me?

thanks

Unable to get any version of VDDK to connect to ESXi 6.5.

Following are the outputs from VDDK 5.5.4 and 6.0.2.

Tried VDDK installed on Windows 7 and Windows 10.

Similar command works fine with ESXi 5.5 & 6.0.

Any help would be appreciated.

VDDK 5.5.4:

vixDiskLibSample.exe -info -host 192.168.241.130 -user root -password x
xxxxxxx -thumb 0B:1E:C4:21:14:EA:2F:CF:B0:C6:2E:3A:40:4E:97:77:A4:BE:C0:BB -init
ex null "[datastore1] vlab8vm01/vlab8vm01.vmdk"
Warning: VixDiskLib: Unable to load configuration options from null.
Log: OBJLIB-LIB: Objlib initialized.
Log: VixDiskLib: Advanced transport module not loaded.
Log: VixDiskLib: Using transport modes from DiskLib: file:nbdssl:nbd.
Log: VMware VixDiskLib (5.5) Release build-2454786
Log: PREF early PreferenceGet(poll.forceSelect), using default
Log: POLL Using the WSAPoll API Implementation for PollDefault
Log: VixDiskLibVim: VixDiskLibVim_Init: Initialization is completed.
Log: VixDiskLib: VixDiskLib_Connect: Establish connection.
Log: HOSTINFO 462703657053 @ 2435927Hz -> 0 @ 1000000000Hz
Log: HOSTINFO ((x * 3443702541) >> 23) + -189949722233224
Log: VixDiskLib: VixDiskLib_OpenEx: Open a disk.
Log: VixDiskLibVim: VixDiskLibVim_GetNfcTicket: Get NFC ticket for [datastore1]
vlab8vm01/vlab8vm01.vmdk.
Log: HOSTINFO 462703709602 @ 2435927Hz -> 0 @ 1000000000Hz
Log: HOSTINFO ((x * 3443702541) >> 23) + -189949743805710
Log: VThreadBase detected multiple threads.
Log: VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.
Log: NBD_ClientOpen: attempting to create connection to ha-nfc://[datastore1] vl
ab8vm01/vlab8vm01.vmdk@192.168.241.130:902
Log: Started up WSA
Log: SSL: EOF in violation of protocol
Warning: SSL: connect failed
Log: CnxAuthdConnect: Returning false because SSL_ConnectAndVerify failed
Log: CnxConnectAuthd: Returning false because CnxAuthdConnect failed
Log: Cnx_Connect: Returning false because CnxConnectAuthd failed
Log: Cnx_Connect: Error message:
Warning: [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error:

Log: NBD_ClientOpen: Couldn't connect to 192.168.241.130:902
Log: DISKLIB-DSCPTR: : "ha-nfc://[datastore1] vlab8vm01/vlab8vm01.vmdk@192.168.2
41.130:902" : Failed to open NBD extent.
Log: DISKLIB-LINK  : "ha-nfc://[datastore1] vlab8vm01/vlab8vm01.vmdk@192.168.241
.130:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
Log: DISKLIB-CHAIN : "ha-nfc://[datastore1] vlab8vm01/vlab8vm01.vmdk@192.168.241
.130:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
Log: DISKLIB-LIB   : Failed to open 'ha-nfc://[datastore1] vlab8vm01/vlab8vm01.v
mdk@192.168.241.130:902' with flags 0x1e NBD_ERR_NETWORK_CONNECT (2338).
Log: VixDiskLib: Detected DiskLib error 2338 (NBD_ERR_NETWORK_CONNECT).
Error: [vixDiskLibSample.cpp:609]  922000036b9 NBD_ERR_NETWORK_CONNECT
Log: VixDiskLib: VixDiskLib_Disconnect: Disconnect.
Log: VixDiskLib: VixDiskLib_Exit: Unmatched Init calls so far: 1.
Log: VixDiskLibVim: VixDiskLibVim_Exit: Clean up.

VDDK 6.0.2:

vixDiskLibSample.exe -info -host 192.168.241.130 -user root -password x
xxxxxxx -thumb xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx -init
ex null "[datastore1] vlab8vm01/vlab8vm01.vmdk"
Warning: VixDiskLib: Unable to load configuration options from null.
Log: OBJLIB-LIB: Objlib initialized.
Log: VixDiskLib: Advanced transport module not loaded.
Log: VixDiskLib: Using transport modes from DiskLib: file:nbdssl:nbd.
Log: VMware VixDiskLib (6.0) Release build-2942432
Log: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Program
Data\VMware): Cannot create a file when that file already exists (183)
Log: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Program
Data\VMware): Cannot create a file when that file already exists (183)
Log: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Program
Data\VMware): Cannot create a file when that file already exists (183)
Log: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Program
Data\VMware): Cannot create a file when that file already exists (183)
Log: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Program
Data\VMware): Cannot create a file when that file already exists (183)
Log: PREF early PreferenceGet(poll.forceSelect), using default
Log: POLL Using the WSAPoll API Implementation for PollDefault
Log: VixDiskLibVim: VixDiskLibVim_Init: Initialization is completed.
Log: VixDiskLib: VixDiskLib_Connect: Establish connection.
Log: VixDiskLib: Resolve host.
Log: VixDiskLib: VixDiskLib_OpenEx: Open a disk.
Log: VixDiskLibVim: VixDiskLibVim_GetNfcTicket: Get NFC ticket for [datastore1]
vlab8vm01/vlab8vm01.vmdk.
Log: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Program
Data\VMware): Cannot create a file when that file already exists (183)
Log: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Program
Data\VMware): Cannot create a file when that file already exists (183)
Log: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Program
Data\VMware): Cannot create a file when that file already exists (183)
Log: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Program
Data\VMware): Cannot create a file when that file already exists (183)
Log: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\Program
Data\VMware): Cannot create a file when that file already exists (183)
Log: VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.
Log: NBD_ClientOpen: attempting to create connection to ha-nfc://[datastore1] vl
ab8vm01/vlab8vm01.vmdk@192.168.241.130:902
Log: Started up WSA
Log: CnxConnectAuthd: Returning false because CnxAuthdProtoConnect failed
Log: Cnx_Connect: Returning false because CnxConnectAuthd failed
Log: Cnx_Connect: Error message: 550 User not authorized for host agent contact
Warning: [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error:
550 User not authorized for host agent contact
Log: NBD_ClientOpen: Couldn't connect to 192.168.241.130:902 550 User not author
ized for host agent contact
Log: DISKLIB-DSCPTR: : "ha-nfc://[datastore1] vlab8vm01/vlab8vm01.vmdk@192.168.2
41.130:902" : Failed to open NBD extent.
Log: DISKLIB-LINK  : "ha-nfc://[datastore1] vlab8vm01/vlab8vm01.vmdk@192.168.241
.130:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
Log: DISKLIB-CHAIN : "ha-nfc://[datastore1] vlab8vm01/vlab8vm01.vmdk@192.168.241
.130:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
Log: DISKLIB-LIB   : Failed to open 'ha-nfc://[datastore1] vlab8vm01/vlab8vm01.v
mdk@192.168.241.130:902' with flags 0x1e NBD_ERR_NETWORK_CONNECT (2338).
Log: VixDiskLib: Detected DiskLib error 2338 (NBD_ERR_NETWORK_CONNECT).
Log: VixDiskLib: Failed to open disk ha-nfc://[datastore1] vlab8vm01/vlab8vm01.v
mdk@192.168.241.130:902?root/xxxxxxx. Error 14009 (The server refused connectio
n) (DiskLib error 2338: NBD_ERR_NETWORK_CONNECT) at 4464.
Log: VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [datastore1] vlab8vm01/vlab
8vm01.vmdk. Error 14009 (The server refused connection) (DiskLib error 2338: NBD
_ERR_NETWORK_CONNECT) at 4680.
Log: VixDiskLib: VixDiskLib_Open: Cannot open disk [datastore1] vlab8vm01/vlab8v
m01.vmdk. Error 14009 (The server refused connection) at 4718.
Error: [vixDiskLibSample.cpp:644]  36b9 The server refused connection
Log: VixDiskLib: VixDiskLib_Disconnect: Disconnect.
Log: VixDiskLib: VixDiskLib_Exit: Unmatched Init calls so far: 1.
Log: VixDiskLibVim: VixDiskLibVim_Exit: Clean up.

Trying to compile vixDiskLibSample in VDDK 6.5 and getting errors.

I have not had this problem with other (previous) versions of VDDK (notably 5.5.4, 5.5.5, 6.0.0, 6.0.1 and 6.0.2).

Using Microsoft Visual Studio 2015.

Downloaded and extracted VMware-vix-disklib-6.5.0-4604867.x86_64.

Opened and upgraded ...\VMware-vix-disklib-6.5.0-4604867.x86_64\doc\sample\vixDiskLibSample.sln.

Opened Configuration Manager for VS project and set Platform to x64.

Downloaded and extracted boost_1_62_0.zip (source: http://www.boost.org/users/history/version_1_62_0.html) to ...\VMware-vix-disklib-6.5.0-4604867.x86_64\doc\sample\boost.

Set VS project to include ...\VMware-vix-disklib-6.5.0-4604867.x86_64\doc\sample\boost\*.*.

Getting the following errors on build:

Could this be because I am using the wrong version of Boost? Or, could the VMware developers who tested vixDiskLibSample in VDDK 6.5 have made custom edits to the Boost headers in their development environment?

Any help is much appreciated.

I see there was another post also returning 18000 but it didn't seem to resolve my problem. I cannot seem to get the VDDK to open a disk when using the latest version 6.5. Can anyone help?

2016-12-05T16:34:59.654+08:00| vthread-4| I125: 2016-12-05T16:34:59.654+08:00 PREF Optional preferences file not found at C:\Users\heaven\AppData\Roaming\VMware\config.ini. Using default values.
2016-12-05T16:34:59.654+08:00| vthread-4| I125: 2016-12-05T16:34:59.654+08:00 UUID: SMBIOS UUID is reported as '00 28 2d f6 5e a9 e1 81-2b 4b 10 bf 48 26 b7 82'.
2016-12-05T16:34:59.654+08:00| vthread-4| I125: 2016-12-05T16:34:59.654+08:00 FILE: FileLockDynaLink: Further process validation tools are: available
2016-12-05T16:34:59.657+08:00| vthread-4| I125: 2016-12-05T16:34:59.657+08:00 lib/ssl: OpenSSL using FIPS_drbg for RAND
2016-12-05T16:34:59.657+08:00| vthread-4| I125: 2016-12-05T16:34:59.657+08:00 lib/ssl: protocol list tls1.2
2016-12-05T16:34:59.657+08:00| vthread-4| I125: 2016-12-05T16:34:59.657+08:00 lib/ssl: protocol list tls1.2 (openssl flags 0x17000000)
2016-12-05T16:34:59.657+08:00| vthread-4| I125: 2016-12-05T16:34:59.657+08:00 lib/ssl: cipher list !aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES
2016-12-05T16:34:59.657+08:00| vthread-4| I125: 2016-12-05T16:34:59.657+08:00 FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2016-12-05T16:34:59.657+08:00| vthread-4| I125: 2016-12-05T16:34:59.657+08:00 FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2016-12-05T16:34:59.657+08:00| vthread-4| I125: 2016-12-05T16:34:59.657+08:00 FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2016-12-05T16:34:59.657+08:00| vthread-4| I125: 2016-12-05T16:34:59.657+08:00 FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2016-12-05T16:34:59.657+08:00| vthread-4| I125: 2016-12-05T16:34:59.657+08:00 FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2016-12-05T16:34:59.658+08:00| vthread-4| W115: 2016-12-05T16:34:59.658+08:00 Ignoring windows message posted to non-UI thread. hwnd 463178 msg 15 wp 00000000 lp 00000000
2016-12-05T16:34:59.718+08:00| vthread-4| W115: 2016-12-05T16:34:59.718+08:00 Ignoring windows message posted to non-UI thread. hwnd 463178 msg 675 wp 00000000 lp 00000000
2016-12-05T16:34:59.719+08:00| vthread-4| E110: 2016-12-05T16:34:59.719+08:00 VixDiskLibVim: Error 18000 (listener error GVmomiFaultInvalidResponse).
2016-12-05T16:34:59.719+08:00| vthread-4| W115: 2016-12-05T16:34:59.719+08:00 VixDiskLibVim: Login failure. Callback error 18000 at 2444.
2016-12-05T16:34:59.719+08:00| vthread-4| E110: 2016-12-05T16:34:59.719+08:00 VixDiskLibVim: Failed to find the VM. Error 18000 at 2516.
2016-12-05T16:34:59.720+08:00| vthread-4| I125: 2016-12-05T16:34:59.720+08:00 VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.
2016-12-05T16:34:59.720+08:00| vthread-4| E110: VixDiskLib: Error occurred when obtaining NFC ticket for [datastore1] Windows7X64/Windows7X64_0.vmdk. Error 18000 (Cannot connect to the host) (fault (null), type GVmomiFaultInvalidResponse, reason: (none given), translated to 18000) at 2173.
2016-12-05T16:34:59.720+08:00| vthread-4| E110: VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [datastore1] Windows7X64/Windows7X64_0.vmdk. Error 18000 (Cannot connect to the host) at 4964.
2016-12-05T16:34:59.720+08:00| vthread-4| E110: VixDiskLib: VixDiskLib_Open: Cannot open disk [datastore1] Windows7X64/Windows7X64_0.vmdk. Error 18000 (Cannot connect to the host) at 5002.
2016-12-05T16:40:05.381+08:00| vthread-4| I125: VixDiskLib: VixDiskLib_Disconnect: Disconnect.
2016-12-05T16:40:05.381+08:00| vthread-4| I125: VixDiskLib: VixDiskLib_Exit: Unmatched Init calls so far: 1.
2016-12-05T16:40:05.381+08:00| vthread-4| I125: 2016-12-05T16:40:05.381+08:00 VixDiskLibVim: VixDiskLibVim_Exit: Clean up.

We use vSphere 6.0 , VDDK 6.0.2 and IBM TSM Client 7.1 using Hotadd mode.
After backup with VDDK , it had became necessary to consolidate VM and remained target VM disks on proxy.
I guess that bellow problem described in the release note 6.0.2 has not been resolved yet. Pls help.

https://www.vmware.com/support/developer/vddk/vddk-602-releasenotes.html
 >  Backup or restore using HotAdd transport leaves behind target VM disks on proxy.

Hi, my software had implementation for VDDK 6.0.2 and all worked fine. I now test the following versions of ESXi: 4.1 - 5.0 - 5.5(U2) - 6.0 - 6.5

I upgraded VDDK to 6.5.0 and 4.1 and 5.0 stopped working. The others are working fine.

I get the VIX_E_HOST_NETWORK_CONN_REFUSED error calling the VixDiskLib_Open function.

So, i found inside the VDDK 6.5 release note ( http://pubs.vmware.com/Release_Notes/en/developer/vddk/65/vsphere-vddk-65-release-notes.html ) this:

If a vSphere 6.5 customer sets TLS v1.2 authentication as mandatory, backups fail on ESXi 5.5U3 and earlier hosts, with “SSL Exception” errors. The fix is to upgrade those ESXi hosts to 5.5U3e or later

I was confused by the fact that my 5.5U2 still works, but until its working i'm fine with that. Release notes gives a workaround:

Add the following line to the appropriate file:
tls.protocols=tls1.0,tls1.1,tls1.2

Ok then, i added that line on my configuration file and i can go through the VixDiskLib_Open function. After the Open i call VixDiskLib_GetInfo successfully and get the correct result.

-BUT-

when i call the VixDiskLib_Read function i get a generic VIX_E_FAIL error. I checked my ESXi log and found that after calling the Read those line are always added:

[NFC ERROR] Sending Nfc error 2: Illegal message during fssrvr session, id = 46

[NFC ERROR] Failure on msg 46: NFC_INVALID_REQUEST

Read error from the nfcLib: NFC_INVALID_REQUEST (done=yep)

Even after this edit its still working with 5.5, 6.0 and 6.5.

How can i fix this? Thank you!

Hello!

I have follow error when try to connect to ESXi 6/6.5 with 'nbdssl' mode:

Originator@6876 sub=Default] Cannot use advanced transport modes for 10.10.66.147/moref=2/2-snapshot-25: Other error encountered: Object not found: Vmomi::VersionMapImpl::GetOrCreateVersion: versionName = ¸\x16„¶û\x7f.

VixDiskLib: VixDiskLib_ConnectEx: Advanced transport modes not available for opening moref=2. (Cannot use advanced transport modes for 10.10.66.147/moref=2/2-snapshot-25: Other error encountered: Object not found: Vmomi::VersionMapImpl::GetOrCreateVersion: versionName = ¸ „¶û.)

As the result connection open in 'nbd' mode.

I use vddk 6.5, in version 6.0.0 is not happening. 

I'm using VDDK 6.0 build 3566099 to mount a 2TB  Win 7 x64 guest on the U: drive of my test system (also a Win 7 x64 system).

In total I have 20 guests ranging from Win Vista x86-Win Svr 2016 x64 - all of which can successfully mount except for this one guest which is by far the largest.

I am using nbd transport to mount the image with open flags VIXDISKLIB_FLAG_OPEN_READ_ONLY.

I am able to execute VixDiskLib_GetInfo() on the image successfully, just unable to mount it. From logging it does appear to be failing at the creation of the local child disk .vmdk. VixDisk_Lib_CreateChild says one of the parameters is incorrect.

I've seen other postings regarding certain limits with VMWARE and the 2TB ceiling but not specifically with VDDK.

Is there possibly a workaround for this? I don't want to create a disk, nor write to it - just mount RO.

Here is the output of my mount app:

childDiskName: C:\7-childDisk-1.vmdk
Calling VixMntapi_Init()...
INFO: `anonymous-namespace'::VixMntapiReadTmpDirPath: Using tempDirectory C:\VDDK\tmp.
INFO: Mntapi_Init Asked - 2.2 Served - 2.2 was successful,TempDirectory: C:\VDDK\tmp.Calling VixDiskLib_Connect()...
INFO: VixDiskLib: VixDiskLib_Connect: Establish connection.
INFO: VixDiskLib: VixDiskLib_OpenEx: Open a disk.
INFO: VixDiskLibVim: VixDiskLibVim_GetNfcTicket: Get NFC ticket for [datastore2] Win 7 x64_1/Win 7 x64_1.vmdk.
INFO: VixDiskLibVim: Request RandomAccessRO diskKey = 2000, readOnly = 1, openSnapshot = 0.
INFO: VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.
INFO: NBD_ClientOpen: attempting to create connection to ha-nfc://[datastore2] Win 7 x64_1/Win 7 x64_1.vmdk@192.168.4.201:902
INFO: Started up WSA
INFO: Opening file [datastore2] Win 7 x64_1/Win 7 x64_1.vmdk (ha-nfc://[datastore2] Win 7 x64_1/Win 7 x64_1.vmdk@192.168.4.201:902)
INFO: DISKLIB-LINK  : Opened 'ha-nfc://[datastore2] Win 7 x64_1/Win 7 x64_1.vmdk@192.168.4.201:902' (0x1e): custom, 4294967296 sectors / 2 TB.
INFO: DISKLIB-LIB   : Opened "ha-nfc://[datastore2] Win 7 x64_1/Win 7 x64_1.vmdk@192.168.4.201:902" (flags 0x1e, type custom).
INFO: VixDiskLib: VixDiskLib_GetTransportMode: Retrieve transport mode.
Selected transport method: nbd
childDisks[0].c_str() C:\7-childDisk-1.vmdk
INFO: VixDiskLib: VixDiskLib_CreateChild: Create a child disk.
INFO: DISKLIB-LIB_CREATE   : CREATE CHILD: "C:\7-childDisk-1.vmdk" -- monolithicSparse grainSize=128 policy=''
INFO: DISKLIB-LIB_CREATE   : CREATE-CHILD: Creating disk backed by 'default'
INFO: DISKLIB-LIB_CREATE   : Failed to create link: One of the parameters supplied is invalid (1)
INFO: DISKLIB-LIB_CREATE   : DiskLib_CreateChild: failed to create child disk: One of the parameters supplied is invalid (1).
INFO: VixDiskLib: Detected DiskLib error 1 (One of the parameters supplied is invalid).
INFO: VixDiskLib: VixDiskLib_CreateChild: Unable to create child disk. Error 16000 (One of the parameters supplied is invalid) (DiskLib error 1: One of the parameters supplied is invalid) at 4408.
VixDiskLib_CreateChild() returned: 16000 (Disk Invalid): childDisks[0].c_str(): C:\7-childDisk-1.vmdk

I use https://code.vmware.com/samples/1116/sample-to-demonstrate-mounting-of-target-vms-vmdk-on-physical-or-virtual-proxy-using-vddk-sdk.#code and compile it on linux system, but the program quit with error under, is there any suggestions on this problem?

2017-02-15T17:37:23.323+08:00| vthread-4| I130: VixDiskLib: Close sslIdDb.

2017-02-15T17:37:23.323+08:00| vthread-4| I130: VixDiskLib: Release sslIdDb.

2017-02-15T17:37:23.323+08:00| vthread-4| I120: VixDiskLib: VixDiskLib_ConnectEx: No transport plugin. Advanced transports not available.

2017-02-15T17:37:24.440+08:00| vthread-4| I120: VixDiskLib: VixDiskLib_Connect: Establish connection.

2017-02-15T17:37:24.440+08:00| vthread-4| I130: VixDiskLib: VixDiskLib_Connect: Use local connection.

2017-02-15T17:37:24.440+08:00| vthread-4| I125: VixDiskLib: Allocate connection.

2017-02-15T17:37:24.440+08:00| vthread-4| I120: VixDiskLib: VixDiskLib_OpenEx: Open a disk.

2017-02-15T17:37:24.440+08:00| vthread-4| I125: VixDiskLib: Open a disk with standard transport mode.

2017-02-15T17:37:24.440+08:00| vthread-4| I125: VixDiskLib: Construct full path to disk.

2017-02-15T17:37:24.440+08:00| vthread-4| I130: VixDiskLib: Get NFC ticket for: [vsanDatastore] dfc9a258-203e-8b0d-96c9-e03f49b5ce6a/buyaoshan-win-000001.vmdk.

2017-02-15T17:37:25.063+08:00| vthread-4| E105: VixDiskLib: Error occurred when obtaining NFC ticket for [vsanDatastore] dfc9a258-203e-8b0d-96c9-e03f49b5ce6a/buyaoshan-win-000001.vmdk. Error 1 (Unknown error) (fault ManagedObjectNotFound, type VmodlVmomiFaultManagedObjectNotFound, reason: (none given), translated to 1) at 1989.

2017-02-15T17:37:25.063+08:00| vthread-4| E105: VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [vsanDatastore] dfc9a258-203e-8b0d-96c9-e03f49b5ce6a/buyaoshan-win-000001.vmdk. Error 1 (Unknown error) at 4680.

2017-02-15T17:37:25.063+08:00| vthread-4| E105: VixDiskLib: VixDiskLib_Open: Cannot open disk [vsanDatastore] dfc9a258-203e-8b0d-96c9-e03f49b5ce6a/buyaoshan-win-000001.vmdk. Error 1 (Unknown error) at 4718.

First of all I'd like to thank the developers for finally bringing VIX API to Mac OS X. That's a great wrok.

I've started a project for packing pure-C VIX API withing ObjC objects, so it can be used in Mac OS X (10.7+, 64bit) applications without cognitive overhead.

It's distributed as a framework. The homepage of the project is https://github.com/Kentzo/VIXObjC.

Everyone interested are welcome.

Hi,

I'm trying to install vix-perl module on a Windows server with cygwin as build environment.

I have unzipped the vix-perl tar in a directory and succesfully executed the 'perl Makefile.PL' command.

When I try to execute 'make' I have the following error message:

make: *** No rule to make target `libvixAllProducts.so', needed by `subdirs'. Stop.

I have not found any documentation about installing vix-perl on Windows server, can someone help me?

Thanks,

   Andrea

Folks:

I think its a basic question. I see that the "VIX API" is listed under Virtual Machine Management section. Does this mean ESX/ESXi management is not supported by VIX API? Please advice. I'm looking to evaluate a tool which can help me automate reading of some of the config settings on ESXi for e.g I would like to check if the SSH running on ESX is using protocol 2 or protocol 1. If you are aware of any tools which can help me achieve this, please advice.

Thanks in advance.

Regards,

Parash

I'm using  VixVM_WriteVariable() function in order to change the "memsize" of an encrypted vm.

Based on the Vix API (version 1.11) documentation advice, I make use of the flag VIX_VM_CONFIG_RUNTIME_ONLY.

The consequence is that the VMware Player GUI displays the updated value for the memory but the Guest OS (Win 2003 Server) still reports the default amount of memory (the one configured in the .vmx file).

Is this a misleading behavior of the VMware Player?

Regards,

Flaviu

Greetings,

The VIX LoginInGuest() API with the VIX_LOGIN_IN_GUEST_REQUIRE_INTERACTIVE_ENVIRONMENT option does not work when a user is interactively logged in via a Windows 7 (64-bit) Remote Desktop (i.e. Terminal Services) session even if VMwareUser.exe is running in the same session.

LoginInGuest() works fine if I log in interactively via the vCenter console (or VNC). However, if I connect to the same session via RDP (and VMwareUser.exe is still running), the same login command fails.

Also, VMwareUser.exe won't launch from within an interactive RDP session.

I'm running VIX 1.12 against vSphere 4.1.0 using VixCOM in .net;

Thank you,

-Randy