stanguturi's Accepted Solutions

When a user executes 'vmrun' command, vmrun checks for library location and loads all the necessary libraries in a specific order. The order in which the libraries are loaded is specified in a file named 'manifest.txt'. In your test scenario, since you are trying to connect to the remote end ESX server, the library location is /usr/lib/vmware-vix/Workstation-8.0.0-and-vSphere-5.0.0/64bit. The manifest.txt is located at /usr/lib/vmware-vix/Workstation-8.0.0-and-vSphere-5.0.0/64bit/manifest.txt. To resolve the issue, you need to change the library load order little bit. Open the manifest.txt file. The current order to load the libraries is as follows: .... libgobject-2.0.so.0 libgthread-2.0.so.0 ..... Modify the order to load libgthread first before loading the libgobject. The new content should be as follows: .... libgthread-2.0.so.0 libgobject-2.0.so.0 ..... Save the manifest.txt. Remember, all you need to do is to just change the order for gobject and gthread libraries. You don't need to make any other changes. Run 'vmrun' command. Let us know if it works. -Thanks Sankar.

> my $CONNTYPE = "VIX_SERVICEPROVIDER_VMWARE_VI_SERVER"; VIX_SERVICEPROVIDER_VMWARE_VI_SERVER is a constant. Please don't specify that inside the double quotes. Use the following code: my $CONNTYPE = VIX_SERVICEPROVIDER_VMWARE_VI_SERVER; Please take a look at sample perl files available in vix-perl bundle. vix-perl/ - samples/findhosttest.pl - samples/powertest.pl - samples/vmrun.pl -Thanks Sankar.

You're probably hitting the issues reported in the following threads. http://communities.vmware.com/thread/269387?tstart=0 http://communities.vmware.com/thread/264251?tstart=0 -Thanks Sankar.

When you install VIX bundle, you will get VixCOM directory in <VIX INSTALLATION DIRECTORY>. You will find VixCOM.h in VixCOM directory. Check that file. You will find different constants defined. (VIX_API_VERSION etc.) You can refer them in your code by adding VixCOM.Constants. prefix to the constant. Ex: VIX_API_VERSION -> VixCOM.Constants.VIX_API_VERSION. -Thanks Sankar.

On your build machine, you have installed VIX package. On your test machine, you didn't install VIX package. You should install VIX package on your test machine. Feb 03 18:38:42.752: app-3892| Error: VIX wrapper config file (null)\vixwrapper-config.txt not found. Feb 03 18:38:42.752: app-3892| Failed to load wrapper configuration file Since VIX Package is not installed, it didn't find config file (metadata for properly loading libraries]). Please install VIX on your test machine and post if you find any issues. -Thanks Sankar.

How many VMS you are trying to power on concurrently using your program? You might be able to poweron each VM manually. But, enough resources might not be available to poweron multiple VMs concurrently. Also, check this link . You may find it useful. -Thanks Sankar.

As Lemke specified in coment #1, you cannot get the stdio output to your server/host from which you are running vmrun. If you want to get the output of "ipconfig" command, follow these instructions. 1. Create a script file. inside the Guest. 2. In Guest, open your favorite text editor and populate the script.bat with following contents. ipconfig > C:\ip.txt 3. Using vmrun, execute the script.bat using runprograminguest command. Now, ipconfig information will be pumped to file C:\ip.txt in guest. Using vmrun, copy that file from guest to host. Ex: vmrun.exe -gu guestadministrator -gp password runprograminguest C:\path\windowsvm C:\script.bat Provided the above command is successful, vmrun.exe -gu guestadministrator -gp password copyfilefromguesttohost C:\path\windowsvm C:\ip.txt /path/of/file/on/host (I executed the same commands on my box. It worked. If you encounter any issues, please update the bug) Now the new copied file on host will contain the guest's ipconfig details. -Thanks Sankar.