All Posts

Hello, I have a Virtual Machine on ESXi 7.0: Guest OS: Microsoft Windows Server 2016 (64-bit) Compatibility: VmHardware.HWVersion.long.vmx-19 VMware Tools: Running, version:11333 (Current)     It has only one disk on SCSI controller 0: Type: Thick Provision Lazy Zeroed Disk File: [d2] 2016/2016.vmdk Disk Mode: Dependent       quiesced snapshot part After creating a quiesced snapshot, I found that it had two delta files(aka child disks) which is strange because only one delta file should be generated:   vCenter shows that the virtual machine is now using [d2] 2016/2016-000001.vmdk: And Managed Object Browser shows that the disk recorded in the snapshot is [d2] 2016/2016-000002.vmdk Obviously I can't open them READ ONLY through VDDK 7.0.3, NBD transport mode: KLog: NBD_ClientOpen: attempting to create connection to vpxa-nfc://[d2] 2016/2016-000001.vmdk@192.168.88.230:902 KLog: Setting NFC log level to 1 KLog: Setting NFC log level to 1 KLog: NFC Async IO session is established for '[d2] 2016/2016-000001.vmdk' with log level 1. KLog: Opening file [d2] 2016/2016-000001.vmdk (vpxa-nfc://[d2] 2016/2016-000001.vmdk@192.168.88.230:902) KWarning: [NFC ERROR]NfcAioRcvErrorMsg: Error from server: NfcAioProcessOpenFileMsg: Failed to open '[d2] 2016/2016-000001.vmdk': DiskLib error 49: Thin/TBZ/Sparse disks cannot be opened in multiwriter mode KLog: Fail to open file [d2] 2016/2016-000001.vmdk KLog: DISKLIB-DSCPTR: : "vpxa-nfc://[d2] 2016/2016-000001.vmdk@192.168.88.230:902" : Failed to open NBD extent. KLog: DISKLIB-LINK : "vpxa-nfc://[d2] 2016/2016-000001.vmdk@192.168.88.230:902" : failed to open (Thin/TBZ/Sparse disks cannot be opened in multiwriter mode). KLog: DISKLIB-CHAIN : "vpxa-nfc://[d2] 2016/2016-000001.vmdk@192.168.88.230:902" : failed to open (Thin/TBZ/Sparse disks cannot be opened in multiwriter mode). KLog: DISKLIB-LIB : Failed to open 'vpxa-nfc://[d2] 2016/2016-000001.vmdk@192.168.88.230:902' with flags 0xe Thin/TBZ/Sparse disks cannot be opened in multiwriter mode (49). KLog: VixDiskLib: Detected DiskLib error 49 (Thin/TBZ/Sparse disks cannot be opened in multiwriter mode). KLog: VixDiskLib: Failed to open disk vpxa-nfc://[d2] 2016/2016-000001.vmdk@192.168.88.230:902!52 26 a2 59 d8 1d 32 3e-af 4e c9 d9 18 f1 5e b5. Error 1 (Unknown error) (DiskLib error 49: Thin/TBZ/Sparse disks cannot be opened in multiwriter mode) at 6469. KLog: VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [d2] 2016/2016-000001.vmdk. Error 1 (Unknown error) (DiskLib error 49: Thin/TBZ/Sparse disks cannot be opened in multiwriter mode) at 7133. KLog: VixDiskLib: VixDiskLib_Open: Cannot open disk [d2] 2016/2016-000001.vmdk. Error 1 (Unknown error) at 7211. Failed to open   KLog: VixDiskLib: VixDiskLib_OpenEx: Open a disk. KLog: 2021-11-19T16:19:01.733+08:00 error -[05958] [Originator@6876 sub=vimaccess] GetFileName: Cannot create disk spec for disk [d2] 2016/2016-000002.vmdk. KLog: --> KLog: VixDiskLib: Error occurred when obtaining the file name for [d2] 2016/2016-000002.vmdk. Error 1 (Unknown error) (Cannot create disk spec for disk.) at 3344. KLog: VixDiskLib: VixDiskLib_OpenEx: Cannot open disk [d2] 2016/2016-000002.vmdk. Error 1 (Unknown error) at 7133. KLog: VixDiskLib: VixDiskLib_Open: Cannot open disk [d2] 2016/2016-000002.vmdk. Error 1 (Unknown error) at 7211. Failed to open   But I CAN open [d2] 2016/2016.vmdk to read, so I backup the whole [d2] 2016/2016.vmdk disk(not just allocated blocks) through VDDK. Finally, I restored the disk to the virtual machine. And try to use it to start the virtual machine, but the blue screen is directly displayed when starting:     none quiesced snapshot part So I created a none quiesced snapshot instead. And it has only ONE delta file as expected. I backup [d2] 2016/2016.vmdk through VDDK 7.0.3 and restore to the virtual machine again. And the operating system can be turned on normally this time.   question How do I back up this virtual machine with a quiesced snapshot?

