After upgrading to 2.6.12-r4 and linux-headers-2.6.11-r2 vmware-config.pl fails to compile the vmnet module. This sometimes results in a kernel oops when the modules are loaded. It seems that the linux kerenl API sk_alloc was changed between minor releases 2.6.11 and 2.6.12 Two arguments changed places a pointer and a Boolean which cause the kernel to oops. Reproducible: Always Steps to Reproduce: 1.vmware-config.pl 2. 3. Actual Results: Output of vmware-config.pl (shortened): Making sure services for VMware Workstation are stopped. Stopping VMware services: Virtual machine monitor done Bridged networking on /dev/vmnet0 done Virtual ethernet done <...SNIP...> Building the vmnet module. Building for VMware Workstation 4.5.2 or VMware GSX Server 3.1.0. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmnet-only' make -C /lib/modules/2.6.12-gentoo-r4/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.12-gentoo-r4' CC [M] /tmp/vmware-config0/vmnet-only/driver.o CC [M] /tmp/vmware-config0/vmnet-only/hub.o CC [M] /tmp/vmware-config0/vmnet-only/userif.o /tmp/vmware-config0/vmnet-only/userif.c: In function `VNetUserIfMapUint32Ptr': /tmp/vmware-config0/vmnet-only/userif.c:154: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105) /tmp/vmware-config0/vmnet-only/userif.c:155: warning: `verify_area' is deprecated (declared at include/asm/uaccess.h:105) CC [M] /tmp/vmware-config0/vmnet-only/netif.o CC [M] /tmp/vmware-config0/vmnet-only/bridge.o /tmp/vmware-config0/vmnet-only/bridge.c: In function `VNetBridgeUp': /tmp/vmware-config0/vmnet-only/bridge.c:721: warning: passing arg 3 of `sk_alloc' makes pointer from integer without a cast /tmp/vmware-config0/vmnet-only/bridge.c:721: warning: passing arg 4 of `sk_alloc' makes integer from pointer without a cast CC [M] /tmp/vmware-config0/vmnet-only/procfs.o LD [M] /tmp/vmware-config0/vmnet-only/vmnet.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware-config0/vmnet-only/vmnet.ko make[1]: Leaving directory `/usr/src/linux-2.6.12-gentoo-r4' cp -f vmnet.ko ./../vmnet.o make: Leaving directory `/tmp/vmware-config0/vmnet-only' This program previously created the file /lib/modules/2.6.12-gentoo-r4/misc/vmnet.o, and was about to remove it. Somebody else apparently did it already. The module loads perfectly in the running kernel. This program previously created the file /dev/vmnet0, and was about to remove it. Somebody else apparently did it already. You have already setup networking. <...SNIP...> Starting VMware services: Virtual machine monitor done Virtual ethernet done Bridged networking on /dev/vmnet0failed The configuration of VMware Workstation 4.5.2 build-8848 for Linux for this running kernel completed successfully. You can now run VMware Workstation by invoking the following command: "/opt/vmware/bin/vmware". Enjoy, --the VMware team To solve the problem you have to download vmware-any-any-update92 (ftp://platan.vc.cvut.cz/pub/vmware/) and install it before you run vmware-config.pl Maybe the patch should be added to portage?
*** Bug 98228 has been marked as a duplicate of this bug. ***
Dan, Excellent analysis. I can confirm the same issue on my machine, with the same symptoms, and your solution does seem to fix the problem. I'll keep you posted if I see any side effects. Tim
You know it helps to mention what version of a package you're having trouble with, right? Anyway, I've updated VMware 3 and 4 to use update92 and I marked VMware 5 stable. Just do an emerge sync and try again.
So sorry, Chris. I'm can't speak for Dan, but I was getting the problem with vmware-workstation-4.5.2.8848-r6.
OK... I updated vmware 4 to any-any 92... so you should be good to go... I was worried since vmware 5 was already on any-any 92.
(In reply to comment #3) > You know it helps to mention what version of a package you're having trouble > with, right? Sorry Chris that I forgot the version (but if you look at my "case-text" it says "VMware Workstation 4.5.2 build-8848"). By the way. Thanks! --Dan
