r"""###########""" r"""#" Update r"""###########"""
Actually, as I pointed out to Marc's comment below... maybe check out Vagrant - http://vagrantup.com/ as vmware-server is always going to need it's kernel modules recompiled on every kernel upgrade, which is going to be a pain..
VMWare Server install errors
Errors on install of vmware server 2.0.2 on ubuntu 10.04.2 32-bit with either kernel: 2.6.32-28 or 2.6.32-32
/usr/local/vmware-server/vmware-server-distrib/lib/modules/source/vmnet-only/filter.c:1089: error: âfilterIoctlSemâ undeclared (first use in this function) /usr/local/vmware-server/vmware-server-distrib/lib/modules/source/vmnet-only/filter.c:1089: error: (Each undeclared identifier is reported only once /usr/local/vmware-server/vmware-server-distrib/lib/modules/source/vmnet-only/filter.c:1089: error: for each function it appears in.) make: *** [/usr/local/vmware-server/vmware-server-distrib/lib/modules/source/vmnet-only/filter.o] Error 1 make: *** [_module_/usr/local/vmware-server/vmware-server-distrib/lib/modules/source/vmnet-only] Error 2 make: *** [vmnet.ko] Error 2 # There is a problem compiling the vmnet module after it was patched. :(
If you spend the better part of a day blending up various kernels, forum posts and patching methodologies, you get here.
Do not ask me why this mashup below works. It is possible that release-1.5 and its script will work and that mine did not work because of previous steps carried out trying all and sundry forum post suggestions and my autoconf.h and utsrelease.h were foobar.
But FIRST try:
apt-get --reinstall install linux-headers-`uname -r`
- And use release-1.5 and instructions as per http://radu.cotescu.com/how-to-install-vmware-server-2-0-x-on-ubuntu-9-10-karmic-koala/
NOT release-1.6 (latest) but https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/tarball/release-1.5
If that does not work... here is a mashup that did for me.
DO NOT use the latest patch release, use release-1.5 and DO NOT use the vmware-server-2.0.x-kernel-2.6.3x-install.sh INSTALL script.
PATCH IN PLACE!!!.
apt-get -y linux-headers-`uname -r` build-essential bzip2 gcc-4.4
If you have followed some of the forum suggestions, etc you may need to:
apt-get --reinstall install linux-headers-`uname -r`
DOWNLOAD VMWARE SERVER and PATCH ARCHIVES IN THE SAME DIRECTORY
IN THE SAME DIRECTORY
- Download VMware Server 2.0.2 IN gz format, NOT rpm.
- Download @raducotescu vmware-server-linux-2.6.3x-kernel release-1.5 - https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/tarball/release-1.5
DLHOME=/your/download/path cd $DLHOME tar zxvf raducotescu-vmware-server-linux-2.6.3x-kernel-release-1.6-0-<GIT_ID>.tar.gz mkdir -p /usr/local/vmware-server mv raducotescu-vmware-server-linux-2.6.3x-kernel-84fa8c2 /usr/local/vmware-server ln -s $DLHOME/VMware-server-2.0.2-203138.i386.tar.gz /usr/local/vmware-server/VMware-server-2.0.2-203138.i386.tar.gz cd /usr/local/vmware-server tar xvzf VMware-server-2.0.2-203138.i386.tar.gz cd /usr/local/vmware-server/vmware-server-distrib ./vmware-install.pl #### # DO NOT!!! # # Do not start the vmware-config.pl ! If the setup asks you: # # Before running VMware Server for the first time, you need to configure it by # invoking the following command: "/usr/bin/vmware-config.pl". Do you want this: # THE ANSWER IS: no # credit to @linuxconfig # # GO THROUGH THE INSTALL STEPS AND QUESTIONS # # # I installed all to /usr/local/vmware-server/, but most will want to use default paths. So... # $YOUR_BIN_DIR = the directory you specified during the setup the default was [/usr/bin] # $YOUR_LIB_DIR = the directory you specified during the setup the default was [/lib/vmware/modules/source] # # Patch config cd $YOUR_BIN_DIR patch -p3 < /usr/local/vmware-server/vmware-config.patch # # Patch modules cd $YOUR_LIB_DIR for f in *.tar ; do tar pxf $f ; done patch -p4 < /usr/local/vmware-server/vmware-server-2.0.2-203138-update.patch for f in vmci vmmon vmnet vsock ; do tar pcf $f.tar $f-only ; done rm -fr *-only # cd $YOUR_BIN_DIR ./vmware-config.pl # # Go through the rest of the configuration. # Worked for me.
Credits and references go to:
Submitted by Anonymous on Sun, 10/30/2011 - 19:04.
Just wanted to say thanks for the script, I used it a couple of months back. On another server I set up last week, I used the solution discussed here: https://answers.launchpad.net/ubuntu/+source/linux-meta/+question/164913 (Small modification to a header file and the stock 1.6 script from radu). Just wanted to let anyone searching for a solution to install VMWare Server 2.0.2 on Ubuntu 10.04 LTS know that there is an even easier one than the one which was discussed above.
Submitted by Anonymous on Mon, 08/01/2011 - 02:20.
Could you direct me to the location of the patches? I've followed your directions up to that point with no issues, but don't know where to download the patches. Thanks! Mark
Submitted by Gary on Mon, 08/01/2011 - 06:48.
The patches are included in raducotescu release-1.5 tarball from github - https://github.com/raducotescu/vmware-server-linux-2.6.3x-kernel/tarball...
So. Install VMServer and THEN patch with the raducotescu release-1.5 patch. If you have downloaded and unpacked the VMServer and raducotescu to the same directory the patch will is "vmware-config.patch" in the directory that you unpacked the release-1.5 tarball in.
Perhaps this may help you find it:
cd / find ./ -name "vmware-config.patch" -print
That did it!
Submitted by Anonymous on Mon, 08/01/2011 - 22:42.
Thanks for the help. Now I just need to figure out how to use it and set up a VM. :-)
Small Bug in CMDLINE_SCRIPT
Submitted by Anonymous on Sat, 07/02/2011 - 09:42.
thanks. After hours, this page has the final solution for Ubuntu 10.04 LTS 2.6.32-32-server.
But in the script at line 3 you wrote: tar zxvf raducotescu-vmware-server-linux-2.6.3x-kernel-release-1.6-0-gbb26dce.tar.gz
I think it has to be tar zxvf raducotescu-vmware-server-linux-2.6.3x-kernel-release-1.5-0-gd30493a.tar.gz
Best regards Marc
Submitted by Gary on Sat, 07/02/2011 - 19:46.
Thanks. That is a git assigned ID, I should added it as a variable. I have amended it to now to reflect this. I am glad to hear that it worked for you with just the one bug. It was cobbled together after trying many things unsuccessfully :) Once I got it working, I tried to tie all the things together that worked, so I am very glad that it is only the GIT_ID and everything worked OK. Thanks for the feedback.