First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 136544
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo VMWare Bug Squashers <vmware@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: gentoo@msux.cjb.net
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 136544 depends on: Show dependency tree
Show dependency graph
Bug 136544 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-06-12 07:58 0000
EBUILD USED:
vmware-workstation-tools 5.5.1

VMWARE TOOLS TAR USED:
VMwareTools-5.5.1-19175.tar.gz

KERNEL VERSION:
Linux 2.6.15-gentoo-r5

VIRTUAL KERNEL VERSION:
Linux 2.6.16-gentoo-r7 

PLATFORM:
Amd64

BUG:
After we created a directory to solve manually the issue reported in the
bug#136540, the vmware configuration script asks the user for a preferred
resolution, the user specifies one, the scripts makes a "preview", works for a
few seconds, and exits with this error message:

          Using 2.6.x kernel build system.
          /tmp/vmware-config8/vmhgfs-only/driver.c:3975: warning:
initialization 
          from incompatible pointer type

          X Window System Version 6.8.2
          Release Date: 9 February 2005
          X Protocol Version 11, Revision 0, Release 6.8.2
          Build Operating System: Linux 2.6.16-gentoo-r7 x86_64 [ELF] 
          Current Operating System: Linux va64 2.6.16-gentoo-r7 #1 Thu May 25 
          13:25:29 
          CEST 2006 x86_64
          Build Date: 26 May 2006
                  Before reporting problems, check http://wiki.X.Org
                  to make sure that you have the latest version.
          Module Loader present
          Markers: (--) probed, (**) from config file, (==) default setting,
                  (++) from command line, (!!) notice, (II) informational,
                  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
          (++) Log file: "/tmp/vmware-config8/XF86ConfigLog.11975", Time: Mon 
          Jun 12 15:56:20 2006
          (++) Using config file: "/tmp/vmware-config8/XF86Config.11975"
          (WW) VMWARE(0): Failed to set up write-combining range 
          (0xf0000000,0x1000000)
          Unable to start services for VMware Tools

          X is running fine with the new config file.

          VMware Tools is installed, but it has not been
          (correctly) configured for the running kernel.
          To (re-)configure it, invoke the following command:
          /opt/vmware/tools/bin/vmware-config-tools.pl.

          Unable to start services for VMware Tools

          Execution aborted.



The installation is cancelled and the configuration file is not written inside
/etc/conf.d (that is to say, "/etc/conf.d/vmware-tools" does not exist). 

Inside /etc/init.d there is an initialization script, but it does not work (if
we execute "/etc/init.d/vmware-tools start" it says "vmware init scripts not
found. Aborting"). 

However, if we start vmware, the services provided by vmware-tools are working
(we can use all resolutions, and so on; however, copying outside the virtual
machine and pasting inside the virtual machine... works ocasionally).

COMMENTS:
If we directly use the vmware-config-tools.pl from the tar (without using the
ebuild), the scripts works correctly; so there must be little errors inside the
ebuild.

Our virtual machine is available to perform the tests and tryings you may need,
do not hesitate contacting us.

------- Comment #1 From Chris Gianelloni (RETIRED) 2006-06-12 13:48:39 0000 -------
What if you rm /etc/vmware-tools/not_configured, then run the configuration
script?

------- Comment #2 From gentoo@msux.cjb.net 2006-06-13 01:44:26 0000 -------
Dear Chris

We have deleted /etc/vmware-tools/not_configured and re-run the configuration
script and:
- The script says VMware-Tools are configurated correctly, and that we have to
restart the X-Server to apply changes correctly.
- Executing "/etc/init.d/vmware-tools start" shows the same error as before.

However, we have seen that the script "/etc/init.d/vmware-tools" looks for
"/etc/vmware-tools/init.d/vmware", so we executed
    cd /etc/vmware-tools/init.d/
    ln -s vmware-tools vmware
And "/etc/init.d/vmware-tools start" starts the "VMware Tools services" showing
no errors.

Thanks for all!

------- Comment #3 From Chris Gianelloni (RETIRED) 2006-06-13 15:07:34 0000 -------
Thanks for investigating this and finding the solution for me.  I've now
updated the init script to look for the correct files.  Sorry about the
trouble.

First Last Prev Next    No search results available      Search page      Enter new bug