[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

I can't move automatically the mouse pointer outside of the virtual machine.

Posted on 2009-02-17
25
Medium Priority
?
2,203 Views
Last Modified: 2013-12-06
I'm running my physical installation of Debian Lenny on Vista Home Basic with VMware Workstation 6.5.  I've installed the VMware tools,but as you can see a lot of errors are happened :

Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]

Stopping VMware Tools services in the virtual machine:
   Guest operating system daemon:                                      done
   Virtual Printing daemon:                                            done

None of the pre-built vmmemctl modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmmemctl module
for your system (you need to have a C compiler installed on your system)?
[yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The memory manager driver (vmmemctl module) is used by VMware host software to
efficiently reclaim memory from a virtual machine.
If the driver is not available, VMware host software may instead need to swap
guest memory to disk, which may reduce performance.
The rest of the software provided by VMware Tools is designed to work
independently of this feature.
If you want the memory management feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.
These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]

None of the pre-built vmhgfs modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmhgfs module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The filesystem driver (vmhgfs module) is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
independently of this feature.

If you wish to have the shared folders feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.
These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]

None of the pre-built vmxnet modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmxnet module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The fast network device driver (vmxnet module) is used only for our fast
networking interface. The rest of the software provided by VMware Tools is
designed to work independently of this feature.
If you wish to have the fast network driver enabled, you can install the driver
by running vmware-config-tools.pl again after making sure that gcc, binutils,
make and the kernel sources for your running kernel are installed on your
machine. These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]

