Comments on: Installing VMware server 2.0.2 on Ubuntu 9.10 Karmic Koala 64bit

By: Craig Mayhew

Craig Mayhew — Sat, 27 Mar 2010 22:19:10 +0000

Another great resource for debugging VMWare Server issues: https://help.ubuntu.com/community/VMware/Server

By: Ian Justman

Ian Justman — Fri, 19 Feb 2010 17:53:29 +0000

I found something that allows vsock to be built; it involves patching the vmware-config.pl file. There’s a patch attached to this post on a thread on the very subject:

http://ubuntuforums.org/showpost.php?p=6267637&postcount=17

Worked just fine here once I applied your patch and this one.

–Ian.

By: Craig Mayhew

Craig Mayhew — Wed, 17 Feb 2010 09:31:32 +0000

@macke I’ve fixed that, I had an error with the downloads section.

By: Ian Justman

Ian Justman — Mon, 15 Feb 2010 05:21:44 +0000

This procedure does NOT work with my install of Ubuntu 9.10 x86-64. The kernel in use is 2.6.31-19 and I get the following at link-time:

LD [M] /tmp/vmware-config1/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: “VMCIDatagram_CreateHnd” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIDatagram_DestroyHnd” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCI_GetContextID” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIDatagram_Send” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
CC /tmp/vmware-config1/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config1/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.31-19-server’
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config1/vsock-only’
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting ‘/tmp/vmware-config1/vsock.o’: -1 Unknown symbol in module

By: macke

macke — Mon, 01 Feb 2010 13:58:37 +0000

Am I right when i think i need to download the patch before i am able to patch my vmware? Unfortunately there is no file appearing after i click the link. How can i find it again?

By: Craig Mayhew

Craig Mayhew — Sun, 03 Jan 2010 00:35:25 +0000

If you need to rerun vmware-config-tools and know you only want the default values then this command will make it much quicker by automatically using the defaults:

/usr/bin/vmware-config-tools.pl –default

By: Craig Mayhew

Craig Mayhew — Tue, 29 Dec 2009 15:55:54 +0000

@fixer Thanks for spotting that. I must have uploaded it from a windows machine (won’t make that mistake again!). I’ve now uploaded a corrected version of the patch.

By: cyqotiq

cyqotiq — Thu, 24 Dec 2009 05:34:17 +0000

You, sir, are a saint! I’ve been trying to find the fix for the 64-bit karmic kernel. The closest I came was finding the 2.6.30 patch, which failed miserably. This worked like a charm!

By: Sam

Sam — Wed, 16 Dec 2009 22:07:33 +0000

Thanks, worked fine.

Make sure you follow instructions to the letter or it will fail.

By: fixer

fixer — Wed, 09 Dec 2009 23:32:54 +0000

The “command not found” error is because of Microsoft end of line characters in the shell script. (How did that happen?) Anyway, if you try to run the shell script without sudo, you will see:

bash: ./vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh: /bin/sh^M: bad interpreter: No such file or directory

To fix the shell script, first run:
perl -pi -e ’s/\r\n/\n/;’ vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh