Have you read that thread Here is patch for 2.6.30 kernel for VMware Server 2.0.1 build-156745 x_64
If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points.
Kernel 2.6.30 ist NOT the problem. With the kernel 2.6.30 VMware Server 2 is running. The kernel 2.6.31 is the problem.
I can confirm that the fix posted for 2.6.30 does not work for 2.6.31
Is there another patch in the works or are we going to have to hold back kernel upgrades?
Try the patch for kernel 184.108.40.206, midway down this page: http://communities.vmware.com/thread/215985?start=15&tstart=0
This worked for me - now I am running the latest 64-bit VMware Server 2.0.1 on kernel 2.6.31 (64-bit Ubuntu 9.04) just fine. Make sure you follow the directions in the succeeding posts when patching the modules.
But here it wount compile. See the errormessage below:
Trying to compile vmnet module to see if it works
Using 2.6.x kernel build system.
make -C /lib/modules/2.6.31-0.slh.1-sidux-amd64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make: Entering directory `/usr/src/linux-headers-2.6.31-0.slh.1-sidux-amd64'
/usr/lib/vmware/modules/source/vmnet-only/netif.c: In function ‘VNetNetIfSetup’:
/usr/lib/vmware/modules/source/vmnet-only/netif.c:201: error: ‘struct net_device’ has no member named ‘init’
/usr/lib/vmware/modules/source/vmnet-only/netif.c:202: error: ‘struct net_device’ has no member named ‘open’
/usr/lib/vmware/modules/source/vmnet-only/netif.c:203: error: ‘struct net_device’ has no member named ‘hard_start_xmit’
/usr/lib/vmware/modules/source/vmnet-only/netif.c:204: error: ‘struct net_device’ has no member named ‘stop’
/usr/lib/vmware/modules/source/vmnet-only/netif.c:205: error: ‘struct net_device’ has no member named ‘get_stats’
/usr/lib/vmware/modules/source/vmnet-only/netif.c:206: error: ‘struct net_device’ has no member named ‘set_mac_address’
/usr/lib/vmware/modules/source/vmnet-only/netif.c:207: error: ‘struct net_device’ has no member named ‘set_multicast_list’
make: *** /usr/lib/vmware/modules/source/vmnet-only/netif.o Fehler 1
make: Leaving directory `/usr/src/linux-headers-2.6.31-0.slh.1-sidux-amd64'
make: *** http://vmnet.ko Fehler 2
Sorry, problem compiling the vmnet module after it was patched
You must restore from this backup directory:
Any other suggestion?
Make sure you are using the 220.127.116.11-fix script, not the 2.6.30-fix.
With 2.6.30-fix, I had similar issues only with the vmnet module.
Delete the four tarballs you copied, remove everything under
/usr/lib/vmware/modules/, rerun the vmware installer script, and choose
NOT to run the vmware-config.pl script. Then copy the four tarballs
back to your patch directory from /usr/lib/vmware/modules/source and run
the 18.104.22.168-fix script.
If it compiles, then you can run the vmware-config.pl script.
After using the .4 patch everything ist working again. But I had to patch the files by hand. Because ther was a skript error:
root@stka:~# sh vmware-server.2.0.1_x64-modules-22.214.171.124-fix.sh
vmware-server.2.0.1_x64-modules-126.96.36.199-fix.sh: 30: Syntax error: word unexpected (expecting "do")
Funny, I did not have that problem. But I am glad it worked out for you
I successfully used the vmware-server.2.0.1_x64-modules-188.8.131.52-fix.patch to build the modules on my laptop running Ubuntu Karmic Koala. VMware Server version is 2.0.1 from VMware-server-2.0.1-156745.x86_64.tar.gz, and I'm running it with the 2.6.31-10-generic kernel. The issue that I have is that while the web console appears to be running on port 8333, I cannot get a response from it. Has anyone else encountered this issue? Cheers.
I realized that the problem was that the script file (and the patch file) had dos newlines (not unix). Use dos2unix to convert the files and that fixes the problem the shell has interpreting the for/do commands.
According to the 184.108.40.206 patch I've updated the previous patch of 2.6.30 for the 2.6.31
Instructions: verify that you env. is sane (without any previously applied patches)
Apply the patch for 2.6.30 http://communities.vmware.com/thread/215985
Apply the patch for 2.6.31
ps: My env is Ubunt9.04 x06_64 kernel 220.127.116.11+tuxonicepatch, and the patch worked.
If "any" problems, pls read the sh script and modify it on the specs of your env
i have kernel version 18.104.22.168 - 32 bit system and this fixes are not working
after a fresh installation of vmware 2.01 i still get this messages:
make -C /lib/modules/22.214.171.124-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make: Entering directory `/usr/src/packages/BUILD/kernel-126.96.36.199default'
In file included from /usr/lib/vmware/modules/source/vmci-only/./include/vmci_kernel_if.h:41,
/usr/lib/vmware/modules/source/vmci-only/./include/compat_wait.h:78: error: conflicting types for âpoll_initwaitâ
include/linux/poll.h:70: error: previous declaration of âpoll_initwaitâ was here
make: *** /usr/lib/vmware/modules/source/vmci-only/linux/driver.o Error 1
make: Leaving directory `/usr/src/packages/BUILD/kernel-188.8.131.52default'
make: *** http://vmci.ko Error 2
Sorry, problem compiling the vmci module after it was patched
You must restore from this backup directory:
are there someware paches for a 32 bit system an this actual kernel - i looked arround for 4 hours now but nothing seems to help
thaks for your help
just for information ... i use a suse 10.1 guast system
Using Michele's script, I have built my own script that helps you install VMware Server 2.0.x without having to stop in the middle to apply the patch. More details can be found here: How to install VMware Server 2.0.x on Ubuntu 9.10 Karmic Koala.
I hope that you will find my script useful.