Bugzilla Bug 107930

This is with the new 5.5.0.16958 version. Running vmware-config.pl when the
vmware init service is not started gives the following:

Making sure services for VMware Workstation are stopped.

 * ERROR:  "vmware" has not yet been started.
Unable to stop services for VMware Workstation

Execution aborted.

steps to reproduce:

1. /etc/init.d/vmware stop
2. vmware-config.pl

Actual results: see above

Expected results: no error

To summarize my findings:

By calling "/etc/init.d/vmware start|stop" from vmware-config.pl you prevent the
script from running at all (unless the undocumented -skipstopstart argument is
given).

By calling "/etc/vmware/init.d/vmware start|stop" from vmware-config.pl you
integrate the script nicely with Gentoo... let the service be nicely shut down
on shutdown...

Hm, never mind. Can't reproduce on another machine. I think it was all my fault
after all.

Ah, got it now. Sorry for the mess.

The problem only occurs with the stable baselayout. No problem with baselayout-1.12.

Reopening.

lion ~ # emerge =baselayout-1.11*>/dev/null; /etc/init.d/vmware stop; echo $?
>>> Regenerating /etc/ld.so.cache...
 * ERROR:  "vmware" has not yet been started.
1
lion ~ # emerge =baselayout-1.12*>/dev/null; /etc/init.d/vmware stop; echo $?
>>> Regenerating /etc/ld.so.cache...
>>> Regenerating /etc/ld.so.cache...
>>> Regenerating /etc/ld.so.cache...
 * ERROR:  "vmware" has not yet been started.
0

This is caused by vmware-workstation-5.5.0.16958-config.patch  
  
