First off all I just emerge vmware-workstation after a while I found out that the any-any-update75 failed due to missing ld-linux.so.2. After I make shure that there ist a link to /emul/linux/x86/lib/ld-linux.so.2 I run the vmware-config.pl. the modules loaded the vmnet
First off all I just emerge vmware-workstation after a while I found out that the any-any-update75 failed due to missing ld-linux.so.2. After I make shure that there ist a link to /emul/linux/x86/lib/ld-linux.so.2 I run the vmware-config.pl. the modules loaded the vmnet´s are reachable. To start vmware still fail Reproducible: Always Steps to Reproduce: 1.emerge vmware-workstation 2.vmware-config.pl 3. make shure the kernel modules loaded 4. ping to the vmnet1 5. try to start or stop vmware /etc/init.d/vmware (stop/start) Actual Results: ERROR: "vmware" has not yet been started 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: just starting :) after running vmware-config again: Stopping VMware services: Virtual machine monitor done Bridged networking on /dev/vmnet0 done DHCP server on /dev/vmnet1 done SMB share server on /dev/vmnet1 done SMB name 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 failed Unable to stop services for VMware Workstation Execution aborted. After that I killed the running pid and restart the configuration: Starting VMware services: Virtual machine monitor done Virtual ethernet done Bridged networking on /dev/vmnet0 done Host-only networking on /dev/vmnet8 (background) done NAT service on /dev/vmnet8 done The configuration of VMware Workstation 4.5.2 build-8848 for Linux for this running kernel completed successfully /etc/init.d/vmware start * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Bridged networking on /dev/vmnet0 [ !! ] * Host-only networking on /dev/vmnet8 (background) [ ok ] * NAT service on /dev/vmnet8 [ !! ] Portage 2.0.50-r9 (default-amd64-2004.0, gcc-3.3.4, glibc-2.3.4.20040619-r0, 2.6.7-gentoo-r11) ================================================================= System uname: 2.6.7-gentoo-r11 x86_64 5 Gentoo Base System version 1.5.1 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-O2" CHOST="x86_64-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache" GENTOO_MIRRORS="http://gentoo.inode.at/ ftp://gentoo.inode.at/source/ ftp://ftp.easynet.nl/mirror/gentoo/ http://ftp.easynet.nl/mirror/gentoo/ ftp://ftp.tu-clausthal.de/pub/linux/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X acpi alsa amd64 apm arts avi berkdb cdr crypt cups directfb dvd dvdr encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib jpeg kde libg++ libwww linguas_de mikmod motif mozilla mpeg mysql nas ncurses nls nogcj oggvorbis opengl oss pam pdflib perl png postgres ppds python qt quicktime readline samba sdl slang spell ssl tcpd truetype xml2 xmms xv zlib"
looks like a duplicate of http://bugs.gentoo.org/show_bug.cgi?id=54269 [ vmware /dev nodes not restored on pure udev systems ] Do you use udev?
No I don't All /dev/vm* appear after reeboot I faced now the same error on one 32 bit box after the last update. So both systems run now with gcc 3.4 . An Issue ?
I think this has been a persistent problem with the vmware ebuilds. After you run successfully vmware-config.pl, you need to manually remove the /etc/vmware/not_configured file.
Thanks! Removing the file was the solution for me! After I configured vmware-workstation, the script told me that vmware is fully configured and in the next line it printed that it is not fully configured and that I should run the vmware-config.pl again.... After removing the file, everything is okay :)
Can you please close this bug? I do not think a high rate of open bugs is something to be proud of ..
Markus, did the above solution work for you?
Same problem here. Run vmware-config.pl with gcc-3.4.1 and gentoo-dev-sources-2.6.8-r1. Directly after the script finished, the not_configured file is *not* in /etc/vmware/ and I can run vmware just fine. As soon as the init-script ran (for example after a reboot), the init-script fails: antares /home/benni # /etc/init.d/vmware start * Starting VMware services: [ ok ] * Virtual machine monitor [ !! ] * Virtual ethernet [ !! ] * Bridged networking on /dev/vmnet0 [ !! ] * Host-only networking on /dev/vmnet8 (background) [ ok ] * NAT service on /dev/vmnet8 [ !! ] *then* the not_configured file suddenly is back in /etc/vmware/. When I try to start the init-script again, I get the well known message: antares /home/benni # /etc/init.d/vmware start * 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. [ !! ] however, I won't be able to run vmware until I again ran the config-script. Conclusion: I need to run the configure-script everytime (at least once after a reboot). Kinda annoying.
http://escargot.icehouse.net/mediawiki/index.php/vmware_on_gentoo is my log of trying to get it to work, feel free to export it and tweak it I did the configuration script thing, and.. I just found that the not_configured files is still there... I had to manually modprobe vmmon, but, hey, it worked! I had to delete the not_configured file after running the init script though... (I don't know if vmware will _work_ but the gui finally came up past the non-configured note)
I believe that this is fixed in -r2 now in CVS
It is not fixed in -r2... 1> opt/vmware/bin/vmware /usr/bin/ldd: line 152: /lib/ld-linux.so.2: No such file or directory ldd: /lib/ld-linux.so.2 exited with unknown exit code (127) /opt/vmware/bin/vmware: line 189: /opt/vmware/lib/bin/vmware: No such file or directory /opt/vmware/bin/vmware: line 189: /opt/vmware/lib/bin/vmware: Success Change the status or new bug?
It is dependent on the kernel that you're using.