None of the pre-built vmblock modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmblock module
for your system (you need to have a C compiler installed on your system)?
[yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The vmblock module enables dragging or copying files from within a host and
dropping or pasting them onto your guest (host to guest drag and drop and file
copy/paste).  The rest of the software provided by VMware Tools is designed to
work independently of this feature (including guest to host drag and drop and
file copy/paste).

If you would like the host to guest drag and drop and file copy/paste features,
you can install the driver by running vmware-config-tools.pl again after making
sure that gcc, binutils, make and the kernel sources for your running kernel
are installed on your machine. These packages are available on your
distribution's installation CD.
[ Press Enter key to continue ]

[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
creates backups of virtual machines. Please refer to the VMware Knowledge Base
for more details on this capability. Do you wish to enable this feature?
[no] yes

None of the pre-built vmsync modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmsync module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The file system sync driver (vmsync) is only used to create safe backups of the
virtual machine. The rest of the software provided by VMware Tools is designed
to work independently of this feature.
If you wish to have the vmsync feature, you can install the driver by running
vmware-config-tools.pl again after making sure that gcc, binutils, make and the
kernel sources for your running kernel are installed on your machine. These
packages are available on your distribution's installation CD.
[ Press Enter key to continue ]

None of the pre-built vmci modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmci module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The communication service is used in addition to the standard communication
between the guest and the host.  The rest of the software provided by VMware
Tools is designed to work independently of this feature.
If you wish to have the VMCI feature, you can install the driver by running
vmware-config-tools.pl again after making sure that gcc, binutils, make and the
kernel sources for your running kernel are installed on your machine. These
packages are available on your distribution's installation CD.
[ Press Enter key to continue ]

Detected X.org version 7.3.2.

Do you want to change the starting screen display size? (yes/no) [no]

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10)
Current Operating System: Linux marietto2009 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
Build Date: 09 January 2009  02:57:16AM
 
      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-config0/XF86ConfigLog.4160", Time: Wed Feb 18 01:20:39 2009
(++) Using config file: "/tmp/vmware-config0/XF86Config.4160"
(II) Module "ramdac" already built-in
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server

X is running fine with the new config file.

FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.
   Checking acpi hot plug                                              done
Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                                   done
   Guest operating system daemon:                                      done
   Virtual Printing daemon:                                            done

The configuration of VMware Tools 6.5.0 build-118166 for Linux for this running
kernel completed successfully.

You must restart your X session before any mouse or graphics changes take
effect.

You can now run VMware Tools by invoking the following command:
"/usr/bin/vmware-toolbox" during an X server session.

To enable advanced X features (e.g., guest resolution fit, drag and drop, and
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.

If the virtual printer feature is enabled, you will need to restart the CUPS
service to make use of this feature.

Enjoy,

--the VMware team

marietto2009:/home/marietto/Downloads/vmware-tools-distrib# ps ax
  PID TTY      STAT   TIME COMMAND
    1 ?        Ss     0:02 init [2]  
    2 ?        S<     0:00 [kthreadd]
    3 ?        S<     0:00 [migration/0]
    4 ?        S<     0:00 [ksoftirqd/0]
    5 ?        S<     0:00 [watchdog/0]
    6 ?        S<     0:00 [events/0]
    7 ?        S<     0:00 [khelper]
   39 ?        S<     0:00 [kblockd/0]
   41 ?        S<     0:00 [kacpid]
   42 ?        S<     0:00 [kacpi_notify]
  173 ?        S<     0:00 [kseriod]
  210 ?        S      0:00 [pdflush]
  211 ?        S      0:00 [pdflush]
  212 ?        S<     0:00 [kswapd0]
  213 ?        S<     0:00 [aio/0]
  780 ?        S<     0:00 [ksuspend_usbd]
  784 ?        S<     0:00 [khubd]
  949 ?        S<     0:00 [scsi_eh_0]
  998 ?        S<     0:00 [ata/0]
  999 ?        S<     0:00 [ata_aux]
 1062 ?        S<     0:00 [kjournald]
 1138 ?        S<s    0:01 udevd --daemon
 1560 ?        S<     0:00 [kgameportd]
 1672 ?        S<     0:00 [kpsmoused]
 2094 ?        Ss     0:00 /usr/lib/vmware-tools/sbin32/vmware-guestd --backgrou
 2123 ?        Ss     0:00 /sbin/portmap
 2134 ?        Ss     0:00 /sbin/rpc.statd
 2396 ?        S<     0:00 [kondemand/0]
 2433 ?        Sl     0:00 /usr/sbin/rsyslogd -c3
 2444 ?        Ss     0:00 /usr/sbin/acpid
 2454 ?        Ss     0:00 /usr/bin/dbus-daemon --system
 2466 ?        Ss     0:01 avahi-daemon: running [marietto2009.local]
 2467 ?        Ss     0:00 avahi-daemon: chroot helper
 2738 ?        Ss     0:00 tpvmlpd
 2765 ?        Ss     0:00 /usr/sbin/cupsd
 3032 ?        Ss     0:00 /usr/sbin/exim4 -bd -q30m
 3042 ?        Ss     0:00 /usr/sbin/kerneloops
 3056 ?        Ss     0:00 /usr/sbin/dhcdbd --system
 3067 ?        Ss     0:00 /usr/sbin/hald
 3068 ?        S      0:00 hald-runner
 3086 ?        S      0:00 hald-addon-input: Listening on /dev/input/event2 /dev
 3094 ?        S      0:00 hald-addon-acpi: listening on acpid socket /var/run/a
 3095 ?        S      0:00 hald-addon-storage: no polling on /dev/fd0 because it
 3097 ?        S      0:00 hald-addon-storage: polling /dev/hda (every 2 sec)
 3109 ?        Ssl    0:00 /usr/sbin/NetworkManager --pid-file /var/run/NetworkM
 3117 ?        Ss     0:00 /usr/sbin/NetworkManagerDispatcher --pid-file /var/ru
 3149 ?        Ss     0:00 /usr/sbin/gdm
 3156 ?        S      0:00 /usr/sbin/gdm
 3160 tty7     Rs+    0:05 /usr/X11R6/bin/X :0 -audit 0 -auth /var/lib/gdm/:0.Xa
 3163 ?        Ss     0:00 /usr/bin/system-tools-backends
 3182 ?        S      0:00 /sbin/dhclient -1 -lf /var/lib/dhcp3/dhclient.eth0.le
 3188 ?        Ss     0:00 /usr/sbin/atd
 3208 ?        Ss     0:00 /usr/sbin/cron
 3250 ?        Ss     0:00 /usr/sbin/apache2 -k start
 3291 tty1     Ss+    0:00 /sbin/getty 38400 tty1
 3292 tty2     Ss+    0:00 /sbin/getty 38400 tty2
 3294 tty3     Ss+    0:00 /sbin/getty 38400 tty3
 3299 tty4     Ss+    0:00 /sbin/getty 38400 tty4
 3301 tty5     Ss+    0:00 /sbin/getty 38400 tty5
 3304 tty6     Ss+    0:00 /sbin/getty 38400 tty6
 3319 ?        S      0:00 /usr/sbin/apache2 -k start
 3320 ?        S      0:00 /usr/sbin/apache2 -k start
 3321 ?        S      0:00 /usr/sbin/apache2 -k start
 3322 ?        S      0:00 /usr/sbin/apache2 -k start
 3323 ?        S      0:00 /usr/sbin/apache2 -k start
 3342 ?        S      0:00 /usr/lib/libgconf2-4/gconfd-2 11
 3344 ?        S      0:00 /usr/bin/gnome-keyring-daemon -d --login
 3345 ?        Ssl    0:00 x-session-manager
 3393 ?        S      0:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/sea
 3394 ?        Ss     0:00 /usr/bin/dbus-daemon --fork --print-pid 6 --print-add
 3400 ?        Ss     0:00 /usr/bin/seahorse-agent --execute x-session-manager
 3403 ?        Sl     0:00 gnome-settings-daemon
 3422 ?        Ss     0:00 gnome-screensaver
 3423 ?        S      0:00 /usr/bin/metacity --sm-client-id=default0
 3425 ?        S      0:01 gnome-panel --sm-client-id default1
 3427 ?        S      0:01 nautilus --no-default-window --sm-client-id default2
 3433 ?        Ssl    0:00 /usr/lib/bonobo-activation/bonobo-activation-server -
 3439 ?        S      0:00 bluetooth-applet --singleton
 3443 ?        S      0:00 update-notifier
 3447 ?        S      0:00 /usr/lib/gnome-vfs-2.0/gnome-vfs-daemon
 3448 ?        S      0:03 /usr/lib/vmware-tools/bin/xorg71/vmware-user
 3450 ?        S      0:00 /usr/bin/python /usr/bin/system-config-printer-applet
 3454 ?        S      0:00 kerneloops-applet
 3457 ?        S      0:00 nm-applet --sm-disable
 3458 ?        Ss     0:00 gnome-power-manager
 3461 ?        Ss     0:00 /usr/lib/gnome-volume-manager/gnome-volume-manager --
 3474 ?        S      0:00 /usr/lib/nautilus-cd-burner/mapping-daemon
 4016 ?        Sl     0:00 /usr/lib/gnome-applets/mixer_applet2 --oaf-activate-i
 4091 ?        Sl     0:00 gnome-terminal
 4093 ?        S      0:00 gnome-pty-helper
 4094 pts/0    Ss     0:00 bash
 4106 pts/0    S      0:00 su
 4107 pts/0    S      0:00 bash
 4725 pts/0    R+     0:00 ps ax

The problem is that everytime I want to go out of the virtual machine I can't move the mouse pointer outside it,but I should press CTRL+ALT. That's very annoying. What I can do ?
0
Comment
Question by:marietto2008
  • 12
  • 11
  • +1
25 Comments
 
LVL 6

Expert Comment

by:Justin_W_Chandler
ID: 23666063
FIRST -- good luck. SECOND -- maybe you could consider trying Virtual Box instead of VMWare... This is a simple solution to your problem, unless you're heart's set on using VMWare to run Linux.
0
 
LVL 4

Expert Comment

by:philtpaik
ID: 23666070
I didn't read everything you wrote except for the first couple sentences and the last question...so forgive me if I didn't answer many of your questions except the title and last one =)

I could be wrong on this but I think hitting a hotkey to get out of "captured" mode is a must.

To change the setting, try going to the Edit menu and choose Preferences.

I believe you only have 3 choices to change the combination of the hotkey.

hope this helps
0
 
LVL 8

Expert Comment

by:agamal
ID: 23667904
moving out your mouse without pressing keys working only if you have windows or gui linux like Gnome or KDE

not only this you will need to install vmware drivers using

VM => install Vmware tools

then it will work with you


i have ubuntu (KDE) and windows xp both on VMware and both have VMware tools installed
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
LVL 2

Author Comment

by:marietto2008
ID: 23668484
1) Virtual Box can't run a physical installation of Linux
2) If the Vmware Tools are installed correctly I don't need to hit hotkeys to get out of "captured" mode,because it's done automatically.
3) I've installed the VMware tools by clicking on VM / Install VMware Tools
4) I'm running Gnome on the physical installation of Debian
0
 
