Request for ebuild for VMWare Workstation 5.5 Beta. Download location: http://www.vmware.com/wl/info/1884/0 Reproducible: Always Steps to Reproduce: 1. 2. 3.
We don't do the betas. Feel free to REOPEN when it goes final. I will add an ebuild under package.mask if you attach one, but I won't spend my time creating one for a beta product that will just generate more bugs for me... ;]
*** Bug 106130 has been marked as a duplicate of this bug. ***
Wolf: Please add me to the vmware herd, i'll add a package.masked version of the beta and will handle bugs.
I added you, but in the future, you can just add yourself to herds by editing gentoo/misc/herds.xml in CVS...
Also, please hold off on this for a bit... I'm about to make some changes to the vmware ebuilds due to a security bug and also to resolve another bug, and it would be best if you based your ebuild off the updated ebuilds rather than the current ones.
I added the new vmware-workstation 5 ebuild into portage, so base your work off that. There's not a whole lot changed, but the primary thing is the requirement of being in the vmware group now.
Created attachment 68685 [details] vmware-workstation-5.5.0.16325.ebuild
Created attachment 68686 [details, diff] files/vmware-workstation-5.5.0.16325-config.patch The /opt/vmware/bin/vmware-config.pl script will start the service thus making it impossible to use our init.d script. What do you think of removing that from the script?
> The /opt/vmware/bin/vmware-config.pl script will start the service thus making it impossible to use our init.d script. What do you think of removing that from the script? From a user point of view; I like this change a lot, I have quite a few systems in monitoring, one of the things I (we) monitor is if all the init-scripts are started; when vmware is upgraded I always need to kill some stuff before I can start the init-script. I have checked /opt/vmware/bin/vmware-config.pl but is kinda large script, but maybe you know this already; when vmware is correctly configured is the only interesting/necessary step that this script do building the kernelmodule? If yes, why not do this from the ebuild so upgrades don't need any extra manual steps (besides restarting the init-script)?
I'll add a here patch for the vmware-config.pl script that uses our init, well actually out init script almos only wrapps the vmware one in /etc/vmware/init.d but this way the gentoo init system is always uptodate.
Created attachment 68690 [details, diff] vmware-config.pl.patch
Created attachment 68696 [details] vmware-workstation-5.5.0.16325.ebuild Fix for need to have vmware-vmx binary setuid root.
Created attachment 68697 [details] files/vmware-workstation-5.5.0.16325-config.patch Combine the two patches.
Created attachment 68699 [details] files/vmware-workstation-5.5.0.16325-config.patch Uploaded the unchanged patch, sorry for the extra mail.
there is a bug in the ebuild: it installed the init-script to /etc/vmware/init.d/vmware, not to /etc/init.d/vmware. I didn't do any further investigations, but you should fix this
(In reply to comment #15) > there is a bug in the ebuild: it installed the init-script to > /etc/vmware/init.d/vmware, not to /etc/init.d/vmware. I didn't do any further > investigations, but you should fix this No there is not. The /etc/vmware/init.d/vmware is the vmware builtin script, the /etc/init.d/vmware is the gentoo wrapper. If you do not have a /etc/init.d/vmware that is because you did not copy the file from the portage files dir to your overlay.
I don't see a problem with using our init script wrapper, so feel free to commit that. Will it apply cleanly to older versions (5.0)? Also, vmware-config.pl does a ton of junk. Yes, if someone wanted to taek the time to change it all to ebuild syntax, I'd gladly add it to the ebuilds, since it would remove the requirement to re-run vmware-config.pl every time you reinstall vmware. We would still want it around for upgraded kernels, though, so we don't want to patch out the functionality, just add the functionality to the ebuild.
I can't get this to work, perhaps I have done something wrong I get this circular annoyance when trying to run the config script /opt/vmware/bin/vmware-config.pl Making sure services for VMware Workstation are stopped. * ERROR: "vmware" has not yet been started. Unable to stop services for VMware Workstation Execution aborted. If I try to start the init script.. /etc/init.d/vmware start * Re-caching dependency info (mtimes differ)... * 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. [ !! ] So I can't start it without configuring it, and it won't configure before it's started (and it can stop it itself). Catch 22 Jim PS. The patch is successfully applied at the start of emerge Portage 2.0.51.22-r2 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r1, 2.6.13-gentoo-r2 x86_64) ================================================================= System uname: 2.6.13-gentoo-r2 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5, 2.4.1-r1 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.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=athlon64 -pipe" CHOST="x86_64-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/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -march=athlon64 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks multilib-strict sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.blueyonder.co.uk http://mirror.gentoo.gr.jp http://ftp.gentoo.or.kr/ ftp://mirror.nutsmaas.nl/gentoo/" LINGUAS="en_GB" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aac alsa amarok amd64 apache2 avi berkdb bitmap-fonts browserplugin cdb cdr crypt cups curl dba directfb dvd dvdr dvdread eds emboss encode esd fam flac foomaticdb fortran freetype gd gdbm gif gphoto2 gpm gstreamer gtk gtk2 guile hal imagemagick imlib ipv6 java jpeg junit kde kdeenablefinal ldap libwww lzw lzw-tiff mad mikmod mp3 mpeg mplayer msn musicbrainz mysql ncurses nls nocd nvidia ogg oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline real ruby samba sdl speex spell ssl symlink tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts usb userlocales v4l vcd vorbis xine xml xml2 xpm xv zlib linguas_en_GB userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS
You probably need module unload support in your kernel...
CONFIG_MODULE_UNLOAD ? It's there... Jim
Just to be sure I removed the modules by hand, stoped the service, made sure all processes were gone and i emerge -C vmware-workstation, after that i nuked all vmware related stuff from /opt and /etc. I then remerged vmware. Tried the /etc/init.d/vmware script and got the expected error. I then runned the /opt/vmware/bin/vmware-config.pl script and all went fine. From your messages i cannot see what is wrong. I know that the output of the config.pl script should be: sam portage # /opt/vmware/bin/vmware-config.pl Making sure services for VMware Workstation are stopped. * ERROR: "vmware" has not yet been started. 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 ................................... Please do a emerge sync and try again. This time do a emerge -C vmware-workstation;rm -rf /etc/vmware /etc/init.d/vmware /opt/vmware first :) ALSO before the emerge see if there are loaded modules used by vmware (vmnet vmmon)
I have exactly the same problem as Jim; Jim, Were you able to solve this problem, if so how? Gustavo, Chris, Do you have more tips/tricks I can try? Is it necessary to (re)open this/a bug? # lsmod Module Size Used by nvidia 3704904 12 # uname -r 2.6.13-gentoo # grep MODULE /usr/src/linux/.config CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODULE_SRCVERSION_ALL is not set # emerge sync # emerge -C vmware-workstation # rm -rf /etc/vmware /etc/init.d/vmware /opt/vmware # emerge vmware-workstation -v # /opt/vmware/bin/vmware-config.pl Making sure services for VMware Workstation are stopped. * ERROR: "vmware" has not yet been started. Unable to stop services for VMware Workstation Execution aborted. # /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. # emerge --info Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r1, 2.6.13-gentoo i686) ================================================================= System uname: 2.6.13-gentoo i686 AMD Athlon(tm) XP 2600+ 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 [disabled] 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.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" 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/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks fixpackages sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X a52 aac alsa apm arts artswrappersuid avi bash-completion berkdb bitmap-fonts cddb cdinstall cdr crypt css cups curl dts dvd dvdr eds emboss encode fam ffmpeg flac font-server foomaticdb fortran gd gdbm gif gpm gstreamer hal imagemagick imlib jack java javascript jpeg kde kdeenablefinal kdexdeltas kdgraphics libg++ libwww lm_sensors logitech-mouse mad mikmod mmx mng motif mozilla mp3 mpeg musicbrainz ncurses nls nocd nptl nsplugin nvidia ogg oggvorbis opengl pam pdflib png ppds python qt quicktime rdesktop readline real samba scanner sdl sensord slang speex spell sse ssl svga tcpd theora tidy tiff truetype truetype-fonts type1-fonts unicode usb visualization vorbis win32codecs xine xml xml2 xv xvid xvmc zeroconf zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Well, it definitely wouldn't belong here. As for VMWare itself, I'd recommend contacting them for support on their code. Problems with vmware-config.pl or the modules falls squarely within their support. We'll gladly add any necessary patches to resolve these issues, but I personally don't feel that we should be spending our time to work on any VMWare issues that are non-ebuild related, as VMWare is a commercial company with their own support. Besides, as a beta tester, you're supposed to be reporting bugs to them so they can fix them. Basically, we're not paid by VMWare, so why should we work for them fixing their bugs for free? Applying patches to our ebuilds that have been made by VMWare (or even third parties) is one thing, but trying to troubleshoot and create patches for a commercial product is a bit much. If you're having problems with the modules not unloading, try a reboot. Unfortunately, that's about all the advice I can give you.
(In reply to comment #23) > Well, it definitely wouldn't belong here. Sorry, this was ambiguous. The "here" would mean this bug. This bug was for having the package added to portage. As you can tell from comment #1, I wasn't too keen on the idea of even adding this thing to portage due to it being a beta and *knowing* that stuff simply isn't going to work right. By the way, does anyone know if vmware-any-any-update94 might have anything to resolve this issue?
