All Posts

This is what is described in the guide: For VixDiskLib_Open, The following flags modify the open instruction: VIXDISKLIB_FLAG_OPEN_UNBUFFERED – Disable host disk caching. How do I understand this sentence(Disable host disk caching)? Thanks.

Please see the call stack below due to which user process hangs. vixdisklib 6.7.1.35969 (file version) build 10362358 (product version) # Child-SP RetAddr Call Site 00 0000000f`d31fe068 00007ffe`c882d831 win32u!NtUserWaitMessage+0x14 01 0000000f`d31fe070 00007ffe`c882d5a1 user32!DialogBox2+0x261 02 0000000f`d31fe110 00007ffe`c887d22b user32!InternalDialogBox+0x12d 03 0000000f`d31fe170 00007ffe`c887bb45 user32!SoftModalMessageBox+0x85b 04 0000000f`d31fe2c0 00007ffe`c887c937 user32!MessageBoxWorker+0x341 05 0000000f`d31fe470 00007ffe`c887c9be user32!MessageBoxTimeoutW+0x1a7 06 0000000f`d31fe570 00007ffe`b1464e88 user32!MessageBoxW+0x4e 07 0000000f`d31fe5b0 00007ffe`b15020af vixDiskLib!VixDiskLib_FreeErrorText+0x4808 08 0000000f`d31fe5e0 00007ffe`b15032b1 vixDiskLib!VixDiskLib_FreeErrorText+0xa1a2f 09 0000000f`d31fe610 00007ffe`b15035e7 vixDiskLib!VixDiskLib_FreeErrorText+0xa2c31 0a 0000000f`d31fe6f0 00007ffe`b15fd49a vixDiskLib!VixDiskLib_FreeErrorText+0xa2f67 0b 0000000f`d31fe730 00007ffe`b15eafed vixDiskLib!VixDiskLib_FreeErrorText+0x19ce1a 0c 0000000f`d31feb90 00007ffe`b15053d2 vixDiskLib!VixDiskLib_FreeErrorText+0x18a96d 0d 0000000f`d31fefc0 00007ffe`b1482381 vixDiskLib!VixDiskLib_FreeErrorText+0xa4d52 0e 0000000f`d31feff0 00007ffe`b1482a3c vixDiskLib!VixDiskLib_FreeErrorText+0x21d01 0f 0000000f`d31ff050 00007ffe`b1451430 vixDiskLib!VixDiskLib_FreeErrorText+0x223bc 10 0000000f`d31ff0e0 00007ff7`80c0dc40 vixDiskLib!VixDiskLib_Write+0x140 11 0000000f`d31ff130 00007ff7`80c0b088 OUR-private-module!OUR-private-function+0x1a0 vixDiskLib!VixDiskLib_Write function is called with a valid handle, valid buffer, offset and length of 1 sector of 4096. Disk it was trying to write is 503 GB. ( a integer sized disk). @VMware, please help. please share the insight. Thanks.

I am trying to access remote VMDK using VDDK via hotadd transport mode but  it seems that the system consistently falls back to utilizing the NBD internally, rather than successfully utilizing the HotAdd transport mode as intended. Below are the logs for the query. We have initialised the required values for VixDiskLib_InitEx() including libdir which points to lib64. Also after using VixDiskLib_ListTransportModes() we get the output as file:nbdssl:nbd. How do we enable VDDK to work for advanced transports. Are there any additional prerequisites or virtual machine configurations that might be required to enable the successful use of the HotAdd transport mode for remote VMDK access? Any insights, suggestions, or troubleshooting steps will be of great help.

I am trying to open a VMDK file on a VMFS datastore via mount but the Vixdisklib_Open() function returns error code 16063 ("The specified file is not a virtual disk"). Same API works with NFS datastore.  Note: we have mounted the VMFS datastore using vmfs6-tools on the ubuntu system where the VDDK is running.  After further debugging, we noticed that Vixdisklib_Open() works for MAIN vmdk file (createType="vmfs" and data file is -flat.vmdk). But it fails with the SESPARSE snapshot vmdk file (createType="seSparse" and data file is -000001-sesparse.vmdk) Are there additional parameters to set while opening SESPARSE snapshot vmdk file?  