LVL 8

Expert Comment

by:agamal
ID: 23668534
so ... what you need else ....
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23668635
There is something wrong with the installation of the VMware Tools because I have to press CTRL+ALT each time  I want to go out of the virtual machine,with Ubuntu it worked like this.
0
 
LVL 8

Expert Comment

by:agamal
ID: 23668653
i can tell that i have 2 ubuntu installation
one is the desktop installation and this one working fine after installing the tool

the other one is the server edition and it is not always working right .... i am testing now my server edition and will get back to you
0
 
LVL 8

Expert Comment

by:agamal
ID: 23668755
working fine with me

check settings in the screen shot

ScreenShot035.gif
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23668870
My settings are like yours but it doesn't works for me. In your screenshot I've read "These options are effective only when VMware Tools is running in the Virtual Machine",it doesn't works for me maybe because VMware Tools is not running well in my Virtual Machine ?
0
 
LVL 8

Expert Comment

by:agamal
ID: 23668877
that is why i asked you to install it ....... if you can ... a new clean installation and then vmware tools will be more clear to determine where is the error
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23668980
but a clean installation of the whole physical o/s takes a lot of time. I will do it as soon as possible.
0
 
LVL 8

Expert Comment

by:agamal
ID: 23669471
I will be waiting ...............  :D

