All Posts

I personally have had very little success using -m32 with a 64 bit gcc to link with 32 bit libraries -- it tends to have major issues with CRT code. Do you have any issues on a 32 bit Linux? ... See more...
I personally have had very little success using -m32 with a 64 bit gcc to link with 32 bit libraries -- it tends to have major issues with CRT code. Do you have any issues on a 32 bit Linux? Im still confused what versions are being used -- the ws-2 directory is part of the Workstation 6 Vix, and is used only for Workstation, not Server.
Yes I changed the port number because the installer claimed 902 was in use. I can connect and query the server now but I am seeing different problems as described in the othe other posts in this... See more...
Yes I changed the port number because the installer claimed 902 was in use. I can connect and query the server now but I am seeing different problems as described in the othe other posts in this thread.
This code still fails in the sense that It can't list out all the running machines. it dies in the middle of quering the server with a segfault. have you seen this behavior before? Thanks
Did you change the port number when you installed VMware Server? The default port that it listens on is 902, but you are trying to connect on port 904. When you try to establish a remote conn... See more...
Did you change the port number when you installed VMware Server? The default port that it listens on is 902, but you are trying to connect on port 904. When you try to establish a remote connection to a port that is not listening, the VixJob_Wait for that connect job will wait indefinitely. You can also use VixJob_CheckCompletion to check if the call has succeeded without blocking.
My Question now is how can I get the vix bindings for perl to compile against 32bit libraries? Thanks
Hi, I found a solution, one must pass -m32 flag to the compiler to be able to link against the 32bit versions of the libraries. The ws-2 64bit version don't work on vmwar-server up to 1.0.3. Thi... See more...
Hi, I found a solution, one must pass -m32 flag to the compiler to be able to link against the 32bit versions of the libraries. The ws-2 64bit version don't work on vmwar-server up to 1.0.3. This is what I used to complie code that worked. gcc -m32 -o hostconnect hostconnect.c -I/usr/include/vmware-vix /usr/lib/libvmware-vix.so.0.0.0 The only thing is I get a segmentation fault at the end. much like what I am used to seeing from vmrun up to VMware server 1.0.2. Any hints what I can do to fix that?
OS: OpenSUSE 10.2 x86_64 VMware Product: VMware server VMware Product version: VMware-server-1.0.3-44356 Vix version: VMware-vix-1.0.3-44356.tar.gz let me know if there is anything else to ... See more...
OS: OpenSUSE 10.2 x86_64 VMware Product: VMware server VMware Product version: VMware-server-1.0.3-44356 Vix version: VMware-vix-1.0.3-44356.tar.gz let me know if there is anything else to help file a bug on this or find a way to get it to work
Can you give more version and product details? Your code is trying to talk to VMWare server, but the latest Vix is for Workstation. Which are you using?
Hi, I am using the latest release of the vix api and I am not getting anywhere from C or from perl. I tried this on both 32 and 64 bit linux hosts and it seems like Vix_JobWait hangs forever. Th... See more...
Hi, I am using the latest release of the vix api and I am not getting anywhere from C or from perl. I tried this on both 32 and 64 bit linux hosts and it seems like Vix_JobWait hangs forever. The example in the docs that passes NULL for hostname, username and password also need to be corrected since they result in a segfault as it seems that some code tries to do strlen on these params. below is my code, which is pretty much out of the examples. I appreciate any tips : int main() { VixError err; // Connect to specified host. jobHandle = VixHost_Connect(VIX_API_VERSION, VIX_SERVICEPROVIDER_VMWARE_SERVER, "mymachine.com", // hostName 904, // hostPort "root", // userName "password", // password, 0, // options VIX_INVALID_HANDLE, // propertyListHandle NULL, // callbackProc NULL); // clientData err = VixJob_Wait(jobHandle, VIX_PROPERTY_JOB_RESULT_HANDLE, &hostHandle, VIX_PROPERTY_NONE); if (VIX_OK != err) { // Handle the error... goto abort; } Vix_ReleaseHandle(jobHandle); printf("\nLooking for running virtual machines"); jobHandle = VixHost_FindItems(hostHandle, VIX_FIND_RUNNING_VMS, VIX_INVALID_HANDLE, // searchCriteria -1, // timeout VixDiscoveryProc, NULL); VixJob_Wait(jobHandle, VIX_PROPERTY_NONE); abort: Vix_ReleaseHandle(jobHandle); VixHost_Disconnect(hostHandle); }
You can't depend on environment variables being set when doing a RunProgramInGuest, and it appears that cmd.exe returns the literal string if the env var isn't valid.
I was wondering why certain environment variables aren't getting set. One environment variable I need is %USERNAME%. When I have remotely turn on cmd.exe, and I issue the command: ec... See more...
I was wondering why certain environment variables aren't getting set. One environment variable I need is %USERNAME%. When I have remotely turn on cmd.exe, and I issue the command: echo %USERNAME% it returns "%USERNAME% When I open a new instance of cmd.exe, from the start menu and type in the same command. I get "hbobuild" which was the username I used in the previous step of LoginGuest. Anybody know why this is happening?
There's nothing obivously wrong here. But I have a suggestion and some questions: \- first, it may be crashing in the VixJob_Wait(), since the printf() may not be flushing -- can you tweak th... See more...
There's nothing obivously wrong here. But I have a suggestion and some questions: \- first, it may be crashing in the VixJob_Wait(), since the printf() may not be flushing -- can you tweak the code to be sure its flushing? \- where does the debugger say the crash is? \- what version of VMware server (and Vix) are you using? \- I don't know anything about Dev-C++ -- is there a chance its got any incompatibilities with MS VC 2003 libraries?
Another option is, you could use a tcpmon between the client and the server (VC or ESX) and chk out the SOAP XML - the reason will be much clearer for the crash.
Are you trying to connect to the VirtualCenter running on your system? the connection parameter "localhost" implies that..isn't it?
Hi from Austria, When i want to run the following code : #include <string.h> #include "vix.h" VixHandle hostHandle = VIX_INVALID_HANDLE; int main() { VixError err; VixHandle job... See more...
Hi from Austria, When i want to run the following code : #include <string.h> #include "vix.h" VixHandle hostHandle = VIX_INVALID_HANDLE; int main() { VixError err; VixHandle jobHandle = VIX_INVALID_HANDLE; VixHandle vmHandle = VIX_INVALID_HANDLE; printf("before"); jobHandle = VixHost_Connect(VIX_API_VERSION, VIX_SERVICEPROVIDER_VMWARE_SERVER, "localhost", // *hostName, 902, // hostPort, "localadmin", // *userName, "thepassword", // *password, 0, // options, VIX_INVALID_HANDLE, // propertyListHandle, NULL, // *callbackProc, NULL); // *clientData); printf("after"); err = VixJob_Wait(jobHandle, VIX_PROPERTY_JOB_RESULT_HANDLE, &hostHandle, VIX_PROPERTY_NONE); if (VIX_OK != err) { goto abort; } } the code does compiles, but during the runtime the program doesn't come to print "after". There is an error thrown at runtime, which looks like this http://666kb.com/i/am63ukv2oljdavh6v.jpg Excuse for the german language, but the bold text says: asdf.exe has made a problem, and it has to be closed. under it stands the stereotyp message from windows, which says that if the program has not been saved, some data will be lost. the buttons : debug and the other: close my operation system is : win XP profession serivce pack 2 and the vm server works as it should work. please help me because i don't know what to do to solve the problem. thank you