If the Gentoo-VMware-initscript isn't started before running the vmware-config.pl script 
then /etc/init.d/vmware stop returns a 1 which make the vmware-config.pl script abort. The 
vmware-config.pl script should first check if the Gentoo-VMware-initscript is started before 
calling /etc/init.d/vmware stop. If the Gentoo-VMware-initscript isn't started it should call the 
original command (if (system(shell_string(db_get_answer('INITSCRIPTSDIR') . '/vmware')) etc. 
just in case VMware was started another way. 
  

Can you guys give some more info on your system? Like portage and base layout
you're using, because i dont have the described problem. Please attach emerge
info output.

(In reply to comment #4)
> Can you guys give some more info on your system? Like portage and base layout
> you're using, because i dont have the described problem. Please attach emerge
> info output.

See Comment #2. This happens only with the 1.11 baselayouts. 1.12 doesn't have
the problem.

Hi Gustavo,   
   
The version of the baselayout doesn't mather if the Gentoo-VMware-initscript is started  
before running vmware-config.pl. 
 
The version of the baselayout does mather if the Gentoo-VMware-initscript isn't started  
before running vmware-config.pl due to the returncode when stopping a stopped init-script. 
 
If you are running stable baselayout (1.11.13-r1). You can reproduce the problem by; 
# /etc/init.d/vmware stop 
# /opt/vmware/bin/vmware-config.pl 
 
 
$ emerge --info    
Portage 2.0.51.22-r3 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r2, 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 [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-r1    
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 ccache 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    

Bleh... didn't notice this was for the beta.  I can ignore this one, then.  ;]

For the meantime you might want to try 
vmware-config.pl -skipstopstart  
as a workaround. 

This problem still exists in vmware-workstation-5.5.0.18007-r1.  I've seen this
error in each of the Workstation 5.5 ebuilds.

Step One: Emerge vmware-workstation-5.5.0.18007-r1.  Successful.

Step Two: I try to start the VMWare services via the init script
(/etc/init.d/vmware start).  That doesn't work.  Tells me I need to run
/opt/vmware/workstation/bin/vmware-config.pl to build my kernel modules.

Step Three: Run /opt/vmware/workstation/bin/vmware-config.pl to build my kernel
modules.  The config script calls the init script to stop the VMWare services. 
This fails and stops the config script.  The init script is trying to stop a
service that hasn't been started.  This is a Gentoo introduced error.  The
VMWare init script was modified to make the VMWare init script look pretty like
normal Gentoo init script output.  The config script calls '/etc/init.d/vmware
stop' at the start of each execution.  The Gentoo intelligence of not stopping
services that aren't actually started breaks the vmware-config.pl script.

My Workaround: Replace Gentoo-modified /etc/init.d/vmware with VMWare-original
/etc/vmware/init.d/vmware.  The output isn't as pretty, but at least it works.

After that, VMWare runs just fine.

How this works:

/etc/init.d/vmware is a gentoo script that wrapps around
/etc/vmware/init.d/vmware that is vmware's provided init script.
/opt/vmware/bin/vmware-config.pl is vmware's script to generate kernel modules
for vmware.

To run a virtual machine one must run vmware-config.pl to setup kernel modules.
If the vmware services are already running this script will  stop the
/etc/vmware/init.d/vmware . This leeds to gentoo init system thinking that the
service is still running and all hell breaks.

To fix that i changed the vmware-config.pl script to call our wrapper, but seems
that for some users this is not working when the vmware-config.pl gets the reply
from the wrapper about the service not being started.

I cannot duplicate this so i guess it must be a baselayout issue, if it is we
need to depend on a newer version of base-layout.

looks to me like baselayout-1.12 is doing the wrong thing ... it should have
exited with 1, not with 0

The return code of 0 is correct as there was no error stopping the service as
it
was already stopped.

so what does `init.d start ; init.d start` return ?  both zeros ?

init.d start|stop would only return 1 if there was a problem starting or
stopping. If it's already marked started or stopped and we're asking to be
started or stopped then we don't count that as an error as we're already there.

init.d status returns 0 if started, otherwise 1 which could be used to work out
if a service is started or not before asking it to start or stop.

then you should make the same changes to the 1.11 branch so that we dont force
people to depend on the unstable 1.12 version

i hit this bug today when attempting to upgrade from 5.0 to the final 5.5
release now in portage...

clemens ~ # emerge --info && emerge -pv baselayout
Portage 2.0.51.22-r3 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r2,
2.6.14-ck6 x86_64)
=================================================================
System uname: 2.6.14-ck6 x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.6.13
ccache version 2.3 [enabled]
dev-lang/python:     2.3.5, 2.4.2
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-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O3 -march=athlon64 -pipe -funroll-all-loops -fpeel-loops -ftracer
-funswitch-loops -funit-at-a-time"
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/lib64/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=athlon64 -pipe -funroll-all-loops -fpeel-loops -ftracer
-funswitch-loops -funit-at-a-time"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.osuosl.org"
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="amd64 X a52 aac aalib acpi aim alsa apache2 artworkextra audiofile avi
bash-completion berkdb bitmap-fonts browserplugin bzip2 cd cddb cdr chroot
clamav crypt css cups curl dbus divx4linux dts dv dvd dvdr dvdread eds emboss
encode esd esdexif evo exif expat fam fame ffmpeg firefox flac flash foomaticdb
fortran gd gdbm gif glut gmp gnome gpm gstreamer gtk gtk2 hal idn ieee1394
imagemagick imlib java javascript jikes jpeg lcms ldap libcaca libwww live lzo
lzw lzw-tiff mad mbox mhash ming mng mono mozilla moznocompose moznoirc
moznomail moznosvg mp3 mpeg nautilus ncurses network nls nptl nptlonly nsplugin
nvidia offensive ogg opengl oss pam pcre pdflib perl pic png posix python
quicktime readline real samba sdl speex spell sqlite ssl svg tcltk tcpd theora
tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales videos
vorbis xine xml xml2 xmms xpm xv xvid xvmc zlib userland_GNU kernel_linux
elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS


These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] sys-apps/baselayout-1.11.13-r1  -bootstrap -build -static
+unicode 0 kB

Total size of downloads: 0 kB
clemens ~ #


no amount of /etc/vmware/init.d/vmware stop/start/restart or /etc/init.d/vmware
stop/start/restart allowed the script to run, always dumping with the same
message as given by original reporter.

is upgrading to ~arch baselayout a sure fix, or is that still up for
speculation?  any other known workarounds?

Roy synced the exit status behavior in current 1.11.x branch and will be in
next
baselayout-1.11.x release

Is a new baselayout stable planned soon?  I have more people reporting this to
me (not via bugs...) already and I think it'll only get worse until a fix is in
the tree (and stable).

*** Bug 114338 has been marked as a duplicate of this bug. ***

*** Bug 114816 has been marked as a duplicate of this bug. ***

Um, not sure this should be marked "fixed" - I'm seeing the problem with the
latest VMware ebuild  and baselayout-1.11.13-r1.

I also had to use the undocumented "skipstopstart" switch to work around this.

Try baselayout-1.11.14 

It is fixed in the latest ~arch baselayout.  Since VMware 5.5 is still in
~arch,
this is acceptable.  It does mean that without a newer stable baselayout
version
to resolve this, VMware 5.5 cannot go stable, however.

*** Bug 116322 has been marked as a duplicate of this bug. ***

*** Bug 116324 has been marked as a duplicate of this bug. ***

SOLVED with /opt/vmware/workstation/bin/vmware-config.pl -skipstopstart



emerge info
Portage 2.0.53 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r2,
2.6.14-ge ntoo-r5 x86_64)
=================================================================
System uname: 2.6.14-gentoo-r5 x86_64 Intel(R) Pentium(R) 4 CPU 3.20GHz
Gentoo Base System version 1.6.13
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[enabl ed]
dev-lang/python:     2.4.2
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-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -mtune=nocona -march=nocona -pipe -fomit-frame-pointer
-mfpmath=sse"
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/lib6 4/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/bind /var/qmail/alias /var/qmail/ control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -mtune=nocona -march=nocona -pipe -fomit-frame-pointer
-mfpmath=ss e"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distcc distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/ distributions/gentoo"
LANG="it_IT.UTF-8"
LC_ALL="it_IT.UTF-8"
LINGUAS="ar en_GB it"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X a52 aac aalib acpi alsa apache2 arts audiofile avi bash-completion
berkdb bidi bitmap-fonts bluetooth bonobo bzip2 caps cddb cdr cgi chroot cjk
cry pt cups curl dbus directfb dts dv dvd dvdr dvdread eds emacs emboss encode
esd e thereal evo exif expat fam fame fbcon ffmpeg firefox flac flash
foomaticdb fortr an freetype gcj gd gdbm gif gimp gimpprint glut gmp gnome
gnutls gphoto2 gpm gst reamer gtk gtk2 gtkhtml guile hal howl idn ieee1394
imagemagick imap imlib ithre ads jack java jpeg kde lcms libcaca libclamav
libedit libwww live lzo lzw lzw-ti ff mad matroska mhash mikmod ming mjpeg mng
motif mozilla mp3 mpeg mule musicbra inz mysql ncurses nfs nls nsplugin ogg
oggvorbis opengl oss pam pcre pda pdflib perl php pic png ppds python qmail qt
quicktime quotas readline real recode samb a scanner sdl slang smp sndfile
speex spell ssl svg symlink tetex theora threads  tiff truetype truetype-fonts
type1-fonts udev unicode usb v4l vcd vhosts vorbis  wxgtk1 wxwindows xine xml
xml2 xmms xpm xv xvid zlib linguas_ar linguas_en_GB l inguas_it userland_GNU
kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LDFLAGS, PORTDIR_OVERLAY







emerge -pv baselayout gentoo-sources vmware-workstation

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] sys-apps/baselayout-1.11.13-r1  -bootstrap -build -static
+unicode 0 kB
[ebuild   R   ] sys-kernel/gentoo-sources-2.6.14-r5  -build -doc +symlink
(-ultra1) 0 kB
[ebuild   R   ] app-emulation/vmware-workstation-5.5.0.18463  0 kB