Good Luck
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23671126
I'm trying to install the open vmware tools,but I have two versions of gcc already installed (4.1 and 4.3) and I'm having some troubles as you can see :

marietto2009:/home/marietto/Downloads/vmware-tools-distrib/bin# cd /usr/src

marietto2009:/usr/src# ls

gcc-4.1 linux-headers-2.6.26-1-common-vserver
gcc-4.3 linux-headers-2.6.26-1-common-xen
linux linux-headers-2.6.26-1-openvz-686
linux-headers-2.6.26-1-486 linux-headers-2.6.26-1-vserver-686
linux-headers-2.6.26-1-686 linux-headers-2.6.26-1-vserver-686-bigmem
linux-headers-2.6.26-1-686-bigmem linux-headers-2.6.26-1-xen-686
linux-headers-2.6.26-1-amd64 linux-kbuild-2.6.26
linux-headers-2.6.26-1-common linux-source-2.6.26.tar.bz2
linux-headers-2.6.26-1-common-openvz open-vm.tar.bz2

marietto2009:/usr/src# tar -jxf open-vm.tar.bz2

marietto2009:/usr/src# cd /usr/src/modules/open-vm

marietto2009:/usr/src/modules/open-vm# ls

debian Makefile modules

marietto2009:/usr/src/modules/open-vm# make

make -C modules/linux/pvscsi
Using 2.6.x kernel build system.
make[1]: Entering directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
/usr/src/modules/open-vm/modules/linux/pvscsi/Makefile:115: *** Inappropriate build environment: you wanted to use gcc version 4.3.2 while kernel attempts to use gcc version 4.1.3.
/usr/src/modules/open-vm/modules/linux/pvscsi/Makefile:117: *** For proper build you'll have to replace gcc-4.1 with symbolic link to cc. Stop.
make[2]: *** [_module_/usr/src/modules/open-vm/modules/linux/pvscsi] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
make[1]: *** [pvscsi.ko] Error 2
make[1]: Leaving directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make: *** [build] Error 2

what to do ?

Thanks.
0
 
LVL 8

Accepted Solution

by:
agamal earned 1500 total points
ID: 23671277
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23671395
marietto2009:/usr/src/modules/open-vm# apt-get install build-essential

build-essential is updated.

marietto2009:/usr/src/modules/open-vm# apt-get install linux-headers-`uname -r`

linux-headers-2.6.26-1-686 is updated.
linux-headers-2.6.26-1-686 is ready for the manual installation.

Can you tell me how to replace gcc-4.1 with a symbolic link to cc ?

Thanks.
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23671963
I've fixed the old error and now I have another one :

marietto2009: cd /usr/bin
marietto2009: rm gcc
marietto2009: ln -s /usr/bin/gcc-4.1 /usr/bin/gcc
marietto2009: /usr/src/modules/open-vm# make

make -C modules/linux/pvscsi
Using 2.6.x kernel build system.
make[1]: Entering directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
  Building modules, stage 2.
  MODPOST 1 modules
