No Success here...Kubuntu 8.04 Kernel 2.6.24-5 amd64

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmon-only'
make -C /lib/modules/2.6.24-5-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.24-5-generic'
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config0/vmmon-only/./include/vmci_kernel_defs.h:26,
from /tmp/vmware-config0/vmmon-only/./common/vmciContext.h:19,
from /tmp/vmware-config0/vmmon-only/linux/driver.h:21,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:84:
/tmp/vmware-config0/vmmon-only/./include/compat_wait.h:37:5: warning: "VMW_HAVE_EPOLL" is not defined
/tmp/vmware-config0/vmmon-only/./include/compat_wait.h:43:5: warning: "VMW_HAVE_EPOLL" is not defined
In file included from /tmp/vmware-config0/vmmon-only/./include/vmci_kernel_defs.h:26,
from /tmp/vmware-config0/vmmon-only/./common/vmciContext.h:19,
from /tmp/vmware-config0/vmmon-only/linux/driver.h:21,
from /tmp/vmware-config0/vmmon-only/linux/driver.c:84:
/tmp/vmware-config0/vmmon-only/./include/compat_wait.h:60: error: conflicting types for ‘poll_initwait’
include/linux/poll.h:65: error: previous declaration of ‘poll_initwait’ was here
/tmp/vmware-config0/vmmon-only/linux/driver.c:198: warning: initialization from incompatible pointer type
make[2]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1
make[1]: *** _module_/tmp/vmware-config0/vmmon-only Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-5-generic'
make: *** http://vmmon.ko Error 2
make: Leaving directory `/tmp/vmware-config0/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/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

sblantipodi - can you post 'uname -rm' or 'uname -a'? IE: is it x86_64 or i386 that it works on?

pav: I'll test:

1) extract Workstation 6.0.2
2) Run ./vmware-install.pl but NOT run "vmware-config.pl"
3) extract and run "runme.pl" from vmware-any-any-update-116
4) run vmware-config.pl
5) find and replace modules you just posted
6) /etc/init.d/vmware restart
7) see if the entire host still hangs on any guest startup (which is what currently happens with existing vmware-any-any-update-116)

questions: what's different about these modules you posted? Are my steps above correct? YOu haven't provided a lot of documentation on these posts, so I want to make sure I have them clear.

sblantipodi: and you used his modules to get it to work, right?

/me goes to find a fedora 8 .config and diff it.

Pavlinux:

I'm hoping that you can provide some better instructions, because it seems as though you're a talented module hacker. Unfortunately, I can't yet get your hack to work:

Linux localhost 2.6.24-20080124a #1 SMP Thu Jan 24 22:51:52 CST 2008 x86_64 GNU/Linux (custom 2.6.24 on Ubuntu 7.10 Gutsy with Intel Paravirtualization)

~/vmware-distrib/vmware-install.pl extracted straight from 6.0.2 download fails as others have mentioned many times.

~/vmware-any-any-update116/runme.pl runs fine. modules compile. services start.
However, starting any virtual machine (paravirtual support on or off in the VM) causes the entire host to hang. Appears that it locks the system in a top-most IRQL (255 on x86_64, IIRC?), because no interrupt appears to be serviced (no NIC activity light, no keyboard indicator light) No info in /var/log/messages, nor anywhere else I can find, and I don't have a serial port on this laptop to attach a debugger to (nor a debugger available).

Running your runme.pl from the latest download gives the error that cozmic posted - replayed in full below. I'm attaching my .config for reference, and will PM you some extra contact info if you want some extra testing assistance. I'm unfortunately not a programmer or code-jockey by any means - just a resourceful sysadmin. If anyone else has any thoughts/suggestions, please let us know.

docsmooth@localhost:~/vmware-6.0.2_modules_for_2.6.24$ sudo ./runme.pl
Updating /usr/bin/vmware ... No patch needed/available
Updating /usr/bin/vmnet-bridge ... No patch needed/available
Updating /usr/lib/vmware/bin/vmware-vmx ... No patch needed/available
Updating /usr/lib/vmware/bin-debug/vmware-vmx ... No patch needed/available
VMware modules in "/usr/lib/vmware/modules/source" has been updated.

Before running VMware for the first time after update, you need to configure it
for your running kernel by invoking the following command:
"/usr/bin/vmware-config.pl". Do you want this script to invoke the command for
you now? yes

Making sure services for VMware Workstation are stopped.

Stopping VMware services:
Virtual machine monitor done
Blocking file system: done
Bridged networking on /dev/vmnet0 done
Host network detection done
DHCP server on /dev/vmnet1 done
Host-only networking on /dev/vmnet1 done
DHCP server on /dev/vmnet8 done
NAT service on /dev/vmnet8 done
Host-only networking on /dev/vmnet8 done
Virtual ethernet done

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the theme icons?
[/usr/share/icons]

What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]

In which directory do you want to install the application's icon?
[/usr/share/pixmaps]

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Workstation 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.24-20080124a/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.24-20080124a/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.24'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
In file included from /tmp/vmware-config1/vmmon-only/./include/vmci_kernel_defs.h:26,
from /tmp/vmware-config1/vmmon-only/./common/vmciContext.h:19,
from /tmp/vmware-config1/vmmon-only/linux/driver.h:21,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:84:
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:37:5: warning: "VMW_HAVE_EPOLL" is not defined
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:43:5: warning: "VMW_HAVE_EPOLL" is not defined
In file included from /tmp/vmware-config1/vmmon-only/./include/vmci_kernel_defs.h:26,
from /tmp/vmware-config1/vmmon-only/./common/vmciContext.h:19,
from /tmp/vmware-config1/vmmon-only/linux/driver.h:21,
from /tmp/vmware-config1/vmmon-only/linux/driver.c:84:
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:60: error: conflicting types for ‘poll_initwait’
include/linux/poll.h:65: error: previous declaration of ‘poll_initwait’ was here
/tmp/vmware-config1/vmmon-only/linux/driver.c:198: warning: initialization from incompatible pointer type
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-2.6.24'
make: *** http://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/download/modules/modules.html" and
"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

Message was edited by: docsmooth - changed to plain text editor, repasted, so the interpreter didn't screw up the errors.

Debian 32-bit? 64-bit? custom or stock kernel? Workstation 6.0.0? 6.0.01? 6.0.02?

My system continues to freeze upon bootup of guests. With any-any-update115a, the vmware BIOS logo doesn't come up, but the actual freeze doesn't happen for about 45 seconds, rather than immediately with 116.

So yeah, everything compiles, but that doesn't mean it's working here.