spanish version - all english posts
Howto make work wmware-server-2.0.2 in Ubuntu 10.04 LTS lucid lynx
I'm using lucid's beta for a month. Today I remembered that I had not yet tested vmware-server on 10.04 lucid; so we will see how to solve the problems that may appear.
Basically we will do the same we did for karmic:
- install vmware-server
- apply the ubuntugeek's patch
But since the kernel version in lucid is 2.6.32 to get the vmware modules compile we will need to...
manualy edit a couple of files:
vmnet-only/vnetUserListener.c vmci-only/linux/vmciKernelIf.c
Note: at the end of this post there is a remark about vmware-tools in Ubuntu lucid 10.04 LTS guests
Lets summarize the process step by step:
First of all we need a basic build environment to compile the vmware modules; with the following commands we will install all the programs we'll need and its dependencies:
~# aptitude update ~# aptitude -y install build-essential linux-headers-$(uname -r) psmisc
Untar the vmware-server tarball that you have already download from vmware's site:
~# tar xvf VMware-server-2.0.2-203138.i386.tar.gz
We proceed to perform the installation:
~# cd /tmp/vmware-server-distrib/ ~# ./vmware-install.pl
When the process arrives to the modules compilation step, we see the same error that happens in all the last ubuntu releases:
None of the pre-built vmmon modules for VMware Server is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.32-21-generic/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config1/vmmon-only' make -C /lib/modules/2.6.32-21-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-headers-2.6.32-21-generic' CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o In file included from /tmp/vmware-config1/vmmon-only/linux/driver.c:31: /tmp/vmware-config1/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait' include/linux/poll.h:70: note: previous declaration of 'poll_initwait' was here In file included from /tmp/vmware-config1/vmmon-only/./include/vmware.h:38, from /tmp/vmware-config1/vmmon-only/linux/driver.c:99: /tmp/vmware-config1/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined In file included from /tmp/vmware-config1/vmmon-only/./common/vmx86.h:32, from /tmp/vmware-config1/vmmon-only/linux/driver.h:29, from /tmp/vmware-config1/vmmon-only/linux/driver.c:101: /tmp/vmware-config1/vmmon-only/./include/x86msr.h:164:1: warning: "MSR_THERM2_CTL" redefined In file included from /usr/src/linux-headers-2.6.32-21-generic/arch/x86/include/asm/msr.h:4, from /usr/src/linux-headers-2.6.32-21-generic/arch/x86/include/asm/processor.h:21, from include/linux/prefetch.h:14, from include/linux/list.h:6, from include/linux/module.h:9, from /tmp/vmware-config1/vmmon-only/./include/compat_module.h:27, from /tmp/vmware-config1/vmmon-only/linux/driver.c:26: /usr/src/linux-headers-2.6.32-21-generic/arch/x86/include/asm/msr-index.h:227:1: warning: this is the location of the previous definition In file included from /tmp/vmware-config1/vmmon-only/./include/vcpuset.h:103, from /tmp/vmware-config1/vmmon-only/./include/modulecall.h:37, from /tmp/vmware-config1/vmmon-only/./common/vmx86.h:33, from /tmp/vmware-config1/vmmon-only/linux/driver.h:29, from /tmp/vmware-config1/vmmon-only/linux/driver.c:101: /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config1/vmmon-only/./include/vm_basic_asm.h:46, from /tmp/vmware-config1/vmmon-only/./include/rateconv.h:45, from /tmp/vmware-config1/vmmon-only/./include/modulecall.h:40, from /tmp/vmware-config1/vmmon-only/./common/vmx86.h:33, from /tmp/vmware-config1/vmmon-only/linux/driver.h:29, from /tmp/vmware-config1/vmmon-only/linux/driver.c:101: /tmp/vmware-config1/vmmon-only/./include/vm_basic_asm_x86.h:62:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_basic_asm_x86.h:177:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_basic_asm_x86.h:346:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_basic_asm_x86.h:453:7: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config1/vmmon-only/./include/vm_asm.h:43, from /tmp/vmware-config1/vmmon-only/linux/driver.c:103: /tmp/vmware-config1/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined /tmp/vmware-config1/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config1/vmmon-only/linux/driver.c:119: /tmp/vmware-config1/vmmon-only/./common/hostif.h:53:7: warning: "WINNT_DDK" is not defined /tmp/vmware-config1/vmmon-only/linux/driver.c: In function 'LinuxDriverSyncCallOnEachCPU': /tmp/vmware-config1/vmmon-only/linux/driver.c:1423: error: too many arguments to function 'smp_call_function' /tmp/vmware-config1/vmmon-only/linux/driver.c: In function 'LinuxDriver_Ioctl': /tmp/vmware-config1/vmmon-only/linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid' /tmp/vmware-config1/vmmon-only/linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid' /tmp/vmware-config1/vmmon-only/linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid' /tmp/vmware-config1/vmmon-only/linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid' /tmp/vmware-config1/vmmon-only/linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid' /tmp/vmware-config1/vmmon-only/linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid' /tmp/vmware-config1/vmmon-only/linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid' /tmp/vmware-config1/vmmon-only/linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid' /tmp/vmware-config1/vmmon-only/linux/driver.c:2007: error: too many arguments to function 'smp_call_function' make[2]: *** [/tmp/vmware-config1/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config1/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-21-generic' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config1/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/go/unsup-linux-products" and "http://www.vmware.com/go/unsup-linux-tools". Execution aborted.
Hmm, this sounds familiar; so hands-on. Download and install the ubuntugeek's patches:
~# wget -O - http://www.ubuntugeek.com/images/vmware-server.2.0.1_x64-modules-2.6.30.4-fix.tgz | tar xvfz - ~# ./vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh
But surprise, it ends up with errors:
[...] /usr/lib/vmware/modules/source/vmnet-only/vm_basic_asm_x86.h:62:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_basic_asm_x86.h:177:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_basic_asm_x86.h:346:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_basic_asm_x86.h:453:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c: In function ‘VNetUserListenerEventHandler’: /usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:240: error: ‘TASK_INTERRUPTIBLE’ undeclared (first use in this function) /usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:240: error: (Each undeclared identifier is reported only once /usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:240: error: for each function it appears in.) /usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c: In function ‘VNetUserListenerRead’: /usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:282: error: ‘TASK_INTERRUPTIBLE’ undeclared (first use in this function) /usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:282: error: implicit declaration of function ‘signal_pending’ /usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:282: error: implicit declaration of function ‘schedule’ make[2]: *** [/usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.o] Error 1 make[1]: *** [_module_/usr/lib/vmware/modules/source/vmnet-only] Error 2 make[1]: se sale del directorio `/usr/src/linux-headers-2.6.32-21-generic' make: *** [vmnet.ko] Error 2 Sorry, problem compiling the vmnet module after it was patched You must restore from this backup directory: /usr/lib/vmware/modules/source-backup
Do not give up! Let's look for more information...
According to Noel at vmware communities we need to patch the following files:
vmnet-only/vnetUserListener.c vmci-only/linux/vmciKernelIf.c
adding a «#include "compat_sched.h"» in each of them.
First of all lets restore the sources that we wrapped in our first attempt:
~# cd /usr/lib/vmware/modules ~# rm -r source ~# mv source-backup source
now modify the files the following way (I could have redo the ubuntugeek's patch adding these little modifications, but it's more work); so lets KISS.
First vnetUserListener.c:
~# cd source/ ~# tar xvf vmnet.tar ~# vim vmnet-only/vnetUserListener.c
Among the #includes in that file add «#include "compat_sched.h"»; once done, re-pack the tar:
~# tar cvf vmnet.tar vmnet-only ~# rm -r vmnet-only
Now do the same with vmciKernelIf.c:
~# tar xvf vmci.tar ~# vim vmci-only/linux/vmciKernelIf.c
We again will add an «#include "compat_sched.h"» among the other includes. Finally re-pack the tar file:
~# tar cvf vmci.tar vmci-only/ ~# rm -r vmci-only
After those little changes, run again the ubuntugeek's patch:
~# cd /tmp/ ~# ./vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh [...] /usr/lib/vmware/modules/source/vmnet-only/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined In file included from /usr/lib/vmware/modules/source/vmnet-only/vm_basic_asm.h:46, from /usr/lib/vmware/modules/source/vmnet-only/vm_oui.h:28, from /usr/lib/vmware/modules/source/vmnet-only/vnetInt.h:25, from /usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:36: /usr/lib/vmware/modules/source/vmnet-only/vm_basic_asm_x86.h:62:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_basic_asm_x86.h:177:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_basic_asm_x86.h:346:7: warning: "_MSC_VER" is not defined /usr/lib/vmware/modules/source/vmnet-only/vm_basic_asm_x86.h:453:7: warning: "_MSC_VER" is not defined LD [M] /usr/lib/vmware/modules/source/vmnet-only/vmnet.o Building modules, stage 2. MODPOST 1 modules CC /usr/lib/vmware/modules/source/vmnet-only/vmnet.mod.o LD [M] /usr/lib/vmware/modules/source/vmnet-only/vmnet.ko make[1]: se sale del directorio `/usr/src/linux-headers-2.6.32-21-generic' cp -f vmnet.ko ./../vmnet.o Replacing original file vsock.tar with patched file Replacing original file vmci.tar with patched file Replacing original file vmmon.tar with patched file Replacing original file vmnet.tar with patched file Done! I have changed the files in here: /usr/lib/vmware/modules/source I have placed a backup of the original files in here: /usr/lib/vmware/modules/source-backup The original VMware modules directory is still in the way. Please move this directory somewhere else, because it confuses VMware: /usr/lib/vmware/modules/binary This command should work now, to install the modules: vmware-config.pl -d
We are almost done!
Install the modules (notice the '-d' flag; don't use it if you need to define non default settings or accept the license):
~# /usr/bin/vmware-config.pl -d [...] The installation of VMware VIX API 1.6.2 build-203138 for Linux completed successfully. You can decide to remove this software from your system at any time by invoking the following command: "/usr/bin/vmware-uninstall-vix.pl". Enjoy, --the VMware team Starting VMware services: Virtual machine monitor done Virtual machine communication interface done Virtual ethernet done Bridged networking on /dev/vmnet0 done Host-only networking on /dev/vmnet1 (background) done DHCP server on /dev/vmnet1 done Host-only networking on /dev/vmnet8 (background) done DHCP server on /dev/vmnet8 done NAT service on /dev/vmnet8 done VMware Server Authentication Daemon (background) done Shared Memory Available done Starting VMware management services: VMware Server Host Agent (background) done VMware Virtual Infrastructure Web Access Starting VMware autostart virtual machines: Virtual machines done The configuration of VMware Server 2.0.2 build-203138 for Linux for this running kernel completed successfully.
Finally we have our new vmware 2.0.2 server working in our brand new Ubuntu Lucid Lynx 10.04
vmware-tools for ubuntu 10.04 guestsAnd what about vmware-tools in ubuntu 10.04 guests?
This issue may deserve it's own post, but as many of you will face this problem sooner or later; I've added this note about it at the end of this post.
I've tried to install the native vmware-tools in ubuntu 10.04 guests with no succeed.
Do not waste your time on it. There is a big lag between vmware and the new kernels
Instead of the vmware native tools install the opensource version in your guests as follows:
~# apt-get update ~# apt-get install --no-install-recommends open-vm-tools open-vm-dkms
The --no-install-recommends is to avoid the installation of X11 related packages as most of my gests have no gui.
So if your guest is a desktop leave off that flag and run:
~# apt-get update ~# apt-get install open-vm-tools open-vm-dkms
You'll see that with the opensource tools, you'll get most, if not all, the functionality you should have had with the native vmware-tools.
Thanks for the post!
ReplyDeleteIt would be create if you could create and publish the new patch to KISS :-)
w00t! Thank you so much. I was not looking forward to figuring this out on my own :)
ReplyDeleteWorked for 32 bit 10.4 fresh Lucid install - HOWEVER - I had to run the /usr/bin/vmware-config.pl without the "-d" - otherwise it skipped through questions I needed to answer.
excellent walk-though
ReplyDeleteI hate to repeat, but it will... This was an EXCELLENT walkthrough! Perfect. Command-for-Command.
ReplyDeleteThanks!
Thanks for the detailed walkthrough .. worked perfectly and saved lot of time. :)
ReplyDeleteI'm with lionstone. Leave off the "-d", so you can enter the license key.
ReplyDeleteThat was excellent. Thank you very much for the detailed walk-through with all the necessary commands. I was afraid I was going to have to look up the proper parameters to tar up the files.
ReplyDeleteThanks all for your nice comments!
ReplyDeleteAbout the '-d' flag, I've added a comment in the post.
This doesn't work for me :(
ReplyDeletei get this
vmware-server.2.0.1_x64-modules-2.6.30.4-fix.patch
Using module directory: /usr/lib/vmware/modules/source
Using backup directory: /usr/lib/vmware/modules/source-backup
Backing up ./vsock-temp.tar to /usr/lib/vmware/modules/source-backup/./vsock-temp.tar
Backing up ./vsock.tar to /usr/lib/vmware/modules/source-backup/./vsock.tar
Backing up ./vmnet.tar to /usr/lib/vmware/modules/source-backup/./vmnet.tar
Backing up ./vmci-temp.tar to /usr/lib/vmware/modules/source-backup/./vmci-temp.tar
Backing up ./vmmon-temp.tar to /usr/lib/vmware/modules/source-backup/./vmmon-temp.tar
Backing up ./vmnet-temp.tar to /usr/lib/vmware/modules/source-backup/./vmnet-temp.tar
Backing up ./vmmon.tar to /usr/lib/vmware/modules/source-backup/./vmmon.tar
Backing up ./vmci.tar to /usr/lib/vmware/modules/source-backup/./vmci.tar
Untarring vsock-temp.tar
Sorry, vsock-temp.tar tarball failed to extract the directory vsock-temp-only
nadia@nadell:~$ sudo ./vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh
Found tar file for vsock-temp module
Found tar file for vsock module
Found tar file for vmnet module
Found tar file for vmci-temp module
Found tar file for vmmon-temp module
Found tar file for vmnet-temp module
Found tar file for vmmon module
Found tar file for vmci module
Using patch file: /home/nadia/vmware-server.2.0.1_x64-modules-2.6.30.4-fix.patch
Using module directory: /usr/lib/vmware/modules/source
Using backup directory: /usr/lib/vmware/modules/source-backup
Untarring vsock-temp.tar
Sorry, vsock-temp.tar tarball failed to extract the directory vsock-temp-only
I am running 64 bits kubuntu 10.04, and i get the same errors running the ubuntugeek's scrips after changing the mentioned files... Please help, thank you
ReplyDeleteany reason you're not running 64-bit? I think everyone else has switched.
ReplyDeleteJust wanted to add this does not work on Ubuntu Lucide ... when running the 2.0.1 patch script, after patching the files, I get the following error:
ReplyDeleteSorry, vmnet-temp.tar tarball failed to extract the directory vmnet-temp-only
At step "After those little changes, run again the ubuntugeek's patch:"
ReplyDeletei got this error:
Found tar file for vmnet-temp module
Found tar file for vsock module
Found tar file for vmmon module
Found tar file for vsock-temp module
Found tar file for vmnet module
Found tar file for vmmon-temp module
Found tar file for vmci-temp module
Found tar file for vmci module
Using patch file: /home/steven/Downloads/software/vmware-server.2.0.1_x64-modules-2.6.30.4-fix.patch
Using module directory: /usr/bin/lib/vmware/modules/source
Using backup directory: /usr/bin/lib/vmware/modules/source-backup
Untarring vmnet-temp.tar
Sorry, vmnet-temp.tar tarball failed to extract the directory vmnet-temp-only
Please help me.......
I have followed your steps and get the following error while running the vmware-config.pl command
ReplyDelete++++++++++++++++++++++++++++++++++++++++++
/tmp/vmware-config3/vmnet-only/vm_basic_asm_x86.h:346:7: warning: "_MSC_VER" is not defined
/tmp/vmware-config3/vmnet-only/vm_basic_asm_x86.h:453:7: warning: "_MSC_VER" is not defined
LD [M] /tmp/vmware-config3/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config3/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config3/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-21-generic'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config3/vmnet-only'
This program previously created the file
/lib/modules/2.6.32-21-generic/misc/vmnet.o, and was about to remove it.
Somebody else apparently did it already.
This program previously created the file
/lib/modules/2.6.32-21-generic/misc/vmnet.ko, and was about to remove it.
Somebody else apparently did it already.
The vmnet module loads perfectly into the running kernel.
Please specify a port for remote connections to use [902]
Using Existing SSL Certificate.
You have a pre-existing config.xml. The new version will be created as
/etc/vmware/hostd/NEW_config.xml. Please check the new file for any new values
that you may need to migrate to your current config.xml.
Do you want to use the current proxy port values? [yes]
Use of uninitialized value $property_file in concatenation (.) or string at /usr/bin/vmware-config.pl line 8629.
There is no ! This file is necessary for the operation of the webAccess
service.
Execution aborted.
++++++++++++++++++++++++++++++++++++++++++
Any help would be appreciated.
Thanks. Just wanted to note that during the modification process you outline, I had to also add the #include "compat_sched.h" to the file vmci-only/include/pgtbl.h . This saved me from a compile error on line 301: "error: dereferencing pointer to incomplete type"
ReplyDelete(server 2.0.2 on Lucid x86_64)
funciona! excelente. quedaría por ver el tema de la licencia.
ReplyDeleteThanks but I get the same error as Steven, Cassey and Nadia....
ReplyDeleteThis is my output
root@uue-linuxadmin:/home/linuxadmin/Downloads# ./vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh
Found tar file for vmci-temp module
Found tar file for vsock module
Found tar file for vmmon module
Found tar file for vmmon-temp module
Found tar file for vmnet module
Found tar file for vmci module
Found tar file for vsock-temp module
Found tar file for vmnet-temp module
Using patch file: /home/linuxadmin/Downloads/vmware-server.2.0.1_x64-modules-2.6.30.4-fix.patch
Using module directory: /usr/lib/vmware/modules/source
Using backup directory: /usr/lib/vmware/modules/source-backup
Backing up ./vmci-temp.tar to /usr/lib/vmware/modules/source-backup/./vmci-temp.tar
Backing up ./vsock.tar to /usr/lib/vmware/modules/source-backup/./vsock.tar
Backing up ./vmmon.tar to /usr/lib/vmware/modules/source-backup/./vmmon.tar
Backing up ./vmmon-temp.tar to /usr/lib/vmware/modules/source-backup/./vmmon-temp.tar
Backing up ./vmnet.tar to /usr/lib/vmware/modules/source-backup/./vmnet.tar
Backing up ./vmci.tar to /usr/lib/vmware/modules/source-backup/./vmci.tar
Backing up ./vsock-temp.tar to /usr/lib/vmware/modules/source-backup/./vsock-temp.tar
Backing up ./vmnet-temp.tar to /usr/lib/vmware/modules/source-backup/./vmnet-temp.tar
Untarring vmci-temp.tar
Sorry, vmci-temp.tar tarball failed to extract the directory vmci-temp-only
root@uue-linuxadmin:/home/linuxadmin/Downloads#
Thanks
For those of you with problems related to extract the vmci-temp.tar tarball, I'd just suggest you to check:
ReplyDeleteHave you followed all the steps in this howto?
Is tar installed? (on most if not all the systems it should be)
Is your destination partition/disk full?
Are you root?
Do you have permissions to write in the destination dir?
As I haven't had this issue these are the only hints I'm able to give you.
Maybe it is an issue with the 64bits files... I don't know.
Bryan thanks a lot! your post (#include "compat_sched.h" to the file vmci-only/include/pgtbl.h) was helpful
ReplyDeletesaved from error:
/usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c: In function �VNetUserListenerEventHandler’:
/usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:240: error: �TASK_INTERRUPTIBLE’ undeclared (first use in this function)
/usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:240: error: (Each undeclared identifier is reported only once
/usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:240: error: for each function it appears in.)
/usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c: In function �VNetUserListenerRead’:
/usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:282: error: �TASK_INTERRUPTIBLE’ undeclared (first use in this function)
/usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:282: error: implicit declaration of function �signal_pending’
/usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.c:282: error: implicit declaration of function �schedule’
make[2]: *** [/usr/lib/vmware/modules/source/vmnet-only/vnetUserListener.o] Ошибка 1
make[1]: *** [_module_/usr/lib/vmware/modules/source/vmnet-only] Ошибка 2
make[1]: Выход из каталога `/usr/src/linux-headers-2.6.32-22-generic'
make: *** [vmnet.ko] Ошибка 2
Sorry, problem compiling the vmnet module after it was patched
You must restore from this backup directory:
/usr/lib/vmware/modules/source-backup
Thanks man I managed to get it running.
ReplyDeleteHowever does anyone else have a loading error on https port 8333? It seems somehow javascript objects will not load properly in the browser, although I have no idea why. the certificate is accepted and the browser is open to javascript, no proxies.
Anything to do with compiling the modules?
debi,
ReplyDeleteThis is a known issue with firefox 3.6.
You can see a deeper answer in the spanish version of this post.
As a quick reply:
In order to fix the error I presume you have, you need to change the value "security.enable_ssl2" to "True" in "about:config" in ff3.6
However, even if you fix that problem, you'll notice that you wont be able to run the vmware-plugin in firefox 3.6; so you wont be able to access your VMs consoles.
So you either need to enable the vnc sessions of your vmware virtual machines editing their vmx files, or easier, download and use a firefox 3.5 just for accessing your VMs consoles and 3.6 for surfing the www (the later is what I do).
Excellent post - worked for me using a Lenovo Thinkpad W500 ( 4061-BL5 ) running a freshly installed version of Lucid, with the 2.6.32-22-generic 64-bit kernel.
ReplyDeleteHave blogged it here: -
http://portal2portal.blogspot.com/2010/05/lenovo-thinkpad-w500-my-first-few-hours.html
GREAT !!
ReplyDeleteI've enjoyed to read and apply this detailed (and even working ;) ) article very much! Thank you for this great article!
I have one suggestion: The script out of the ubuntugeek's patch expects all the stuff in /usr/lib . It could be worth a line to tell people to modify the line with the path. I for example installed everythind to /usr/local to not interrupt the package-manager.
thank you,
ReplyDeleteEXCELLENT
to adeola0405 , Steven Kuok and Nadia
ReplyDeleteIf you remove the directory "/usr/lib/vmware", and start over you will have sucess.
this is because you already tried and ther scripts criated the xxx-temp.tar files.
just great
ReplyDeleteWorked for me. Thank you very much. I was looking a solution for a few days. I never had such problems with ubuntu 9.10. Once again... Your the man :)
ReplyDeleteThank you! Thank you! Thank you! I tried installing VMWare 1.0.x and followed instructions for recompiling the kernel. When I completed the process and rebooted I received a kernel panic and had to do a fresh install of Ubuntu. That was my try with 1.0.x. I followed your instructions with low expectations for v.2.0.2 and was amazed that when the installation completed, I was able to install a new VM! Excellent, I take my hat to you!!!!!!
ReplyDeleteOnce I get to this part I can't seem to go any further.
ReplyDeleteFirst vnetUserListener.c:
~# cd source/
~# tar xvf vmnet.tar
~# vim vmnet-only/vnetUserListener.c
Among the #includes in that file add «#include "compat_sched.h"»; once done, re-pack the tar:
I was able to add the #include to the file but can't for the life of me figure out how to exit once it is added. I tried opening another terminal but when I try to go on to the next steps I am told 'no such file or directory'
I still have the first terminal open to the source file. Now I have this message at the bottom of the file.
E211: File "vmnet-only/vnetUserListener.c" no longer available
what to do???
vmware server 2.0.2 and ubuntu 10.04 server 64 bit + updates
ReplyDeleteafter install weg gui is not responded
This works great! Thank you!! BUT the web management interface is a desaster: After installation of the vm-ware server it works great - ca. 2-3 days. Then a connection isnt possible any more?! I tried every hint and trick - the only working solution is to uninstall vmware server, delete all config files, and reinstall again. Now I have another 3 days... (I tried several browsers and several connection types. Its all the same?!) Anybody an idea?
ReplyDeletextr said...
ReplyDelete> This works great! Thank you!! BUT the web management interface is a desaster:
> After installation of the vm-ware server it works great - ca. 2-3 days. Then
> a connection isnt possible any more?! I tried every hint and trick - the only
> working solution is to uninstall vmware server, delete all config files, and
> reinstall again. Now I have another 3 days... (I tried several browsers and
> several connection types. Its all the same?!) Anybody an idea?
Hi xtr,
I've never experienced that problem. The uptime of my vmware servers is measured in months.
However the webgui hangs from time to time. In that case you'll have to restart /etc/init.d/vmware-mgmt. That wont affect your vmware virtual machines which will keep running.
In case the restart of vmware-mgmt hangs in "stoping vmware-hostd" you'll just need to kill the hostd process and run again "/etc/init.d/vmware-mgmt restart".
HTH
Excellent guide!
ReplyDeleteWorking like a charm with 5 hosted linux machines on an old athlon 2ghz with ubuntu 10.04 as host OS.
thank you very much!
L
Thanks, this was so helpful. You saved my behind. I was having these exact same issues after I upgraded from 9.10 to 10.04, I was so disappointed that my VMWare installation broke. Now, it works again, thanks to your helpful guide!
ReplyDeleteHi, thank you for the guide--it worked great!
ReplyDeleteProcedure works for me (VMware-server-2.0.1-156745.i386 and Ubuntu 10.04 kernel 2.6.32-21-generic-pae IF additionaly
ReplyDeletespaces are removed between #-sign and "define COMPAT_SCHED" in the compat_sched.h files both in vmnet-only and vmci-only/include directory.
Thanks for all the postings! Nice job done !
Thanks to every one, and a special thanks to Alf who told to delete the directory "/usr/lib/vmware", and start over you will have sucess.
ReplyDeleteDoes it work for 64bit version as well? It didn't work for me (yet).
ReplyDeleteAkos said...
ReplyDelete> Does it work for 64bit version as well? It didn't work for me (yet).
It should work
great post.
ReplyDeleteNow vmware 2.0.2 runs on my thinkpad 410s with ubuntu 10.04
thank you
worked for me with....
ReplyDeleteThe configuration of VMware Server 2.0.2 build-203138 for Linux for this
running kernel
Linux baby 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 x86_64 GNU/Linux
completed successfully.
Thanks for the great post!
ReplyDeleteAny idea on how to get full screen working with the remote console?
I huge thank you dude! You saved me hours if not days :)
ReplyDeleteWill the installation even work on Lucid 64bit 2.6.32-25-server kernel? I have to upgrade the host-kernel because of intel-usb hardware bugfixes and I am scared the vmware-server will probably not start again...
ReplyDeleteAnd to mention my last problem (see above): The webinterface now works (after reinstalling anything). But I still have a problem: Only one "/etc/init.d/vmware restart" e.g. causes a no-more working vmware. Even host reboot does not fix it then. I have to uninstall and reinstall (as written in this guide - thanks again for the howto). Any clues?
BTW does anybody know if VMWare will release an update or next version of vm-ware server? I would be soooo lucky for finding ready-to-run dpkg's one day. Or will the product be discontinued?
Greetings
I realise now reading the title "Installing vmware-server-2.0.2 in Ubuntu Lucid Lynx 10.04" that I am a numpty
ReplyDeleteTo clarify what Alf said (because I tried 'restarting' at a couple different points without success), I made the changes to
ReplyDeletevmnet-only/vnetUserListener.c and
vmci-only/linux/vmciKernelIf.c (as well as deleting the spaces in compat_sched.h as Mike suggested) BEFORE I tried applying the ubuntugeek patch. It then compiled correctly. Get a VSOCK error though, not sure if that will cause any issues in the future, but I am connected to the web console now.
This no longer seems to work, but here is one from the ubuntu forums that worked for me. You need to be sure and run the patch script and use the path to the where you downloaded the VMware-server-2.0.2-203138.x86_64.tar.gz to.
ReplyDeletehttps://help.ubuntu.com/community/VMware/Server
Hope this helps others.
WalkTheTalk said...
ReplyDelete> This no longer seems to work, but here is one from the ubuntu forums that
> worked for me. You need to be sure and run the patch script and use the
> path to the where you downloaded the
> VMware-server-2.0.2-203138.x86_64.tar.gz to.
Hi WalkTheTalk, you probably missed some step(s) because I'm constantly deploying vmware-servers for my customers following this system (in an automated way). As far as of today I've just deployed two HP Proliant G6 with ubuntu 10.04.1 LTS which are serving right now its brand new virtual machines.
You didn't said what went wrong to you, so I cannot help you.
Finally something that works! Thx a lot by the post.
ReplyDeleteI've been looking for a piece of tech advice on the internet, but none (except your post) work.
Thx again.
Pedro
Hi I am having same problem as adeola,
ReplyDeletewhile doing: sudo ./vmware-server.2.0.1_x64-modules-2.6.30.4-fix.sh
I get:
Found tar file for vmmon module
Found tar file for vmci module
Found tar file for vmnet module
Found tar file for vmci-temp module
Found tar file for vsock-temp module
Found tar file for vmnet-temp module
Found tar file for vsock module
Found tar file for vmmon-temp module
Using patch file: /home/aa306/Desktop/vmware-server-distrib/vmware-server.2.0.1_x64-modules-2.6.30.4-fix.patch
Using module directory: /usr/lib/vmware/modules/source
Using backup directory: /usr/lib/vmware/modules/source-backup
Untarring vmmon.tar
Untarring vmci.tar
Untarring vmnet.tar
Untarring vmci-temp.tar
Sorry, vmci-temp.tar tarball failed to extract the directory vmci-temp-only
I really appreciate if someone can help me, because after struggling a lot with the headers and getting here, I think Im already there but it is still missing!
Thanks,
Asa
thank you, thank you, thank you
ReplyDeleteThanks a lot, saved a lot of time and is very dependable.
ReplyDeletei have this problem "Power on this Virtual Machine error"
ReplyDeleteI also recommend you to watch this ubuntu installation video.
ReplyDeletehttps://www.youtube.com/watch?v=-DLZETe0onY