VIX 1.12.x was released with Workstation 9 / Player 5 and is not compatible with Player 6.0. We will be releasing a new version of vix (1.13.0) for Workstation 10.0 and Player 6.0.0 We will updat...
See more...
VIX 1.12.x was released with Workstation 9 / Player 5 and is not compatible with Player 6.0. We will be releasing a new version of vix (1.13.0) for Workstation 10.0 and Player 6.0.0 We will update the post with the VIX download links once the VIX bits are uploaded. -Thanks Sankar.
There is a workaround. Follow these steps. - Execute VixVM_ListProcessesInGuest(). This api lists down the information (owner, process id, command name, etc) about all the running processes in...
See more...
There is a workaround. Follow these steps. - Execute VixVM_ListProcessesInGuest(). This api lists down the information (owner, process id, command name, etc) about all the running processes in the guest. - From the list, check for processes which have 'vmtoolsd' and 'vmusr' in the command name. - Get the owner of the matching processes. This gives the information about the currently logged in user. You can use 'vmrun' (command line utility bundled with VMware VIX API) to list the processes running in the guest. Use your favorite grep utility to search in the 'vmrun' output. Ex: vmrun -gu guestuser -gp guestpassword listprocessesinguest /path/to/myvm.vmx | grep -i vmtoolsd | grep -i vmusr pid=1412, owner=WINXP64-IRON\guestadmin, cmd="C:\Program Files\VMware\VMware Tools\vmtoolsd.exe" -n vmusr Check the owner. The currently logged in user is guestadmin.
> gcc -O0 -g3 -Wall -lvixAllProducts -ldl -lpthread -I/usr/include/vmware-vix -MMD -MP -MF"src/Connection.d" -MT"src/Connection.d" -o "src/Connection.o" "../src/Connection.c" When you execute ...
See more...
> gcc -O0 -g3 -Wall -lvixAllProducts -ldl -lpthread -I/usr/include/vmware-vix -MMD -MP -MF"src/Connection.d" -MT"src/Connection.d" -o "src/Connection.o" "../src/Connection.c" When you execute the above command, what error did you get?
Please check https://www.vmware.com/support/developer/vix-api/vix111_reference/intro.html#13_95619 for information about compiling programs in linux. Sample command: gcc -I/usr/include/vmw...
See more...
Please check https://www.vmware.com/support/developer/vix-api/vix111_reference/intro.html#13_95619 for information about compiling programs in linux. Sample command: gcc -I/usr/include/vmware-vix vixapp.c -o vixapp -lvixAllProducts -ldl -lpthread
You need to specify -l option with the vix library name. Check http://bit.ly/vixapi for programming guide.
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 fi...
See more...
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.
Few days back, I encountered the same issue. I resolved it by installing Microsoft Visual Studio 2008 (Full edition, after un-installing the Visual Studio 2010) and applying Visual Studio 2008 se...
See more...
Few days back, I encountered the same issue. I resolved it by installing Microsoft Visual Studio 2008 (Full edition, after un-installing the Visual Studio 2010) and applying Visual Studio 2008 service pack1. -Thanks Sankar.
The latest version of vix (1.11) was released few days back. Download the latest vix bundle from http://bit.ly/vixapi. Check the release notes at https://www.vmware.com/support/developer/vix-api/...
See more...
The latest version of vix (1.11) was released few days back. Download the latest vix bundle from http://bit.ly/vixapi. Check the release notes at https://www.vmware.com/support/developer/vix-api/VIX-1.11-ReleaseNotes.html#NewFeatures We have added a new option "directoryExistsInGuest" to vmrun. This should solve your problem. -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 $...
See more...
> 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.
> I'm running 1.10.2. When I execute the runprograminguest what I get is some output (maybe the stderr printed by the executed app) and a -1 return code so I have no way of knowing if the one t...
See more...
> I'm running 1.10.2. When I execute the runprograminguest what I get is some output (maybe the stderr printed by the executed app) and a -1 return code so I have no way of knowing if the one that failed was vmrun or the executed app (and I'm losing the original errorcode by the way). If the program fails inside the guest, then vmrun captures the return value of the guest program and returns it back to the caller. Also when the program fails inside the guest, vmrun prints the following: Guest program exited with non-zero exit code:<returnerror code of the guest program> If you received -1 error and didn't see the above message, then the error is related to vmrun. -Thanks Sankar.
> - You have no way of knowing if executeProgramAtGuest has succeded or not as you don't get the exit code of the executed program. What version of vmrun are you using? When you execute a prog...
See more...
> - You have no way of knowing if executeProgramAtGuest has succeded or not as you don't get the exit code of the executed program. What version of vmrun are you using? When you execute a program using vmrun via "runprograminguest" option, vmrun prints the errorcode on the console if the program terminates with a non-zero exit code in the guest. Also, vmrun returns the errorcode back to the caller. -Thanks Sankar.
> - GetPowerState. You can use "vmrun list" command which will give a list of all running VMs. You can check if the list contains the required VM. > - ReadingEnvVariables does not work. What...
See more...
> - GetPowerState. You can use "vmrun list" command which will give a list of all running VMs. You can check if the list contains the required VM. > - ReadingEnvVariables does not work. What is the exact issue that you encountered with this option?
vmrun is not a 1:1 mapping of the VIX API, but this is a good request, and we will look at adding this new option to vmrun in the next release. -Thanks Sankar.
You can download VSphere SDK for perl. You can find a sample perl script vifs.pl that allows you copy files between your host (Machine from which you execute your programs) and ESX datastore. ...
See more...
You can download VSphere SDK for perl. You can find a sample perl script vifs.pl that allows you copy files between your host (Machine from which you execute your programs) and ESX datastore. -Thanks Sankar.
No. It is not possible to capture the output of a command executed inside the virtual machine and display it on the console using vmrun. -Thanks Sankar.
