Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 263560 - app-emulation/vmware-server-2.0.0.122956 `vmrun list': Error: The specified service provider was not found
Summary: app-emulation/vmware-server-2.0.0.122956 `vmrun list': Error: The specified s...
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo VMWare Bug Squashers [disabled]
URL:
Whiteboard:
Keywords:
: 302000 (view as bug list)
Depends on:
Blocks: 199514
  Show dependency tree
 
Reported: 2009-03-23 23:33 UTC by John W Eckhart
Modified: 2011-12-17 13:55 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John W Eckhart 2009-03-23 23:33:38 UTC
This bug references bug #246854 (http://bugs.gentoo.org/show_bug.cgi?id=246854). The same symptoms occur for the vmware server product: 

cmd: /opt/vmware/server/lib/bin/vmrun -T server -h https://localhost/sdk -u myuser -p mypass list
returns: Error: The specified service provider was not found

cat /tmp/vmware-root/vixWrapper-25999.log
Mar 23 19:29:51.239: app| Log for VixWrapper pid=25999 version=1 build=build-122956 option=Release
Mar 23 19:29:51.239: app| vixWrapper config file ./vixwrapper-config.txt not found
Mar 23 19:29:51.239: app| Failed to load wrapper configuration file
Mar 23 19:29:51.239: app| config points to non-existent implementation library './ws_server_esx-4/64bit/libvix.so'
Mar 23 19:29:51.239: app| config points to non-existent implementation library './ws_server_esx-4/64bit/libvix.so'
Mar 23 19:29:51.239: app| config points to non-existent implementation library './ws_server_esx-4/64bit/libvix.so'
Mar 23 19:29:51.239: app| config points to non-existent implementation library './ws_server_esx-4/64bit/libvix.so'
Mar 23 19:29:51.239: app| config points to non-existent implementation library './ws-5/64bit/libvix.so'
Mar 23 19:29:51.239: app| config points to non-existent implementation library './ws-3/64bit/libvix.so'
Mar 23 19:29:51.239: app| config points to non-existent implementation library './ws-3/64bit/libvix.so'
Mar 23 19:29:51.239: app| config points to non-existent implementation library './ws-2/64bit/libvix.so'
Mar 23 19:29:51.239: app| config points to non-existent implementation library './server-1/64bit/libvix.so'
Mar 23 19:29:51.239: app| No implementation found for service provider 10, apiVersion -1 installedVersion (null)
Mar 23 19:29:51.239: app| No Vix library found for provider 10 revision -1
Mar 23 19:29:51.239: app| No implementation libraries loaded, cannot call 'Vix_GetErrorText'

The workarounds mentioned in bug #246854 did not work here. I checked for a vix library to link to and found none:
find /opt/vmware/server -iname '*vix*' returns no results.


Reproducible: Always

Steps to Reproduce:
Comment 1 iceh 2009-04-25 11:05:59 UTC
I found a solution for this bug.

The installer file (VMware-server-2.0.1-156745.x86_64.tar.gz) (maybe the 32bit version, too) contains an additonal package for vix.

 vmware-vix.tar.gz

This isn't installed in the ebuild. You can install the file by hand. I notified Mike to add this to recent ebuilds for vmware server 2.0.
Comment 2 Sunit Das 2009-06-29 22:16:59 UTC
Ouch. This just bit me, too. This problem still exists for the 2.0.1.156745-r1 ebuild (I think).

The problem is that I have no idea what lib path I'm supposed to decompress that tarball into... that is, what is the '.' in './ws-5/32bit' ??

Also, it looks like a library is available for 32 & 64 bit installs of workstation 2-5 and server version 1. However, this bug is filed against a server 2 install. The tarball contains a 'VIServer-2.0.0/32bit' directory with stuff in it that looks right, but it doesn't seem that 'vmrun' invocations are attempting to traverse a libpath named thusly.

???

Has anyone else had positive progress on this issue within the last two months? I'm spinning my wheels...
Comment 3 Vadim Kuznetsov (RETIRED) gentoo-dev 2009-07-06 17:54:15 UTC
I've added vmware-vix and updated vmware-server ebuilds.
vmware-vix is still somewhat "beta". Please test and report patches, bug, comments, etc.

Thanks.

