ldconfig fixed it.
1 person found this helpful
When using ldconfig on ubuntu 10.04, the libraries that are installed with vixDiskLib are old enough to cause issues with other applications. To solve the problem, I had to create shell scripts to isolate the library path like this:
LD_LIBRARY_PATH=/usr/lib/vmware-vix-disklib/lib64 vmware-mount \
-v "KS-PROD-Datacenter/vm/vMA" -h vcenter.company.com -u "administrator@company" \
-F /root/.password -f "[VM-Appliances] vMA/vMA-000001.vmdk" /mnt/test/
/usr/lib/vmware-vix-disklib/ [ lib32 or lib64 ] is the default place that it's installed on linux.
Just thought I would add my 2 cents here in case anyone else was having difficulties (like I was).
Thank you very much!
create /etc/ld.so.conf.d/vmware-vix.conf with the following content
/usr/lib/vmware-vix-disklib/lib64 (if you are using 64 bit)
/usr/lib/vmware-vix-disklib/lib32 (if you are using 32 bit)
Then run ldconfig
Benichou, although that would be the proper way to do it, on my systems (Ubuntu 10.04 LTS), it causes issues:
# vi /etc/ld.so.conf.d/vmware-vix.conf
vim: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0: undefined symbol: g_cclosure_marshal_VOID__VARIANT
Because of this, I have to use a script and specify it on the command line on a per script basis.
If VMware would release this in source form, or at the very least link against the systems libraries, this would be avoided.