Proxy agent：Ubuntu 16 and Ubuntu 20 VDDK version: VDDK 6.7、7.0、8.0 Reading ONE disk through SAN is successful, but reading multiple virtual machine disks simultaneously will fail (each virtual machine's disk is on the same LUN)   2023-06-08 15:39:30.173@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.160+08:00 error -[3701150] [Originator@6876 sub=Default] Incomplete read from, Wanted 1048576 Got 0, Error 2 (52) 2023-06-08 15:39:30.174@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.160+08:00 trivia -[3701150] [Originator@6876 sub=Default] Evaluating 1 paths. 2023-06-08 15:39:30.175@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.160+08:00 trivia -[3701150] [Originator@6876 sub=Default] Trying to open path /dev/sdc. 2023-06-08 15:39:30.176@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.174+08:00 info -[3701150] [Originator@6876 sub=Default] Now using Path /dev/sdc. 2023-06-08 15:39:30.177@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.176+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.177@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.176+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.178@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.176+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.179@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.177+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.179@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.177+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.180@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.177+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.181@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.179+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.181@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.179+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.182@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.179+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.183@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.181+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.184@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.181+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.184@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.181+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.186@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.183+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.187@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.183+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.188@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.183+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.188@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.184+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.189@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.184+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.190@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.184+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.191@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.186+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.192@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.186+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.192@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.186+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.193@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.191+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.194@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.192+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.194@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.192+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.195@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.193+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.196@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.193+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.197@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.193+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.197@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.196+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.200@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.196+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.201@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.197+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.201@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.198+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.202@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.199+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.203@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.199+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.203@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.201+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.204@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.201+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.206@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.201+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.207@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.206+08:00 error -[3701150] [Originator@6876 sub=Default] Incomplete read from, Wanted 1048576 Got 0, Error 2 (52) 2023-06-08 15:39:30.208@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.206+08:00 trivia -[3701150] [Originator@6876 sub=Default] Evaluating 1 paths. 2023-06-08 15:39:30.209@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.206+08:00 trivia -[3701150] [Originator@6876 sub=Default] Trying to open path /dev/sdc. 2023-06-08 15:39:30.210@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.209+08:00 info -[3701150] [Originator@6876 sub=Default] Path /dev/sdc seems to be inactive, ignoring. 2023-06-08 15:39:30.210@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.209+08:00 error -[3701150] [Originator@6876 sub=Default] No active paths found. 2023-06-08 15:39:30.211@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.209+08:00 error -[3701150] [Originator@6876 sub=BlockList] 2023-06-08 15:39:30.212@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.209+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.213@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.209+08:00 error -[3701150] [Originator@6876 sub=Default] San transport error: I/O Operation failed. 2023-06-08 15:39:30.214@infokist@3658437@LM_INFO@155|DISKLIB-LIB : RWv failed ioId: #723 (4096062) (62) . 2023-06-08 15:39:30.215@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.209+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread enlisted 2023-06-08 15:39:30.216@infokist@3658437@LM_INFO@155|2023-06-08T15:39:30.209+08:00 trivia -[3701150] [Originator@6876 sub=ThreadPool] Thread delisted 2023-06-08 15:39:30.217@infokist@3658437@LM_INFO@155|VixDiskLib: Detected DiskLib error 4096062 (One of the parameters supplied is invalid). 2023-06-08 15:39:30.218@infokist@3658437@LM_INFO@155|VixDiskLib: VixDiskLib_Read: Read 2048 sectors at 1478656 failed. Error 16000 (One of the parameters supplied is invalid) (DiskLib error 4096062: One of the parameters supplied is invalid) at 7867. 2023-06-08 15:39:30.219@infokist@3658437@LM_ERROR@155|Failed to read disk, VM=5235c7db-ae8b-ebb2-9733-1439edfd478b, vix_error=16000, err_msg=One of the parameters supplied is invalid 2023-06-08 15:39:30.220@infokist@3658437@LM_ERROR@155|Failed to read data from disk [san_test_lmy_2T] san_test-lmy-ubuntu1604/san_test-lmy-ubuntu1604.vmdk, offset 757071872, maxlen 1385694208

I am trying to access the remote VMDK using the latest VDDK Kit (version – 8.0.1) by calling the VixDiskLib_ConnectEx() function to connect to the datastore. The function returns the vixError Status code to be 3 (VIX_E_INVALID_ARG).  I have attached the code snippet that I am trying to use for the same. Need assistance in identifying the following aspects: Clear format of required structure for cnxParams->vmxSpec , cnxParams->serverName, cnxParams->spec.dsSpec.datastoreMoRef, cnxParams->spec.dsSpec.diskFolder. Do we need to initialize any other parameter for making the connection apart from the one’s mentioned in the code snippet if we want to have a datastore level access to VMDK. Any other pointers that we need to keep in mind while making connection to remote server. FYI – we are able to establish the connection to local server using VixDiskLib_Connect() by taking cnxParams as NULL.

Hi, I downloaded VDDK8.0 and found that vmware-mount binary is missing. Read on the forum that Vmware no longer ships this binary with VDDK. Is there a safe alternative that VMWare suggests? Or is it now part of some other SDK?   -- Thanks, Saurabh 

VDDK version 7.0.3.2 includes few third party packages which have known security vulnerabilities: zlib-1.2.12 (https://nvd.nist.gov/vuln/detail/CVE-2022-37434) OpenSSL-1.0.2ze (https://nvd.nist.gov/vuln/detail/CVE-2022-2068) curl-7.76.1 (https://nvd.nist.gov/vuln/detail/CVE-2021-22901, https://nvd.nist.gov/vuln/detail/CVE-2021-22898, https://nvd.nist.gov/vuln/detail/CVE-2021-22897)   Could someone please share some details on whether the above-states vulnerabilities are affecting (and/or can be exploited via) the VDDK? If so, we would kindly request a 7.0.3.X VDDK update with those third party packages upgraded to patched version. If VDDK is not affected, it would be great to have some details why/how  Thanks a lot!

  Hi,  I have sometimes corrupted vmdk-files which do not boot anymore. How can I repair such files ? Is VMWare Virtual Disk Development Kit useful for this ? Since I am not experience please denote in detail.   Regards, mainze