Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 106644 - vmware-workstation-5.0.0.13124-r2: kernel module doesn't work
Summary: vmware-workstation-5.0.0.13124-r2: kernel module doesn't work
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo VMWare Bug Squashers [disabled]
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-19 22:42 UTC by brankob
Modified: 2005-09-20 10:43 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
vmware-workstation-5.0.0.13124-r1.ebuild (vmware-workstation-5.0.0.13124-r1.ebuild,7.22 KB, text/plain)
2005-09-20 06:14 UTC, Sascha Lucas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description brankob 2005-09-19 22:42:39 UTC
After emerging newest vmware-workstation (5.0.0.13124-r2) I can't make it to work.

It keepstelling me that it's kernel module is not good.

When compiling the module with /opt/vmware/bin/vmware-config.pl , script
compiles the module O.K. and says something to the effect that module fits in
the kernel perfectly, but when I try vmware-workstation, it fails.

Interestingly, vmware-config.pl says something about compiling kernel module
version (!!) 4.5xx and not 5.0.0.xx (!!)

Here is the interesting bit:

******************

VMware 2 or VMware Express detected, building for VMware 2, VMware Express and
VMware Workstation 4.0.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/2.6.12-gentoo-r10/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules

******************

It seems that it builds kernel module for previous version of vmware-workstation
and so it can't use it.

I see there are many reports on the the lasst revision of ebuild
(vmware-workstation-5.0.0.13124-r1), but for me "r1" have been built and was
working just fine. I upgraded to "r2" just because of occasional crash/freeze of
the whole machine...













Reproducible: Always
Steps to Reproduce:
1. emerge vmware-workstation
2. /opt/vmware/bin/vmware-config.pl
3. /usr/bin/vmware

Actual Results:  
vmware is installed, but it has not been (correctly) configured
for this system. To (re-)configure it, invoke the following command:
/opt/vmware/bin/vmware-config.pl.


Expected Results:  
Working vmware

