vmware-config.pl fails with: /tmp/vmware-config0/vmnet-only/driver.c: In function `VNetProcessOwnsPort': /tmp/vmware-config0/vmnet-only/driver.c:1816: error: structure has no member named `max_fds' make[2]: *** [/tmp/vmware-config0/vmnet-only/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config0/vmnet-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.13-rc6-mm1' Reproducible: Always Steps to Reproduce: 1. 2. 3.
I just updated the patch version to 93... can you try doing an emerge sync and see if the latest version fixes your issue? Otherwise, it'll have to wait for an upstream patch unless you have one yourself.
no luck - confirming sync and reemerge which picked up the 93 patch. also rm -rf /etc/vmware/ rm -rf /etc/init.d/vmware rm -rf /lib/modules/*/misc/vm*.o rm -rf /var/tmp/portage/* and /tmp/* cleared ccache -C lsmod - confirmed no modules loaded env-update && source /etc/profile emerge vmware-workstation (no issue) /opt/vmware/bin/vmware-config.pl output: Making sure services for VMware Workstation are stopped. Stopping VMware services: Virtual machine monitor done You must read and accept the End User License Agreement to continue. Press enter to display it. Do you accept? (yes/no) yes Thank you. Configuring fallback GTK+ 2.4 libraries. 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.13-rc6-mm1/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Building for VMware Workstation 5.0.0. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmmon-only' make -C /lib/modules/2.6.13-rc6-mm1/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.13-rc6-mm1' CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:26, from /tmp/vmware-config0/vmmon-only/linux/driver.c:52: /tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:222:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:57, from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:22, from /tmp/vmware-config0/vmmon-only/./common/vmx86.h:18, from /tmp/vmware-config0/vmmon-only/linux/driver.h:16, from /tmp/vmware-config0/vmmon-only/linux/driver.c:53: /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:56:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:25, from /tmp/vmware-config0/vmmon-only/linux/driver.c:56: /tmp/vmware-config0/vmmon-only/./include/vm_basic_asm.h:50:5: warning: "_MSC_VER" is not defined CC [M] /tmp/vmware-config0/vmmon-only/linux/hostif.o In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:26, from /tmp/vmware-config0/vmmon-only/linux/hostif.c:48: /tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:222:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:25, from /tmp/vmware-config0/vmmon-only/linux/hostif.c:50: /tmp/vmware-config0/vmmon-only/./include/vm_basic_asm.h:50:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:57, from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:22, from /tmp/vmware-config0/vmmon-only/linux/hostif.c:51: /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:56:5: warning: "_MSC_VER" is not defined CC [M] /tmp/vmware-config0/vmmon-only/common/cpuid.o In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:26, from /tmp/vmware-config0/vmmon-only/common/cpuid.c:12: /tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:222:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:57, from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:22, from /tmp/vmware-config0/vmmon-only/common/vmx86.h:18, from /tmp/vmware-config0/vmmon-only/common/hostif.h:18, from /tmp/vmware-config0/vmmon-only/common/cpuid.c:14: /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:56:5: warning: "_MSC_VER" is not defined CC [M] /tmp/vmware-config0/vmmon-only/common/hash.o In file included from /tmp/vmware-config0/vmmon-only/./include/hash.h:23, from /tmp/vmware-config0/vmmon-only/common/hash.c:14: /tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:222:5: warning: "_MSC_VER" is not defined CC [M] /tmp/vmware-config0/vmmon-only/common/memtrack.o In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:26, from /tmp/vmware-config0/vmmon-only/common/memtrack.c:25: /tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:222:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:57, from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:22, from /tmp/vmware-config0/vmmon-only/common/vmx86.h:18, from /tmp/vmware-config0/vmmon-only/common/memtrack.c:28: /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:56:5: warning: "_MSC_VER" is not defined CC [M] /tmp/vmware-config0/vmmon-only/common/phystrack.o In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:26, from /tmp/vmware-config0/vmmon-only/common/phystrack.c:26: /tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:222:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:57, from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:22, from /tmp/vmware-config0/vmmon-only/common/vmx86.h:18, from /tmp/vmware-config0/vmmon-only/common/phystrack.c:27: /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:56:5: warning: "_MSC_VER" is not defined CC [M] /tmp/vmware-config0/vmmon-only/common/task.o cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++ cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++ cc1plus: warning: command line option "-Wstrict-prototypes" is valid for C/ObjC but not for C++ cc1plus: warning: command line option "-ffreestanding" is valid for C/ObjC but not for C++ In file included from include/linux/bitops.h:77, from include/linux/kernel.h:15, from /tmp/vmware-config0/vmmon-only/common/task.c:27: include/asm/bitops.h: In function `int find_first_bit(const long unsigned int*, unsigned int)': include/asm/bitops.h:339: warning: comparison between signed and unsigned integer expressions In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:26, from /tmp/vmware-config0/vmmon-only/common/task.c:36: /tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:222:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:57, from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:22, from /tmp/vmware-config0/vmmon-only/common/task.c:37: /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:56:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:25, from /tmp/vmware-config0/vmmon-only/common/task.c:40: /tmp/vmware-config0/vmmon-only/./include/vm_basic_asm.h:50:5: warning: "_MSC_VER" is not defined CC [M] /tmp/vmware-config0/vmmon-only/common/vmx86.o In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:26, from /tmp/vmware-config0/vmmon-only/common/vmx86.c:25: /tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:222:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:57, from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:22, from /tmp/vmware-config0/vmmon-only/common/vmx86.h:18, from /tmp/vmware-config0/vmmon-only/common/vmx86.c:27: /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:56:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:25, from /tmp/vmware-config0/vmmon-only/common/vmx86.c:30: /tmp/vmware-config0/vmmon-only/./include/vm_basic_asm.h:50:5: warning: "_MSC_VER" is not defined CC [M] /tmp/vmware-config0/vmmon-only/vmcore/compat.o In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:26, from /tmp/vmware-config0/vmmon-only/vmcore/compat.c:5: /tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:222:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:57, from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:22, from /tmp/vmware-config0/vmmon-only/vmcore/compat.c:7: /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:56:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vm_asm.h:25, from /tmp/vmware-config0/vmmon-only/vmcore/compat.c:11: /tmp/vmware-config0/vmmon-only/./include/vm_basic_asm.h:50:5: warning: "_MSC_VER" is not defined CC [M] /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:26, from /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.c:13: /tmp/vmware-config0/vmmon-only/./include/vm_basic_defs.h:222:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/./include/vcpuset.h:57, from /tmp/vmware-config0/vmmon-only/./include/modulecall.h:22, from /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.c:15: /tmp/vmware-config0/vmmon-only/./include/vm_atomic.h:56:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.c:19: /tmp/vmware-config0/vmmon-only/./include/vm_basic_asm.h:50:5: warning: "_MSC_VER" is not defined LD [M] /tmp/vmware-config0/vmmon-only/vmmon.o Building modules, stage 2. MODPOST CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o LD [M] /tmp/vmware-config0/vmmon-only/vmmon.ko make[1]: Leaving directory `/usr/src/linux-2.6.13-rc6-mm1' cp -f vmmon.ko ./../vmmon.o make: Leaving directory `/tmp/vmware-config0/vmmon-only' The file /lib/modules/2.6.13-rc6-mm1/misc/vmmon.ko that this program was about to install already exists. Overwrite? [yes] The module loads perfectly in the running kernel. Do you want networking for your virtual machines? (yes/no/help) [yes] Configuring a bridged network for vmnet0. The following bridged networks have been defined: All your ethernet interfaces are already bridged. Do you want to be able to use NAT networking in your virtual machines? (yes/no) [yes] no Do you want to be able to use host-only networking in your virtual machines? [no] Extracting the sources of the vmnet module. Building the vmnet module. Building for VMware Workstation 5.0.0. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmnet-only' make -C /lib/modules/2.6.13-rc6-mm1/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.13-rc6-mm1' CC [M] /tmp/vmware-config0/vmnet-only/driver.o In file included from /tmp/vmware-config0/vmnet-only/vnet.h:14, from /tmp/vmware-config0/vmnet-only/vnetInt.h:10, from /tmp/vmware-config0/vmnet-only/driver.c:40: /tmp/vmware-config0/vmnet-only/vm_atomic.h:56:5: warning: "_MSC_VER" is not defined In file included from /tmp/vmware-config0/vmnet-only/vm_oui.h:14, from /tmp/vmware-config0/vmnet-only/vnetInt.h:11, from /tmp/vmware-config0/vmnet-only/driver.c:40: /tmp/vmware-config0/vmnet-only/vm_basic_asm.h:50:5: warning: "_MSC_VER" is not defined /tmp/vmware-config0/vmnet-only/driver.c: In function `VNetProcessOwnsPort': /tmp/vmware-config0/vmnet-only/driver.c:1816: error: structure has no member named `max_fds' make[2]: *** [/tmp/vmware-config0/vmnet-only/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config0/vmnet-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.13-rc6-mm1' make: *** [vmnet.ko] Error 2 make: Leaving directory `/tmp/vmware-config0/vmnet-only' Unable to build the vmnet 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.
If you are still experiencing this issue, I recoomend contacting VMWare as you are having a problem with their code and not mine. I'm willing to add patches to the ebuild to resolve the issue, but you've paid for VMWare and support, go takes advantage of it... ;]
Thanks - They are already aware of it. Supposed to be dealt with in: http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update94.tar.gz
Nice!
Updated the ebuild in CVS to use update 94... thanks for reporting back to me... =]
gentoo ~ # genlop vmware-workstation * app-emulation/vmware-workstation Sat Sep 17 12:52:45 2005 >>> app-emulation/vmware-workstation-5.0.0.13124-r2 From Changelog: 22 Sep 2005; Chris Gianelloni <wolf31o2@gentoo.org> vmware-workstation-5.0.0.13124-r2.ebuild: Updated to vmware-any-any-update94 and closing bug #104113. So I had vmware-workstation-5.0.0.13124-r2 with patch #93 installed using gentoo-sources-2.6.13-r5. Now I updated to gentoo-sources-2.6.14 which resulted in the build error mentioned in comment #2 and fixed by vmware-patch #94. This was because you did not update the ebuild release number to -r3. It took me two days to figure out why I could not build the vmware kernel modules :-( Please raise the ebuild revision number next time a new vmware patch comes out.
No. There's a reason for it, too. If I revision bumped with every patch-level upgrade, it would require every user to recompile their modules, every time, even when they had a perfectly working VMWare setup before. At any rate, it is impossible for me to counter *possible* *future* updates that you may do. In this one case, it applied, but I can think of several where it would not, as I've had these problems over and over in the past. My general rule of thumb is to *never* expect VMWare to work when I update to new kernel version (not revision) and to always resync/remerge VMWare after any kernel upgrade. Unfortunately, that's just the way it is with a half-source product like VMWare, especially one that is kernel dependent.
I also got bitten by this no change in version numbers. I seriously thought the the ebuild had not changed a bit and never reemerged it. I didn't expect that the ebuild had changed without changing revision/patchlevel numbering. Ofcourse there are good resons to change the version numbers when modifying the ebuild. If you have like 20 computers to manage running gentoo you probably will do all compiling on 1 computer and distribute binary compiles. How would you be able to know any difference between packages in a binary package archive? What if a patch is a security update? Then would people who have a perfectly working vmware configuration never get that update. I suggest that you use the patchlevel _p suffix when the pachlevel changes and change the revision number every time you do change the ebuild. http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1#doc_chap3 We do *need* to know what patchlevel we run. People who have a perfectly working configuration and don't want to upgrade to a new patchlevel can use /etc/portage/package.mask like we do on all other packages we don't want to upgrade.
I'm sorry, but this is a bug. This is not a discussion forum and this issue is not up for discussion. As for security updates, they *always* get a revision bump as everyone needs t upgrade. Quoting from the page you so kindly linked to yourself. "Package revision numbers should be incremented by Gentoo Linux developers when the ebuild has changed to the point where users would want to upgrade. Typically, this is the case when fixes are made to an ebuild that affect the resultant installed files, but the ebuild uses the same source tarball as the previous release. If you make an internal, stylistic change to the ebuild that does not change any of the installed files, then there is no need to bump the revision number. Likewise, if you fix a compilation problem in the ebuild that was affecting some users, there is no need to bump the revision number, since those for whom it worked perfectly would see no benefit in installing a new revision, and those who experienced the problem do not have the package installed (since compilation failed) and thus have no need for the new revision number to force an upgrade." These are compilation fixes and nothing more. I am fully within the policy on this and have been doing it this way for quite some time, as not everyone needs to reinstall vmware and recompile their modules for every compilation fix. If you have a problem with this, feel free to maintain your own VMWare packages in an overlay or use the official VMWare installation methods.
