First Gentoo bug report so please bear with me... After attempting to emerge both versions of vmware-workstation available and also downloading and installing the newest source beta from vmware I keep coming up with the same problems. Basically, the symptoms are the installer tells me the modules have been built correctly, yet none of the services dependent on them run at all. Furthermore, an "/etc/init.d/vmware restart" command gives me: * VMware Workstation is installed, but it has not been (correctly) configured * for the running kernel. To (re-)configure it, invoke the * following command: /opt/vmware/bin/vmware-config.pl. * VMware is not properly configured! See above. [ !! ] I tried this multiple times. For reference, I'm using gcc-3.2.2 and the linux-2.4.20-gentoo-r1 sources. I know I should probably try this with a vanilla kernel, but the prospect is relatively unappetizing at the moment. If no one pipes up with a similar problem in a day or two I'll check the vanilla 2.4.20 as well as 2.4.19 and possibly 2.4.18 if it still doesn't work... Thanks everyone, I've had a lot of fun getting Gentoo working in the last week or two! Reproducible: Always Steps to Reproduce: 1. emerge vmware 2. run vmware-config.pl 3. rinse and repeat Actual Results: Apparent success...then: root@shanna bin # /etc/init.d/vmware restart * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Bridged networking on /dev/vmnet0 [ !! ] * Host-only networking on /dev/vmnet1 (background) [ ok ] * Host-only networking on /dev/vmnet8 (background) [ ok ] * NAT networking on /dev/vmnet8 [ ok ] root@shanna bin # /etc/init.d/vmware restart * VMware Workstation is installed, but it has not been (correctly) configured * for the running kernel. To (re-)configure it, invoke the * following command: /opt/vmware/bin/vmware-config.pl. * VMware is not properly configured! See above. [ !! ] Expected Results: Compiled working modules. The vmware output during compile (interesting warnings for vmnet module): Extracting the sources of the vmmon module. Building the vmmon module. make: Entering directory `/tmp/vmware-config0/vmmon-only' make[1]: Entering directory `/tmp/vmware-config0/vmmon-only' make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.4.20-gibbons' make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.4.20-gibbons' make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.4.20-gibbons' make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.4.20-gibbons' make[1]: Leaving directory `/tmp/vmware-config0/vmmon-only' make: Leaving directory `/tmp/vmware-config0/vmmon-only' The module loads perfectly in the running kernel. Trying to find a suitable vmnet module for your running kernel. None of VMware Workstation's pre-built vmnet modules is suitable for your running kernel. Do you want this script to try to build the vmnet module for your system (you need to have a C compiler installed on your system)? [yes] Extracting the sources of the vmnet module. Building the vmnet module. make: Entering directory `/tmp/vmware-config0/vmnet-only' In file included from driver.c:51: vmnetInt.h:54:1: warning: "major" redefined In file included from /usr/src/linux/include/linux/fs.h:16, from /usr/src/linux/include/linux/capability.h:17, from /usr/src/linux/include/linux/binfmts.h:6, from /usr/src/linux/include/linux/sched.h:9, from driver.c:22: /usr/src/linux/include/linux/kdev_t.h:80:1: warning: this is the location of the previous definition In file included from driver.c:51: vmnetInt.h:55:1: warning: "minor" redefined In file included from /usr/src/linux/include/linux/fs.h:16, from /usr/src/linux/include/linux/capability.h:17, from /usr/src/linux/include/linux/binfmts.h:6, from /usr/src/linux/include/linux/sched.h:9, from driver.c:22: /usr/src/linux/include/linux/kdev_t.h:81:1: warning: this is the location of the previous definition In file included from userif.c:53: vmnetInt.h:54:1: warning: "major" redefined In file included from /usr/src/linux/include/linux/fs.h:16, from /usr/src/linux/include/linux/capability.h:17, from /usr/src/linux/include/linux/binfmts.h:6, from /usr/src/linux/include/linux/sched.h:9, from userif.c:21: /usr/src/linux/include/linux/kdev_t.h:80:1: warning: this is the location of the previous definition In file included from userif.c:53: vmnetInt.h:55:1: warning: "minor" redefined In file included from /usr/src/linux/include/linux/fs.h:16, from /usr/src/linux/include/linux/capability.h:17, from /usr/src/linux/include/linux/binfmts.h:6, from /usr/src/linux/include/linux/sched.h:9, from userif.c:21: /usr/src/linux/include/linux/kdev_t.h:81:1: warning: this is the location of the previous definition In file included from netif.c:48: vmnetInt.h:54:1: warning: "major" redefined In file included from /usr/src/linux/include/linux/fs.h:16, from /usr/src/linux/include/linux/capability.h:17, from /usr/src/linux/include/linux/binfmts.h:6, from /usr/src/linux/include/linux/sched.h:9, from netif.c:21: /usr/src/linux/include/linux/kdev_t.h:80:1: warning: this is the location of the previous definition In file included from netif.c:48: vmnetInt.h:55:1: warning: "minor" redefined In file included from /usr/src/linux/include/linux/fs.h:16, from /usr/src/linux/include/linux/capability.h:17, from /usr/src/linux/include/linux/binfmts.h:6, from /usr/src/linux/include/linux/sched.h:9, from netif.c:21: /usr/src/linux/include/linux/kdev_t.h:81:1: warning: this is the location of the previous definition In file included from bridge.c:45: vmnetInt.h:54:1: warning: "major" redefined In file included from /usr/src/linux/include/linux/fs.h:16, from /usr/src/linux/include/linux/capability.h:17, from /usr/src/linux/include/linux/binfmts.h:6, from /usr/src/linux/include/linux/sched.h:9, from bridge.c:21: /usr/src/linux/include/linux/kdev_t.h:80:1: warning: this is the location of the previous definition In file included from bridge.c:45: vmnetInt.h:55:1: warning: "minor" redefined In file included from /usr/src/linux/include/linux/fs.h:16, from /usr/src/linux/include/linux/capability.h:17, from /usr/src/linux/include/linux/binfmts.h:6, from /usr/src/linux/include/linux/sched.h:9, from bridge.c:21: /usr/src/linux/include/linux/kdev_t.h:81:1: warning: this is the location of the previous definition make: Leaving directory `/tmp/vmware-config0/vmnet-only' The module loads perfectly in the running kernel.
The vanilla kernel gives the same warnings on compilation - there is probably nothing to worry about here. When the vmware init-script fails in an operation it drops the file 'not_configured' in /etc/vmware, which causes it to bail out and give the mentioned message the next time it is run with 'start'. I haven't looked fully into what causes the script to fail, but perhaps it fails to unload vmnet and/or vmmon, which isn't really an error.. Try deleting not_configured (assuming you've already configured once) and adding vmware to the default runlevel: rc-update add vmware default Even though it really shouldn't be nessecary, it would reboot the machine at this point (to ensure that everything gets properly unloaded). When I do this vmware 3.2 works like a charm (so far).. (Im having a bit trouble getting 4.0beta working - but after all it is nothing more than a beta)
Doing exactly that fixed it completely. Let me know if you need any more information about the circumstances surrounding the errors I was getting... Thanks!
vmware 3.2 just dont work with glibc 2.3.2 witch possibly is the root to your problem. The latest beta 4.0.4257 works fine for me though, with an fully uptodate system (~x86). The current available ebuild don't fit with the available beta setup though. I made a new ebuild for it (attached) with is basicly the same as current but with built number changed and a digest for new beta archive. You ought to place it in /usr/local/portage/... (and activate in make.conf if not done) as it's not an offivciall ebuild yet.
Created attachment 9509 [details] uptodate ebuild for vmware-workstation 4beta ebuild for latest version 4 beta available from vmware. I will submit this separately as well for the portage tree
Version 4 looks great btw and the beta seam pretty stable so far. Only problem I have had so far is when using a physical disk and use specific partition instead of whole disk.
this was not a kernel bug. seems vmware has taken care of their issues. either follow the fix below or upgrade. Closing, Jay