*** Bug 117747 has been marked as a duplicate of this bug. ***

I have to REOPEN this since I had to take VMware 5.5 stable due to a security
bug.

*** Bug 117794 has been marked as a duplicate of this bug. ***

It's a problem for me unless I use the undocumented 'skipstopstart' option to
vmware-config.pl.

~ $> emerge -pv baselayout vmware-workstation

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] sys-apps/baselayout-1.11.13-r1  -bootstrap -build -static
-unicode 0 kB
[ebuild   R   ] app-emulation/vmware-workstation-5.5.1.19175  0 kB
-----

My 2

It's a problem for me unless I use the undocumented 'skipstopstart' option to
vmware-config.pl.

~ $> emerge -pv baselayout vmware-workstation

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] sys-apps/baselayout-1.11.13-r1  -bootstrap -build -static
-unicode 0 kB
[ebuild   R   ] app-emulation/vmware-workstation-5.5.1.19175  0 kB
-----

My 2¢

It should be mentioned that this also affects the vmware-player ebuild.

*** Bug 122322 has been marked as a duplicate of this bug. ***

*** Bug 123220 has been marked as a duplicate of this bug. ***

This has been fixed for a while, thanks to baselayout 1.11.14 being stable.

I'm still seeing the behaviour I submitted in Bug 122322, which was marked as a
duplicate of this.

I don't know if it really is a duplicate, so I haven't reopend either bug, but
if someone can let me know I'll reopen the right bug :)

Essentially, after running vmware-config.pl, I can't run 
# /etc/init.d/vmware start
Instead I first have to run
# /etc/vmware/init.d/vmware stop
and then
# /etc/init.d/vmware start

because /etc/vmware/init.d/vmware is started by vmware-config.pl and so
'/etc/init.d/vmware start' tries to start it but can't.

Also, "not_configured" is then added to /etc/vmware, meaning I have to delete
it by hand or re-run vmware-config.pl...

I'm using sys-apps/baselayout-1.12.0_pre16-r3 and
app-emulation/vmware-workstation-4.5.3.19414-r1

Perhaps I read your bug report incorrectly.  I thought that you were getting
the problem of vmware-config.pl failing because it could not stop services that
had not been started.  Is this not the case?  If not, feel free to REOPEN your
bug, as even though they have similar symptoms, they would be different.

*** Bug 134210 has been marked as a duplicate of this bug. ***

I just removed the lines in vmware-config.pl that prevented it from working et
voila:

=========================================================================
ruben@bombadil ~ $ diff /opt/vmware/workstation/bin/vmware-config.pl
/opt/vmware/workstation/bin/vmware-config.pl~
8465,8467c8465,8466
< #            error('Unable to stop services for ' . vmware_product_name() .
< #                  "\n\n");
<            ;
---
>             error('Unable to stop services for ' . vmware_product_name() .
>                   "\n\n");
==========================================================================

working just fine.