Ok. I'm really not sure what to think with all of this, but it's incredibly infuriating.
1. A VIX client won't compile using the wrapper because it's looking for __ctype_b which isn't on my Ubuntu system. Bad. Worse because of #2.
2. There's two libvix.so files, depending on whether I'm connecting to Workstation or Server -- which means that I can't have a single program that connects to either Workstation or Server -- I have to link twice (once for Workstation, once for Server). Bad.
3. VixHost_FindItems works ONLY if I specify VIX_FIND_RUNNING_ITEMS even if I'm connecting to Server. I get the ever-so-helpful "One of the parameters was invalid" if I use VIX_FIND_REGISTERED_ITEMS instead. Statically linking with libvix.so for workstation puts me in an infinite loop on connect, so I can't tell if it's just a problem with the libvix.so for Server. Very Bad.
I need to collect the list of VMs that are currently registered to a VMware Server. I can't do this when following the instructions in the documentation. I smell a whole raft of bugs, because the local-link API should be smart enough to handle this.
Why oh why can't this be easy ... you know, like the SOAP API for ESX? (And yes, compared to the sort of problems that I'm seeing with VIX, the ESX SOAP API is easy.)