Comment 4 davidshen 2009-09-03 13:34:47 UTC
(In reply to comment #3)
> I've added vmware-vix and updated vmware-server ebuilds.
> vmware-vix is still somewhat "beta". Please test and report patches, bug,
> comments, etc.
> 
> Thanks.
> 

i am using gentoo amd64, and this bug still repos on vmware-server-2.0.1.156745-r2.

as mentioned in bug #246854, adding "/opt/vmware/vix/lib" to /etc/vmware/config could resolve this issue.
Comment 5 Vadim Kuznetsov (RETIRED) gentoo-dev 2009-09-03 14:57:40 UTC
(In reply to comment #4)

> as mentioned in bug #246854, adding "/opt/vmware/vix/lib" to /etc/vmware/config
> could resolve this issue.
> 

vmware-vix-1.6.2.156745-r2 ebuild is doing exactly it.

Comment 6 John W Eckhart 2009-09-03 23:03:22 UTC
I have not investigated why, but I can confirm that installing vmware-vix (either ver in portage) does not add vix.libdir to my /etc/vmware/config file. Should I open a new bug?
Comment 7 snIP3r 2009-09-16 16:19:34 UTC
hi!

i also encountered the issue. i have installed vmware-vix 1.6.2.156745-r2 and have the same error as the bug was opened.

thx
snIP3r
Comment 8 Vadim Kuznetsov (RETIRED) gentoo-dev 2009-09-16 16:30:25 UTC
(In reply to comment #6)
(In reply to comment #7)

Do you have /opt/vmware/vix/bin in your PATH?
Do you have /opt/vmware/vix/lib" in your /etc/vmware/config?
Comment 9 snIP3r 2009-09-17 19:36:13 UTC
(In reply to comment #8)
> (In reply to comment #6)
> (In reply to comment #7)
> 
> Do you have /opt/vmware/vix/bin in your PATH?
> Do you have /opt/vmware/vix/lib" in your /etc/vmware/config?
> 

after applying the modification it seems to work for me.
thx
snIP3r
Comment 10 Vadim Kuznetsov (RETIRED) gentoo-dev 2009-09-17 19:46:58 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #6)
> > (In reply to comment #7)
> > 
> > Do you have /opt/vmware/vix/bin in your PATH?
> > Do you have /opt/vmware/vix/lib" in your /etc/vmware/config?
> > 
> 
> after applying the modification it seems to work for me.
> thx
> snIP3r
> 

What modifications have you applied?
ebuild is creating new env.d file, so env-update; source /etc/profile or logout; login should take care of the PATH.
ebuild also updates /etc/vmware/config, so etc-update should take care of that as well.

So what was missing in your case?



Comment 11 snIP3r 2009-09-17 19:57:31 UTC
(In reply to comment #10)
> (In reply to comment #9)
> > (In reply to comment #8)
> > > (In reply to comment #6)
> > > (In reply to comment #7)
> > > 
> > > Do you have /opt/vmware/vix/bin in your PATH?
> > > Do you have /opt/vmware/vix/lib" in your /etc/vmware/config?
> > > 
> > 
> > after applying the modification it seems to work for me.
> > thx
> > snIP3r
> > 
> 
> What modifications have you applied?
> ebuild is creating new env.d file, so env-update; source /etc/profile or
> logout; login should take care of the PATH.
> ebuild also updates /etc/vmware/config, so etc-update should take care of that
> as well.
> 
> So what was missing in your case?
> 

i added

vix.libdir="/opt/vmware/vix/lib" to /etc/vmware/config

and everything runs fine now.
Comment 12 Fabio Rossi 2009-10-27 14:53:12 UTC
There is a problem during a reinstallation of vmware-vix. Let's assume that vmware-vix is installed on the system, so the file /etc/vmware/config contains the right line
  vix.libdir = ...

What happens during a re-emerge operation? During the pkg_prerm() phase the config line for vix is deleted leaving a bad configuration file for the vix API.
Comment 13 Vadim Kuznetsov (RETIRED) gentoo-dev 2009-10-27 17:37:01 UTC
(In reply to comment #12)
> There is a problem during a reinstallation of vmware-vix. Let's assume that
> vmware-vix is installed on the system, so the file /etc/vmware/config contains
> the right line
>   vix.libdir = ...
> 
> What happens during a re-emerge operation? During the pkg_prerm() phase the
> config line for vix is deleted leaving a bad configuration file for the vix
> API.
> 

What do you mean be "re-emerge"?
emerge -C vmware-vix; emerge vmware-vix
or just emerge -1v vmware-vix
?
Comment 14 Fabio Rossi 2009-10-27 17:58:45 UTC
(In reply to comment #13)
> What do you mean be "re-emerge"?
> emerge -C vmware-vix; emerge vmware-vix
> or just emerge -1v vmware-vix
> ?

just "emerge -1v vmware-vix"

Comment 15 Fabio Rossi 2010-01-28 21:06:14 UTC
*** Bug 302000 has been marked as a duplicate of this bug. ***
Comment 16 Vadim Kuznetsov (RETIRED) gentoo-dev 2011-12-17 13:55:27 UTC
vmware server was removed from the tree. Bug 374599.