We tried to backup a machine many times ,the machine occasionally failed to use HotAdd and fell back to NBD transport method。 The vddk log is following： VixDiskLib:vixDiskLib ConnectEx:Advanced transport modes not available for opening moref=695. Cannot use advanced transport modes for <ESXi IP>/moref=695/695-snapshot-47：Invalid search specifier: moref:695.) This happened occasionally. Does any one have any idea of what could be going wrong here? Environment:  ESXi 6.5  and  VDDK 6.7.3

I was working on assigning ips to virtual_nic devices. For that, I was trying to map GuestNicInfo information to the vnic device. First, I tried to map using macAddress present in both these objects, but observed that in some cases it was differing. Then, tried to map deviceConfigId present in GuestNicInfo (as it is a mandatory field) to key present in nic device. Observed that deviceConfigId is coming as -1 in some cases. What is the expected behaviour here? Do we expect deviceConfigId to be -1?

When I try to open the disk through vddk 7.0.2., I got the following error: ==================================================================== [2021/06/24 18:20:11][VDDK] [share_disk1] freedos7/FreeDos-VMv7.vmdk [2021/06/24 18:20:11][VDDK] Error: Unknown error [2021/06/24 18:20:11][VDDK] Error: 0x1 [2021/06/24 18:20:11][VDDK] Error: src\VddkLibDiskManager.cpp [2021/06/24 18:20:11][VDDK] Error: 33 [2021/06/24 18:20:11][VDDK] Debug: CVddkLibDiskManager open - Disk: [share_disk1] freedos7/FreeDos-VMv7.vmdk [2021/06/24 18:20:11][VDDK] Info: VixDiskLib: VixDiskLib_OpenEx: Open a disk. [2021/06/24 18:20:11][VDDK] Info: VixDiskLib: VixDiskLib_OpenEx: Failed to start session. Cannot get compatible version for vim at 7149. [2021/06/24 18:20:11][VDDK] Info: VixDiskLib: VixDiskLib_Open: Cannot open disk [share_disk1] freedos7/FreeDos-VMv7.vmdk. Error 1 (Unknown error) at 7250. ====================================================================   I found some article that recommend the open and close disk operation should in the main thread and I put them in multi-thread.  Something like this: thread 1 : open disk1........... close disk1.... thread 2 : open disk2........... close disk2.... Is this the reason that I got such error when I tried to open the disk?

When using the VDDK7.0.2, i am getting the below error. Can someone guide us: The VM has virtual hardware version 14. Not able to figure out the issue in regards to compatible version. We use an older connectSpec ========= [110] [VddkUtil::diskLibLog] VixDiskLib: VixDiskLibConnectInt: Failed to start session. Cannot get compatible version for vim at 5720. [110] [VddkUtil::diskLibLog] VixDiskLib: VixDiskLib_ConnectEx: Advanced transport modes not available for opening moref=vm-17604. (Cannot use advanced transport modes for 10.10.01.01/moref=vm-17604/snapshot-17607: Cannot get compatible version for vim.) [110] [VddkUtil::diskLibLog] VixDiskLib: VixDiskLib_OpenEx: Open a disk. [110] [VddkUtil::diskLibLog] VixDiskLib: VixDiskLib_OpenEx: Failed to start session. Cannot get compatible version for vim at 7149. [110] [VddkUtil::diskLibLog] VixDiskLib: VixDiskLib_Open: Cannot open disk [DS] New Virtual Machine/New Virtual Machine.vmdk. Error 1 (Unknown error) at 7250. ========  

Hi, While using VDDK version 7.0.2, when calling VixDiskLibInitEx() I am getting the error 'Failed to load vddkVimAccess.dll : ErrorCode = 0xb6'. Although the vddkVimAccess.dll is in same folder as VixDiskLib.dll. Where do we meant by error code 0xb6 ? Does anybody has idea about it?