Quantcast
Channel: VMware Communities : Discussion List - Virtual Disk Development Kit
Viewing all articles
Browse latest Browse all 2039

non-ASCII tmpDirectory value?

$
0
0

Hi -

 

I am trying to find out whether non-ASCII characters can be used when configuring the tmpDirectory in the config file inputted to VixDiskLib_InitEx such that VixDiskLib can use advanced transports.  In my case, it appears to be unable to read the tmp directory path from the config file, and consequently will not allow advanced transports (in this case, hotadd).

 

Below is all the information about what I tried and the log output I received.

 

- Jenni

 

The config file I feed to VixDiskLib_InitEx has the following contents:

tmpDirectory = "C:\Documents and Settings\Administrator\Local Settings\Configuración local\Temp\jenni"

 

(I also attempted encapsulating the path with single quotes as well.)

 

This is the vddk logging output (note that the libdir value is actually Configuración, not Configuración.  I believe that's just an artifact from how the log is being printed as VDDK appears to find the libdir fine.):

 

VixDiskLib_InitEx:

debug:  VixDiskLib: config options: libdir 'C:\Documents and Settings\Administrator\Local Settings\Configuración local\Temp\201104131326\Vddk-1.2.1', tmpDir '<null>'.
debug:  VixDiskLib: Advanced transport plugin was successfully loaded into vixDiskLib. Accelerated transport modes available.
debug:  VixDiskLib: Enabling advanced transport modes.
debug:  VixDiskLib: Cannot find temporary directory. Disabling advanced transport modes.
debug:  VMware VixDiskLib (1.2) Release build-323406
debug:  Using system libcrypto, version 90809F
VixDiskLib_ConnectEx log output:
debug:  TicketResolveHostName: Resolving IP address for hostname vc.dev.eng.int.
debug:  TicketResolveHostName: Resolved to 10.11.11.11.
debug:  VixDiskLibVim: TicketLogin
debug:  VixDiskLibVim: TicketFindVMByMoRef: vmxPath = -vm-656-
debug:  VixDiskLibVim: TicketLoadVM
debug:  VixDiskLibVim: Root Snapshot list has 1 elements.
debug:  VixDiskLibVim: Unable to find key for disk [DEV-iSCSI01] KAS-FD0/KAS-FD0.vmdk, trying snapshot tree.
debug:  VixDiskLibVim: TicketCollectSnapshots
debug:  VixDiskLibVim: TicketLoadSnapshot
debug:  VixDiskLibVim: TicketLoadVMCb
debug:  VixDiskLibVim: TicketLoadInternalSic
debug:  VixDiskLibVim: TicketLoadNfcTicket: Request GetVMFiles diskKey = 2000, readOnly = 1, openSnapshot = 1
debug:  VixDiskLibVim: TicketLogout
debug:  NBD_ClientOpen: attempting to create connection to vpxa-nfc://[DEV-iSCSI01] KAS-FD0/KAS-FD0.vmdk@dev029.dev.eng.int:902
debug:  Started up WSA
debug:  SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:
* The host certificate chain is not complete.
debug:  SSLVerifyIsEnabled: failed to read registry value. Falling back to default behavior: verification off. LastError = 0
debug:  SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
debug:  Opening file [DEV-iSCSI01] KAS-FD0/KAS-FD0.vmdk (vpxa-nfc://[DEV-iSCSI01] KAS-FD0/KAS-FD0.vmdk@dev029.dev.eng.int:902)
debug:  DISKLIB-LINK  : Opened 'vpxa-nfc://[DEV-iSCSI01] KAS-FD0/KAS-FD0.vmdk@dev029.dev.eng.int:902' (0x1e): custom, 102400 sectors / 50 MB.
debug:  DISKLIB-LIB   : Opened "vpxa-nfc://[DEV-iSCSI01] KAS-FD0/KAS-FD0.vmdk@dev029.dev.eng.int:902" (flags 0x1e, type custom).

 

 

At this point, the code finds that VixDiskLib_ConnectEx has given us an NBD connection instead of the desired HOTADD connection (presumably due to the tmpdir coming up as null).  I confirmed that given a tmpDirectory value using all ASCII characters, this same setup can connect using HOTADD without issue.


Viewing all articles
Browse latest Browse all 2039

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>