It would seem I'm going to be plagued with issues my entire way through using Vix.
I finally got the Perl bindings for Vix to build on both Linux and Windows, however on both HostConnect() fails, and in different ways.
I have seen some other posts that allude to the fact that using the 1.1 API under Linux may not work correctly. The behavior I'm seeing is that when connecting to both SSL and Non-SSL machines with VM Server 1.0 running, authentication fails and HostConnect() retries forever. The same hostname/port/username/password work fine if I attempt to connect via the VM Server Console interface.
Under Windows, I have set the API version in HostConnect() to a hardcoded 1, as discussed in other posts. Regardless of whether I use 1 or 2, I get the following error message:
Failed to get property type for 3010 on handle 0.
HostConnect() failed, 1000 The handle is not a valid VIX object
I am using the exact code from the reference documentation on HostConnect(). I have also tried setting it to not use localhost and instead use other VM Servers, with identical results. I also tried both with SSL on and off, with identical results.
At this point I'm stumped as to why this does not work - any help would be appreciated.
Also, if someone could clarify the compatibility between VM Server 1.0 and VIX API 1.1? What in particular cannot be used with VM Server (in particular, are guest operations supported)?
Also, looking through the reference documentation, there seem to be some functions that have no associated Perl documentation (in particular, the Perl functions that correspond to the VixJob_* functions in C).
To answer your questions in reverse order:
None of the VixJob functions are present in the Perl bindings, since it uses a simpler model. Specifically, all the functions in the Perl bindings are synchronous, so they return their results directly, as opposed to the C and COM flavors which return a Job handle/object that track the progress and state of an asynchronous call.
Since these functions do not exist in the Perl bindings, they are of course not documented.
In terms of compatibility, please see the announcement at the top of the forum. We strongly recommend against using 1.1 version of the VIX API with VMware Server. Only functions from the 1.0 release will work with Server (those listed in the requirements section of the documentation as "since VMware Server 1.0"), so no new functionality is available for use with Server in the 1.1 release.
As for why HostConnect(), the make script that builds the Perl bindings in the 1.1 API builds the bindings to work with Workstation, not Server. Again, we recommend that you use the 1.0 release of the VIX API that comes bundled with VMware Server, particularly with the Perl bindings.
