See the URL for this ticket. VMWare breaks after every reboot using the vanilla-2.6.8-rc3 kernel with udev only. This worked for me: 1. Add 'rm /etc/vmware/not_configured' to the start section of /etc/init.d/vmware 2. Edit /etc/udev/rules.d/00-vmware.rules and add 2 lines: # tty devices KERNEL="tty[0-9]*", NAME="vc/%n", SYMLINK="%k" # floppy devices KERNEL="fd[0-9]*", NAME="floppy/%n" , SYMLINK="fd%n" The author of this post on the Archlinux Wiki created a lot of device nodes on each start, but I didn't have to do this.
*** Bug 81891 has been marked as a duplicate of this bug. ***
Would it be possible to get an example from somebody's /etc/init.d/vmware file? It is quite difficult to know where to put the line. Can it be anyware or should it be somewhere here??? start() { test -x /etc/vmware/init.d/vmware || \ eend 1 "vmware init script not found. Aborting" || return 1 /etc/vmware/init.d/vmware start | vmware-prettify start return $? } _________________ As to the second suggestion, do I have to create 00-vmware.rules, because there is no such file. I have only got/etc/udev/rules.d/50-udev.rules. But maybe that is the same thing? It also wouldn't hurt to give an example. Ty linfan
Hello. I was experiencing the same problem. Adding the following to /etc/init.d/vmware just after the "start()" line solved: for a in `seq 0 9`; do mknod /dev/vmnet$a c 119 $a; done Not sure if this is the ideal way to do it, but it does solve the problem.
Thank you Bruno :-) That did the trick for me, too. I will give an example, where I put it in nano -w /etc/init.d/vmware: _____________________ start() { for a in `seq 0 9`; do mknod /dev/vmnet$a c 119 $a; done test -x /etc/vmware/init.d/vmware || \ eend 1 "vmware init script not found. Aborting" || return 1 /etc/vmware/init.d/vmware start | vmware-prettify start return $? } _____________________ Regards, linfan
Created attachment 62804 [details, diff] init.d/vmware patch This patch is for /etc/init.d/vmware, based on the code of the previous post. The file /etc/vmware/not_configured, tha patch is in the bug 95761.
Is this still happening with the latest vmware-workstation versions? I haven't encountered this in a long time.
FWIW, I *cannot* confirm it w/ 2.6.12.2 and vmware-workstation 4.5.2.8848-r6.
I think newer versions of udev probably resolved this... feel free to REOPEN it if it is still happening...
This bug is not fixed, /dev/vmnet* devices still don't get created by the init.d script. udev is version 070, vmware-workstation 4.5.2.8848-r7. I just remerged vmware just to be sure... Please reopen bug. Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r1, 2.6.12-gentoo-r10 i686) ================================================================= System uname: 2.6.12-gentoo-r10 i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.6.13 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.5-r2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.8.1-r1, 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-mcpu=i686 -O3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=i686 -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildpkg candy ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.inode.at/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://gentoo.inode.at/source/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo" LANG="de_DE.UTF-8" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="x86 3dnow X aalib acpi acpi4linux adns alsa apache2 avi bash-completion berkdb bitmap-fonts bluetooth bonobo cdr crypt cups curl dba dvb dvd dvdr eds emboss encode esd fam fbcon flac foomaticdb fortran gd gd-external gdbm gif gphoto2 gpm gstreamer gtk gtk2 gtkhtml hal ieee1394 imagemagick imlib innodb ipv6 java jpeg junit kde kdexdeltas ldap libg++ libwww mad maildir mikmod mmx motif mozilla mp3 mpeg mysql ncurses nls nptl ogg oggvorbis opengl oss pam pda pdflib perl png posix postgres python qt quicktime readline samba sdl session slang speex spell sqlite srvdir sse ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts unicode vorbis xine xml xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS
I have no plans on adding device creation to the init scripts, as I think that's really a nasty kludge. Strange that I cannot reproduce this problem. Anyway, I'll REOPEN the bug.
What I actually wanted to say is that the vmnet devices don't get created when the vmnet module is being loaded. I don't recommend a nasty workaround either. So the bug must be related to a missing or wrong udev configuration for VMware, right?
Did you run etc-update after installing the newer version? I've not had a single problem getting the device nodes to create, which is why I've said that I cannot duplicate this issue. This is with either 4.5 or 5.0 on both x86 and amd64, using various udev versions >= 054.
Yes I did, all configuration files are up-to-date. Please tell me which config files should be there (/etc/udev/rules.d/* etc) and what they should look like. Maybe this problem is related to my kernel version? When I manually modprobe vmmon I see a message in /var/log/messages. But when I modprobe vmnet there is no message.
This is exactly my problem (except for VMware version, OS and kernel version): http://www.vmware.com/community/thread.jspa?threadID=18717&messageID=210765 If I do an mknod /dev/vmnet0 c 119 0 mknod /dev/vmnet8 c 119 8 before /etc/init.d/vmware start then everything works! So I am pretty sure the problem is that the vmnet* devices don't get created when the vmnet module loads.
*** Bug 139207 has been marked as a duplicate of this bug. ***
I newly ran into the same problem after upgrading to the now stable sys-apps/baselayout-1.11.15-r3. Falling back to sys-apps/baselayout-1.11.14-r8 solves it. The patch attached to comment #5 also solves it. I also guess that this is mainly an udev problem which could be solved with a modified rule for vmware. Don't know enough about device creation via udev to fix it. But I will play a bit.
Can anyone verify that this is still a problem with the new split vmware ebuilds + baselayout 1.12 + stable udev? I'm running ~arch on all of my vmware boxes, so cannot easily test this myself.
Well, since nobody spoke up, I'm guessing that this has been fixed.