All Posts

Look at the http://pubs.vmware.com/vi301/sdk/ReferenceGuide/vim.cluster.DrsConfigInfo.html this will tell what objects that you need to monitor. Basically, from a Host Object, you would find the owning ComputeResource and then follow the data from there.

At present there is no way to grown a VMDK using the SDK. The "edit" method is to replace it. You can use VMKFSTOOLS on COS to modify the VMDK size, if I remember. It's on the list of futures to enable that via the SDK. Programmatically, your choice is to create a new VMDK with the required size. Copy the old contents to the new and then replace the drive.

Using perl has nothing to do with the configuring the Virtual Center server. The good news is that we will be releasing a beta version of the VI Perl Toolkit in the next few weeks which should make it easier to you to install and run the supplied sample app. I would suggest that you install that beta when available. H

I'll start with what's happening with the Linux environment. First it might help if I explain what I'm trying to do. I am building a Rexx wrapper for the VMWare Vix API to enable VMWare Server to be controlled via a Rexx program. I am generating the wrapper code from the vix.h header file. Linking against the libvmware-vix.so that comes with VMWare Server 1.0.3, and a number of undefined references result; I assume that these are functions in the 1.1 Vix API that are only available when using Workstation. This is not a real problem, but annoying that there are incompatibilities between the two products. As far as linking with the libVixAllProducts.a static library and having to install an old version of gcc is not an ideal situation when you are distributing a wrapper library for other to use and providing installation instructions: "You will need to download the Vix API SDK, and install an old version of gcc." This is not going to encourage people to use it; I'm not even prepared to install an old version of gcc just to try and make this work. Using code that used to work with the 1.0 Vix SDK, I now get the error: "One of the parameters was invalid" on Vix_HostConnect(). Now with an API function that takes 9 parameters, this is a useless error message; at least WHICH parameter is in error would help. I tried using 1 as the ApiVersion as suggested in another thread. Details of the problems I'm having with the Windows version of the Vix 1.1 SDK will be posted in another post. Seriously considering moving back to the 1.0 SDK. Cheers, Mark

I was hoping to be able to run it, but I since I have no knowledge of perl, I failed. If it is not to much troubles for you, can you tell me what I need to install and configure on my virtual center server, in order to use it. Thanks.

This also solved my problem with Visual C+, unfortunately not DevC+ The C code connect example[/b] #include "stdafx.h" #include <vix.h> int _tmain(int argc, _TCHAR* argv[]) { VixHandle jobHandle = VIX_INVALID_HANDLE; VixHandle hostHandle = VIX_INVALID_HANDLE; VixError err = VIX_OK; jobHandle = VixHost_Connect(1,VIX_SERVICEPROVIDER_VMWARE_SERVER,NULL,0,NULL,NULL,0,VIX_INVALID_HANDLE,NULL,NULL); err = VixJob_Wait(jobHandle, VIX_PROPERTY_JOB_RESULT_HANDLE, &hostHandle, VIX_PROPERTY_NONE); if (VIX_OK != err) { printf("\nError: %i",err); printf("\n%s\n",Vix_GetErrorText(err,NULL)); goto abort; } else { printf("connection success!\n"); } Vix_ReleaseHandle(jobHandle); abort: return 0; }