Quantcast
Channel: VMware Communities : Popular Discussions - VIX API
Viewing all articles
Browse latest Browse all 34639

tool working against WS 6, but not server 1.0.1

$
0
0

 

  Regarding the text posted below, and posted at the top of this Virtual Machine Automation APIs (VIX API) community, does this mean literally that 1 (or is it '1'?) should be used instead of VIX_API_VERSION in the call to VixHost_Connect?    I have some test code that's working on my laptop against VMware Workstation 6.0.   But it isn't working when I take the code to a desktop machine with same OS but has VMware Server 1.0.1 instead of workstation... despite recompiling it with appropriate CONNTYPE for use with VMware Server and using 1 as the VERSION as noted above (and below).   Both have 1.1.3 of VMware-VIX installed.   I also tried it after recompiling it with the appropriate CONNTYPE but before changing the first parameter to VixHost_Connect to a 1.   Should that be a '1' (1 in quotes) instead?

 

 

Perhaps I should use an earlier version of vix?   I don't at this time, have the luxury of using a newer version of VMware server...

 

 

Thanks

 

 

      • BEGIN QUOTED MESSAGE ***

Vix 1.1 is recommended for VMware Workstation 6.0, not VMware Server 1.0

 

Expiring the announcement will not delete it but will remove it from the public announcement list.  Are you sure you want to expire this announcement?

 

Are you sure you want to delete this announcement?

 

    Vix API 1.1 does not add any new functionality for use with VMware Server. Currently, we recommend that you do not upgrade to Vix 1.1 if you are using VMware Server.

 

    The VixAllProducts library is intended allow you to write code that works against either Workstation or Server. But the 32bit Linux wrapper was built for old versions of glibc (known bug). On Windows the wrapper will work, but you need to use the value '1' for the apiVersion argument to VixHost_Connect().

 

    We understand this has created real frustration, and apologize for any inconvience and confusion. We are working to fix these issues as quickly as possible.

      • END OF QUOTED MESSAGE ***

 

 

 


Viewing all articles
Browse latest Browse all 34639

Trending Articles



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