Portage 2.0.51.22-r2 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r1,
2.6.12-gentoo-r10 x86_64)
=================================================================
System uname: 2.6.12-gentoo-r10 x86_64 AMD Opteron(tm) Processor 240
Gentoo Base System version 1.6.13
distcc 2.18.3 x86_64-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="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=opteron -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.1/share/config
/usr/kde/3.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/lib64/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/terminfo /etc/env.d"
CXXFLAGS="-march=opteron -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoclean autoconfig buildpkg candy distlocks fixpackages moo nostrip
sandbox sfperms strict"
GENTOO_MIRRORS="ftp://gentoo.inode.at/source/ ftp://130.59.10.35/mirror/gentoo/
ftp://130.59.10.34/mirror/gentoo/ http://130.59.10.35/mirror/gentoo/
http://ftp.uni-erlangen.de/pub/mirrors/gentoo"
LANG="sl_SI.UTF-8"
LC_ALL="sl_SI.UTF-8"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages/opteron_build_glibc_235"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/portage/local"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X a52 aac aalib adns alsa arts avi berkdb bitmap-fonts cdr crypt
cscope cups curl debug directfb doc dvdr eds emacs emboss encode esd evo
examples extensions fam fbcon flac foomaticdb fortran ftp gdbm ggi gif gnome
gnomedb gpm gstreamer gtk gtk2 guile hal ieee1394 imagemagick imlib ipv6 jack
java jpeg junit kde ldap libgda libwww lirc lm_sensors lzw lzw-tiff mad mikmod
motif mozilla mp3 mpeg mysql nas ncurses nls nntp nptl odbc ogg oggvorbis openal
opengl pam pdflib perl png postgres python qt quicktime readline samba scanner
sdl shared sharedmem slang snmp sockets speex spell ssl svg tcltk tcpd tetex
theora threads tiff truetype-fonts type1-fonts unicode usb userlocales vorbis
wmf xine xinerama xml xml2 xmms xosd xpm xv xvid zlib userland_GNU kernel_linux
elibc_glibc"
Unset:  ASFLAGS, CTARGET, LDFLAGS, LINGUAS
Comment 1 brankob 2005-09-20 00:49:38 UTC
(In reply to comment #0)


Erm, it seems that something else is broken. I hav ejust managed to find old
ebuild of 5.0.0.13124-r1 (fu*k, why can't old ebuilds live for a week or so
before  they are purged from the tree ?!?) and it doesn't work either. 

Kernel is gentoo-source 2.6.12-r10 which has workefd before (besides, I have
tried various old kernels with same results).

I have suspected newest udev, so I downgraded from 0.6.8-r1 to 0.6.8 with
same-negative result.

It seems like module vmnet, when loaded, can not properly open network devices... 

I don't suspect glibc, but I seem to remember that gcc was upgraded recently

Oh, yes. I have created tbz2 of the package on the system, where it used to work
recently (can't test it now, because gnome gui doesn't start there) and unpacked
it, but it croaks in exactly the same way...



Comment 2 Sascha Lucas 2005-09-20 06:14:35 UTC
Created attachment 68855 [details]
vmware-workstation-5.0.0.13124-r1.ebuild

Just if someone needs the r1 ebuild...
Comment 3 Chris Gianelloni (RETIRED) gentoo-dev 2005-09-20 06:15:24 UTC
(In reply to comment #1)
> Erm, it seems that something else is broken. I hav ejust managed to find old
> ebuild of 5.0.0.13124-r1 (fu*k, why can't old ebuilds live for a week or so
> before  they are purged from the tree ?!?) and it doesn't work either.

Ehh... because the -r1 ebuild had a security bug in it and should have been
removed.  I don't just arbitrarily remove things.  There's a good reason why I
do it.

Anyway, if you're having issues with the modules, the differences between these
ebuilds would *not* have possibly caused it.  After all, there's only a 1 line
change in the ebuild.

> It seems like module vmnet, when loaded, can not properly open network devices...

Try to emerge sync and reinstall vmware-workstation.  Also, be sure to recompile
your modules.  Follow the instructions given to you in the ebuild (add your suer
to the vmware group) and make sure you're in the group by running "groups" (you
probably need to log out and back in again), then try running vmware.

You cannot downgrade the vmware version and expect it to work, because the newer
version adds a file for udev to lock permissions to the vmware group.  Due to
CONFIG_PROTECT on /etc, this file will not be removed even if you downgrade or
remove VMware entirely.

As for the vmware-config.pl saying it is building the modules for 4.5, the
module scripts haven't changed since then, which is why it says that.  It isn't
building for an older version.  Since you didn't give me an actual error message
of any kind, I can only surmise that you probably are not in the vmware group, too.

Feel free to REOPEN this with more information and after adding your user
account to the vmware group if this is still an issue.
Comment 4 Chris Gianelloni (RETIRED) gentoo-dev 2005-09-20 06:16:31 UTC
Please do not *ever* attach an old ebuild and ask users to use it.  There's a
good reason why I removed it, and telling users to use an old ebuild will *not*
resolve the issue for them.
Comment 5 Sascha Lucas 2005-09-20 06:38:32 UTC
(In reply to comment #4)
> Please do not *ever* attach an old ebuild and ask users to use it.  There's a
> good reason why I removed it, and telling users to use an old ebuild will 
*not*
> resolve the issue for them.

I'm sorry for doing this... please excuse me. Next time I'll do it better.
Comment 6 Chris Gianelloni (RETIRED) gentoo-dev 2005-09-20 06:50:27 UTC
Not a problem.

Reading comment #3, you can see how giving the user an older ebuild wouldn't do
anything to fix their system.
Comment 7 brankob 2005-09-20 08:02:13 UTC
(In reply to comment #3)
> (In reply to comment #1)

> 
> Try to emerge sync and reinstall vmware-workstation.  Also, be sure to recompile
> your modules.  Follow the instructions given to you in the ebuild (add your suer
> to the vmware group) and make sure you're in the group by running "groups" (you
> probably need to log out and back in again), then try running vmware.


I did just that for the 71-st time now...

I'm memmber of group vmware as groups tells me:

*****************************
groups brane2

wheel floppy audio cdrom dialout video games portage scanner stats vmware users
*******************************


I did emerge "vmware-workstation" and started the "/opt/vmware/bin/vmware-config.pl"
Script goes through and finishes fine, but just at the finish it says:

**************
make: Leaving directory `/tmp/vmware-config1/vmnet-only'
The module loads perfectly in the running kernel.

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.


The configuration of VMware Workstation 5.0.0 build-13124 for Linux for this 
running kernel completed successfully.

You can now run VMware Workstation by invoking the following command: 
"/opt/vmware/bin/vmware".

Enjoy,

--the VMware team
*****************

So, just after it says that modules is O.K., it says that Vmware hasn't been
properly configured.

 
> You cannot downgrade the vmware version and expect it to work, because the newer
> version adds a file for udev to lock permissions to the vmware group.  Due to
> CONFIG_PROTECT on /etc, this file will not be removed even if you downgrade or
> remove VMware entirely.

If you think on /etc/udev/rules/60-vmware-something, I have removed it before
emerging back old "r1" (and did "udevstart" after that), besides that, once I
was in the vmware group, it should work even with "r1", shouldn't it.

BTW: I did downgrade my gcc one version down, just to see what happens. I
blocked 3.4.4-r1 and portage offered me 3.4.3 as the next highest.

I was warned that it isn't healthy to have kernel compiled with 3.4.4 and
applications compiled with lower level, so I compiled kernel also with 3.4.3.

Anyway,system behaves the same.

 
>Since you didn't give me an actual error message
> of any kind, I can only surmise that you probably are not in the vmware group,
too.

As said, I am in vmware group. As for the error code, there is only what vmware
reports after unsuccessfull start:

********************************************
vmware is installed, but it has not been (correctly) configured
for this system. To (re-)configure it, invoke the following command:
/opt/vmware/bin/vmware-config.pl.
*********************************************
Comment 8 Chris Gianelloni (RETIRED) gentoo-dev 2005-09-20 08:13:47 UTC
Remove /etc/vmware/not_configured
Comment 9 brankob 2005-09-20 09:40:20 UTC
(In reply to comment #8)
> Remove /etc/vmware/not_configured

I was just about to report that old vmware 4.5.x behaves exactly the same when I
saw your last suggestion. I tried it with 4.5.x- and it works !

I've emerged latest 5.0 and IT WORKS ! :o))))

Many thanks.

Just out of curiosity, what went wrong ?

Is it ebuild's fault or is it something with vmware-config ?

Anyway, thanks again. If you ever pass through Slovenia, you have beer and lunch
on my tab.  :o)




Comment 10 brankob 2005-09-20 09:41:41 UTC
BUG CLOSED :o) 

Comment 11 Chris Gianelloni (RETIRED) gentoo-dev 2005-09-20 10:43:27 UTC
not_configured is *supposed* to be removed by vmware-config.pl, but sometimes,
for some reason, it isn't...