make[2]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
make -C $PWD SRCROOT=$PWD/. postbuild
make[2]: Entering directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make[2]: `postbuild' is up to date.
make[2]: Leaving directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
cp -f pvscsi.ko ./../pvscsi.o
make[1]: Leaving directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make -C modules/linux/vmblock
Using standalone build system.
./autoconf/geninclude.c:19:28: error: linux/autoconf.h: No such file or directory
make[1]: Entering directory `/usr/src/modules/open-vm/modules/linux/vmblock'
.././autoconf/geninclude.c:19:28: error: linux/autoconf.h: No such file or directory
make[2]: Entering directory `/usr/src/modules/open-vm/modules/linux/vmblock/driver-'
Dependencies for .././linux/super.c
In file included from .././linux/super.c:26:
.././include/driver-config.h:42:5: error: #error "No Module support in this kernel.  Please configure with CONFIG_MODULES"
make[2]: *** [super.d] Error 1
make[2]: Leaving directory `/usr/src/modules/open-vm/modules/linux/vmblock/driver-'
make[1]: *** [deps] Error 2
make[1]: Leaving directory `/usr/src/modules/open-vm/modules/linux/vmblock'
make: *** [build] Error 2
0
 
LVL 8

Expert Comment

by:agamal
ID: 23672186
have you checked the link above .... it explains how to do that .....
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23672741
after to have made :

marietto2009: cd /usr/bin
marietto2009: rm gcc
marietto2009: ln -s /usr/bin/gcc-4.1 /usr/bin/gcc

I've tried to reconfigure vmware tools :

marietto2009:/home/marietto/Downloads/vmware-tools-distrib/bin# ./vmware-config-tools.pl

Stopping VMware Tools services in the virtual machine:
   Guest operating system daemon:                                      done
   Virtual Printing daemon:                                            done
None of the pre-built vmmemctl modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmmemctl module
for your system (you need to have a C compiler installed on your system)?
[yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.26-1-686/build/include]

Extracting the sources of the vmmemctl module.

Building the vmmemctl module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmemctl-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
  CC [M]  /tmp/vmware-config0/vmmemctl-only/backdoorGcc32.o
  CC [M]  /tmp/vmware-config0/vmmemctl-only/os.o
  CC [M]  /tmp/vmware-config0/vmmemctl-only/vmballoon.o
  LD [M]  /tmp/vmware-config0/vmmemctl-only/vmmemctl.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config0/vmmemctl-only/vmmemctl.mod.o
  LD [M]  /tmp/vmware-config0/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-config0/vmmemctl-only'
The vmmemctl module loads perfectly into the running kernel.

None of the pre-built vmhgfs modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmhgfs module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmhgfs module.

Building the vmhgfs module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmhgfs-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
  CC [M]  /tmp/vmware-config0/vmhgfs-only/backdoor.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/backdoorGcc32.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/bdhandler.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/cpName.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/cpNameLinux.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/cpNameLite.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/dentry.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/dir.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/file.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/filesystem.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/fsutil.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/hgfsBd.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/hgfsEscapeLinux.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/hgfsUtil.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/inode.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/kernelStubsLinux.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/link.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/messageBackdoor.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/message.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/module.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/page.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/request.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/rpcout.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/staticEscape.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/stubs.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/super.o
  LD [M]  /tmp/vmware-config0/vmhgfs-only/vmhgfs.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o
  LD [M]  /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-config0/vmhgfs-only'
The vmhgfs module loads perfectly into the running kernel.

None of the pre-built vmxnet modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmxnet module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmxnet module.

Building the vmxnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmxnet-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
  CC [M]  /tmp/vmware-config0/vmxnet-only/vmxnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config0/vmxnet-only/vmxnet.mod.o
  LD [M]  /tmp/vmware-config0/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-config0/vmxnet-only'
The vmxnet module loads perfectly into the running kernel.

update-initramfs: Generating /boot/initrd.img-2.6.26-1-686
None of the pre-built vmblock modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmblock module
for your system (you need to have a C compiler installed on your system)?
[yes]

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmblock-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/block.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/control.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/dentry.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/file.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/inode.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/module.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/stubs.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/super.o
  LD [M]  /tmp/vmware-config0/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config0/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/vmware-config0/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config0/vmblock-only'
The vmblock module loads perfectly into the running kernel.

[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
creates backups of virtual machines. Please refer to the VMware Knowledge Base
for more details on this capability. Do you wish to enable this feature?
[no]

None of the pre-built vmci modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmci module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmci-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
  CC [M]  /tmp/vmware-config0/vmci-only/kernelStubsLinux.o
  CC [M]  /tmp/vmware-config0/vmci-only/vmciDatagram.o
  CC [M]  /tmp/vmware-config0/vmci-only/vmci_drv.o
  CC [M]  /tmp/vmware-config0/vmci-only/vmciEvent.o
  CC [M]  /tmp/vmware-config0/vmci-only/vmciGuestDs.o
  CC [M]  /tmp/vmware-config0/vmci-only/vmciGuestKernelIf.o
  CC [M]  /tmp/vmware-config0/vmci-only/vmciKernelIf.o
  CC [M]  /tmp/vmware-config0/vmci-only/vmciProcess.o
  CC [M]  /tmp/vmware-config0/vmci-only/vmciQueuePair.o
  CC [M]  /tmp/vmware-config0/vmci-only/vmciUtil.o
  LD [M]  /tmp/vmware-config0/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config0/vmci-only/vmci.mod.o
  LD [M]  /tmp/vmware-config0/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-config0/vmci-only'
The vmci module loads perfectly into the running kernel.

None of the pre-built vsock modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vsock module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vsock module.

Building the vsock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vsock-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
  CC [M]  /tmp/vmware-config0/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/vmware-config0/vsock-only/linux/driverLog.o
  CC [M]  /tmp/vmware-config0/vsock-only/linux/util.o
  CC [M]  /tmp/vmware-config0/vsock-only/linux/vsockAddr.o
  LD [M]  /tmp/vmware-config0/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Subscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_DeviceGet" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyFromQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Detach" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Alloc" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Unsubscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyToQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
  CC      /tmp/vmware-config0/vsock-only/vsock.mod.o
  LD [M]  /tmp/vmware-config0/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config0/vsock-only'
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/vsock.o': -1 Unknown symbol in module
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel.  You may want to
rebuild a kernel based on that directory, or specify another directory.

The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and
host.  The rest of this software provided by VMware Tools is designed to work
independently of this feature.  If you wish to have the VSOCK feature  you can
install the driver by running vmware-config-tools.pl again after making sure
that gcc, binutils, make and the kernel sources for your running kernel are
installed on your machine. These packages are available on your distribution's
installation CD.
[ Press the Enter key to continue.]



Detected X.org version 7.3.2.



Do you want to change the starting screen display size? (yes/no) [no]


X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10)
Current Operating System: Linux marietto2009 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
Build Date: 09 January 2009  02:57:16AM
 
      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-config1/XF86ConfigLog.6717", Time: Wed Feb 18 17:04:17 2009
(++) Using config file: "/tmp/vmware-config1/XF86Config.6717"
(II) Module "ramdac" already built-in
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server

X is running fine with the new config file.

FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.
   Checking acpi hot plug                                              done
Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                                   done
   Guest filesystem driver:                                            done
   Mounting HGFS shares:                                              failed
   Guest memory manager:                                               done
   Guest vmxnet fast network device:                                   done
   VM communication interface:                                         done
   Blocking file system:                                               done
   VMware User Agent (vmware-user):                                    done
   Guest operating system daemon:                                      done
   Virtual Printing daemon:                                            done

The configuration of VMware Tools 6.5.0 build-118166 for Linux for this running
kernel completed successfully.

You must restart your X session before any mouse or graphics changes take
effect.

You can now run VMware Tools by invoking the following command:
"/usr/bin/vmware-toolbox" during an X server session.

To enable advanced X features (e.g., guest resolution fit, drag and drop, and
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.

To use the vmxnet driver, restart networking using the following commands:
/etc/init.d/networking stop
rmmod pcnet32
rmmod vmxnet
modprobe vmxnet
/etc/init.d/networking start

If the virtual printer feature is enabled, you will need to restart the CUPS
service to make use of this feature.

Enjoy,

--the VMware team

but the mouse still doesn't go outside of the virtual machine automatically
0
 
LVL 8

Expert Comment

by:agamal
ID: 23673890
I don't know which version of ubuntu you have ... could you please have a look on this and tell me what do you think

http://blog.wolffmyren.com/2008/11/03/vmware-tools-dont-work-in-ubuntu-810/
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23674495
I've read it very well. It seems that there is a bug on the Debian Lenny,that has been fixed on ubuntu 8.10. I think that we should try to run the open vm tools instead of the official ones. For this reason we can restart from here :

I've fixed the old error and now I have another one :

marietto2009: cd /usr/bin
marietto2009: rm gcc
marietto2009: ln -s /usr/bin/gcc-4.1 /usr/bin/gcc
marietto2009: /usr/src/modules/open-vm# make

make -C modules/linux/pvscsi
Using 2.6.x kernel build system.
make[1]: Entering directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
  Building modules, stage 2.
  MODPOST 1 modules
make[2]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
make -C $PWD SRCROOT=$PWD/. postbuild
make[2]: Entering directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make[2]: `postbuild' is up to date.
make[2]: Leaving directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
cp -f pvscsi.ko ./../pvscsi.o
make[1]: Leaving directory `/usr/src/modules/open-vm/modules/linux/pvscsi'
make -C modules/linux/vmblock
Using standalone build system.
./autoconf/geninclude.c:19:28: error: linux/autoconf.h: No such file or directory
make[1]: Entering directory `/usr/src/modules/open-vm/modules/linux/vmblock'
.././autoconf/geninclude.c:19:28: error: linux/autoconf.h: No such file or directory
make[2]: Entering directory `/usr/src/modules/open-vm/modules/linux/vmblock/driver-'
Dependencies for .././linux/super.c
In file included from .././linux/super.c:26:
.././include/driver-config.h:42:5: error: #error "No Module support in this kernel.  Please configure with CONFIG_MODULES"
make[2]: *** [super.d] Error 1
make[2]: Leaving directory `/usr/src/modules/open-vm/modules/linux/vmblock/driver-'
make[1]: *** [deps] Error 2
make[1]: Leaving directory `/usr/src/modules/open-vm/modules/linux/vmblock'
make: *** [build] Error 2
0
 
LVL 8

Expert Comment

by:agamal
ID: 23681145
have a look
0
 
LVL 8

Expert Comment

by:agamal
ID: 23681150
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23686442
I've reinstalled everything and I've tried this :

http://www.howtogeek.com/howto/ubuntu/install-vmware-tools-on-ubuntu-edgy-eft/

and this is what's happened :

marietto2009:/tmp/vmware-tools-distrib# ./vmware-install.pl

Creating a new VMware Tools installer database using the tar4 format.

Installing VMware Tools.

In which directory do you want to install the binary files?
[/usr/bin]

What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc]

What is the directory that contains the init scripts?
[/etc/init.d]

In which directory do you want to install the daemon files?
[/usr/sbin]

In which directory do you want to install the library files?
[/usr/lib/vmware-tools]

The path "/usr/lib/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes]

In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]

The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]

The installation of VMware Tools 6.5.0 build-118166 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".

Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]


Stopping VMware Tools services in the virtual machine:
   Guest operating system daemon:                                      done
   Virtual Printing daemon:                                            done
None of the pre-built vmmemctl modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmmemctl module
for your system (you need to have a C compiler installed on your system)?
[yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The memory manager driver (vmmemctl module) is used by VMware host software to
efficiently reclaim memory from a virtual machine.
If the driver is not available, VMware host software may instead need to swap
guest memory to disk, which may reduce performance.
The rest of the software provided by VMware Tools is designed to work
independently of this feature.
If you want the memory management feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.
These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]

None of the pre-built vmhgfs modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmhgfs module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The filesystem driver (vmhgfs module) is used only for the shared folder
feature. The rest of the software provided by VMware Tools is designed to work
independently of this feature.

If you wish to have the shared folders feature, you can install the driver by
running vmware-config-tools.pl again after making sure that gcc, binutils, make
and the kernel sources for your running kernel are installed on your machine.
These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]

None of the pre-built vmxnet modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmxnet module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The fast network device driver (vmxnet module) is used only for our fast
networking interface. The rest of the software provided by VMware Tools is
designed to work independently of this feature.
If you wish to have the fast network driver enabled, you can install the driver
by running vmware-config-tools.pl again after making sure that gcc, binutils,
make and the kernel sources for your running kernel are installed on your
machine. These packages are available on your distribution's installation CD.
[ Press Enter key to continue ]

None of the pre-built vmblock modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmblock module
for your system (you need to have a C compiler installed on your system)?
[yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The vmblock module enables dragging or copying files from within a host and
dropping or pasting them onto your guest (host to guest drag and drop and file
copy/paste).  The rest of the software provided by VMware Tools is designed to
work independently of this feature (including guest to host drag and drop and
file copy/paste).

If you would like the host to guest drag and drop and file copy/paste features,
you can install the driver by running vmware-config-tools.pl again after making
sure that gcc, binutils, make and the kernel sources for your running kernel
are installed on your machine. These packages are available on your
distribution's installation CD.
[ Press Enter key to continue ]

[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
creates backups of virtual machines. Please refer to the VMware Knowledge Base
for more details on this capability. Do you wish to enable this feature?
[no]

None of the pre-built vmci modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmci module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

Your kernel was built with "gcc" version "4.1.3", while you are trying to use
"/usr/bin/gcc" version "4.3.2". This configuration is not recommended and
VMware Tools may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel. Do you want to go with compiler
"/usr/bin/gcc" version "4.3.2" anyway? [no]

The communication service is used in addition to the standard communication
between the guest and the host.  The rest of the software provided by VMware
Tools is designed to work independently of this feature.
If you wish to have the VMCI feature, you can install the driver by running
vmware-config-tools.pl again after making sure that gcc, binutils, make and the
kernel sources for your running kernel are installed on your machine. These
packages are available on your distribution's installation CD.
[ Press Enter key to continue ]



Detected X.org version 7.3.2.


Please choose one of the following display sizes that X will start with (1 -
29):

[1]  "320x200"
[2]  "320x240"
[3]  "400x300"
[4]  "512x384"
[5]  "640x400"
[6]  "640x480"
[7]  "720x480"
[8]  "800x480"
[9]  "854x480"
[10]  "720x576"
[11]  "800x600"
[12]  "1024x768"
[13]  "1280x720"
[14]  "1280x768"
[15]  "1152x864"
[16]  "1280x800"
[17]< "1366x768"
[18]  "1280x960"
[19]  "1440x900"
[20]  "1280x1024"
[21]  "1400x1050"
[22]  "1680x1050"
[23]  "1600x1200"
[24]  "1920x1080"
[25]  "1920x1200"
[26]  "1920x1440"
[27]  "2048x1536"
[28]  "2560x1600"
[29]  "2560x1920"
Please enter a number between 1 and 29:

[17] 11


X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10)
Current Operating System: Linux marietto2009 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
Build Date: 09 January 2009  02:57:16AM
 
      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-config0/XF86ConfigLog.7454", Time: Thu Feb 19 22:30:24 2009
(++) Using config file: "/tmp/vmware-config0/XF86Config.7454"
(II) Module "ramdac" already built-in
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server

X is running fine with the new config file.

FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.
   Checking acpi hot plug                                              done
Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                                   done
   Guest operating system daemon:                                      done
   Virtual Printing daemon:                                            done

The configuration of VMware Tools 6.5.0 build-118166 for Linux for this running
kernel completed successfully.

You must restart your X session before any mouse or graphics changes take
effect.

You can now run VMware Tools by invoking the following command:
"/usr/bin/vmware-toolbox" during an X server session.

To enable advanced X features (e.g., guest resolution fit, drag and drop, and
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.

If the virtual printer feature is enabled, you will need to restart the CUPS
service to make use of this feature.

Enjoy,

--the VMware team

and it doesn't works.
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23706953
I've reinstalled everything again. This time I've used the gcc 4.1 instead of the 4.3 to build the VMware tools. This is what's happened :

None of the pre-built vsock modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vsock module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vsock module.

Building the vsock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vsock-only'
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
  CC [M]  /tmp/vmware-config0/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/vmware-config0/vsock-only/linux/driverLog.o
  CC [M]  /tmp/vmware-config0/vsock-only/linux/util.o
  CC [M]  /tmp/vmware-config0/vsock-only/linux/vsockAddr.o
  LD [M]  /tmp/vmware-config0/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Subscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_DeviceGet" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyFromQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Detach" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Alloc" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Unsubscribe" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyToQueueV" [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
  CC      /tmp/vmware-config0/vsock-only/vsock.mod.o
  LD [M]  /tmp/vmware-config0/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config0/vsock-only'
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/vsock.o': -1 Unknown symbol in module
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel.  You may want to
rebuild a kernel based on that directory, or specify another directory.

The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and
host.  The rest of this software provided by VMware Tools is designed to work
independently of this feature.  If you wish to have the VSOCK feature  you can
install the driver by running vmware-config-tools.pl again after making sure
that gcc, binutils, make and the kernel sources for your running kernel are
installed on your machine. These packages are available on your distribution's
installation CD.
[ Press the Enter key to continue.]
0
 
LVL 2

Author Comment

by:marietto2008
ID: 23710470
Maybe I've found the solution here :

http://kramfs.com/vmware-server-2-unable-to-build-the-vsock-module/

but now there is another error :

marietto2009:/usr/lib/vmware-tools/modules/source/vsock-only# make

Using 2.6.x kernel build system.
make: cc: Command not found
make -C /lib/modules/2.6.26-1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.26-1-686'
/usr/lib/vmware-tools/modules/source/vsock-only/Makefile:106: *** Inappropriate build environment: you wanted to use gcc version while kernel attempts to use gcc version 4.1.3.
/usr/lib/vmware-tools/modules/source/vsock-only/Makefile:108: *** For proper build you'll have to replace  gcc-4.1 with symbolic link to cc.  Stop.
make[1]: *** [_module_/usr/lib/vmware-tools/modules/source/vsock-only] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686'
make: *** [vsock.ko] Error 2
/source/vsock-only#
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this step by step tutorial with screenshots, we will show you HOW TO: Enable SSH Remote Access on a VMware vSphere Hypervisor 6.5 (ESXi 6.5). This is important if you need to enable SSH remote access for additional troubleshooting of the ESXi hos…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…
Suggested Courses

865 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question