Segmentation Fault (core dumped) on VixHost_Connect

[mcroteau]

Hi Guys,

I'm got a ubuntu machine running VMWare Server 1.0.3 build 44356 and first off I'll admit I'm a bit new to this. This line was working on a previous version of VIX (I'm currently running 1.1) but now I can't find anywhere to download the old version from!

jobHandle = VixHost_Connect(VIX_API_VERSION,

VIX_SERVICEPROVIDER_VMWARE_SERVER,

NULL, // hostName

0, // hostPort

NULL, // userName

NULL, // password,

0, // options

VIX_INVALID_HANDLE, // propertyListHandle

NULL, // callbackProc

NULL); // clientData

Well, when the program runs to this line I get a segmentation fault(core dumped).

I've tried replacing the username & password with "user" "pass" to no avail.

Can anyone point me to a link where I can download an older version of VIX? The first post in this forum says to not use vix 1.1 on server but doesn't provide a link for an older version!

Thanks,

Matt

[zerovoid]

instead of VIX_API_VERSION[/b] in your connect string try putting 1[/b], that should solve your problem

The old version is included with the server install

[mcroteau]

Thanks for the quick response but that didn't solve it. Any other ideas?

Matt

[zerovoid]

Actually I think your problem may be the same problem I have compiling on Win32 with DevC++.

In VC++ it works but with minigw (Dev C++) all my Vix code crashes at the connect string.

http://www.vmware.com/community/thread.jspa?threadID=74194&tstart=0

[quotehttp://www.vmware.com/community/thread.jspa?threadID=74194&tstart=0

To quote lemke[/b]

Some of the issues are probably caused by using the 1.1

API with the 1.0 server. The constant VIX_API_VERSION has

been bumped, and server doesn't deal well with the '2'

from 1.1 instead of the '1' it expects. Passing in a '1'

might solve many of your problems.

However, that doesn't make a lot of sense that the

different compilers have different results, so the other

possibility is a C runt-time mismatch. The Vix library

expects a mutil-threaded, non-debug CRT. If you're letting

Visual Studio set up the project, it may be setting you to

use a debug CRT, and the threading model could also be

incorrect. Unfortunately, if you mix CRT versions, you

tend to get ugly crashes.

And errcode 6 is 'not supported'. This is probably because

you're trying to use the version 2 API with a version 1

back end.

If you're working with server 1.03, you can stay with the

Vix 1.0 that shipped with it.

[admin]

First, to address your immediate problem, how are you linking with the Vix API? Are you linking directly with one of the libvix.so files or are you using the libVixAllProducts.a?

In terms of going back to the 1.0 release, we are currently working on making the installer for the 1.0 release available again. For a quick(er) fix, you can try uninstalling the new version of Vix, and then reinstalling VMware Server.

[mcroteau]

Thanks Mattrich,

I uninstalled VIX 1.1.0, then uninstalled & reinstalled VMWare-Server 1.0.3 and my program worked just fine.

You guys might want to remove the link to 1.1.0 on your website or say it's ONLY for workstation.

Thanks for your quick replies, you guys are tops in my book.

Matt

[zerovoid]

Well VixCom is in 1.1, and I use that.