install vmtools on Suse 11

Install VMtoos on Suse enterprise 11,

 

need rebuild some tools,

 

please use following include file for header.

 

/usr/src/linux-obj/x86_64/default/include

 

you need install kernel source package first.

 

----------------------

This program previously created the file
/usr/lib/vmware-tools/lib64/libconf/etc/pango/pango.modules, and was about to
remove it.  Somebody else apparently did it already.

File /usr/lib/vmware-tools/lib64/libconf/etc/pango/pangorc is backed up to
/usr/lib/vmware-tools/lib64/libconf/etc/pango/pangorc.old.1.

This program previously created the file
/usr/lib/vmware-tools/libconf/etc/gtk-2.0/gtk.immodules, and was about to
remove it.  Somebody else apparently did it already.

File /usr/lib/vmware-tools/lib64/libconf/etc/pango/pangox.aliases is backed up
to /usr/lib/vmware-tools/lib64/libconf/etc/pango/pangox.aliases.old.1.

This program previously created the file
/usr/lib/vmware-tools/libconf/etc/pango/pangorc, and was about to remove it. 
Somebody else apparently did it already.

File /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gtk.immodules is backed up
to /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gtk.immodules.old.1.

This program previously created the file
/usr/lib/vmware-tools/libconf/etc/pango/pangox.aliases, and was about to remove
it.  Somebody else apparently did it already.

File /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gdk-pixbuf.loaders is
backed up to
/usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gdk-pixbuf.loaders.old.1.

This program previously created the file
/usr/lib/vmware-tools/libconf/etc/gtk-2.0/gdk-pixbuf.loaders, and was about to
remove it.  Somebody else apparently did it already.

The removal of VMware Tools 7.8.6 build-185404 for Linux completed
successfully.

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/init.d]

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]

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 7.8.6 build-185404 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.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include]

The path "/usr/src/linux/include" is not an existing directory.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include]

The path "/usr/src/linux/include" is a kernel header file directory, but it
does not contain the file "linux/version.h" as expected.  This can happen if
the kernel has never been built, or if you have invoked the "make mrproper"
command in your kernel directory.  In any case, you may want to rebuild your
kernel.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/src/linux-2.6.27.19-5/include

The path "/usr/src/linux-2.6.27.19-5/include" is a kernel header file
directory, but it does not contain the file "linux/version.h" as expected. 
This can happen if the kernel has never been built, or if you have invoked the
"make mrproper" command in your kernel directory.  In any case, you may want to
rebuild your kernel.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/src/linux/include/linux/dvb

The path "/usr/src/linux/include/linux/dvb" is an existing directory, but it
does not contain a "linux" subdirectory as expected.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/src/linux/include/linux

The path "/usr/src/linux/include/linux" is an existing directory, but it does
not contain a "linux" subdirectory as expected.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/include

The header files in /usr/include are generally for C libraries, not for the
running kernel. If you do not have kernel header files in your /usr/src
directory, you probably do not have the kernel-source package installed. Are
you sure that /usr/include contains the header files associated with your
running kernel? [no]

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/src/linux-obj/x86_64/default/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 /usr/src/linux-obj/x86_64/default/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. /
      MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.27.19-5-obj/x86_64/default'
make -C ../../../linux-2.6.27.19-5 O=/usr/src/linux-2.6.27.19-5-obj/x86_64/default/. modules
  CC [M]  /tmp/vmware-config0/vmmemctl-only/backdoorGcc64.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-2.6.27.19-5-obj/x86_64/default'
make -C $PWD SRCROOT=$PWD/. /
      MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-config0/vmmemctl-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-config0/vmmemctl-only'
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 /usr/src/linux-obj/x86_64/default/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. /
      MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.27.19-5-obj/x86_64/default'
make -C ../../../linux-2.6.27.19-5 O=/usr/src/linux-2.6.27.19-5-obj/x86_64/default/. modules
  CC [M]  /tmp/vmware-config0/vmhgfs-only/backdoor.o
  CC [M]  /tmp/vmware-config0/vmhgfs-only/backdoorGcc64.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
/tmp/vmware-config0/vmhgfs-only/page.c: In function ‘HgfsDoWriteBegin’:
/tmp/vmware-config0/vmhgfs-only/page.c:764: warning: ISO C90 forbids mixed declarations and code
  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-2.6.27.19-5-obj/x86_64/default'
make -C $PWD SRCROOT=$PWD/. /
      MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-config0/vmhgfs-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-config0/vmhgfs-only'
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 /usr/src/linux-obj/x86_64/default/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. /
      MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.27.19-5-obj/x86_64/default'
make -C ../../../linux-2.6.27.19-5 O=/usr/src/linux-2.6.27.19-5-obj/x86_64/default/. modules
  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-2.6.27.19-5-obj/x86_64/default'
make -C $PWD SRCROOT=$PWD/. /
      MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-config0/vmxnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-config0/vmxnet-only'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-config0/vmxnet-only'
The vmxnet module loads perfectly into the running kernel.

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 /usr/src/linux-obj/x86_64/default/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. /
      MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.27.19-5-obj/x86_64/default'
make -C ../../../linux-2.6.27.19-5 O=/usr/src/linux-2.6.27.19-5-obj/x86_64/default/. modules
  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-2.6.27.19-5-obj/x86_64/default'
make -C $PWD SRCROOT=$PWD/. /
      MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-config0/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-config0/vmblock-only'
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 /usr/src/linux-obj/x86_64/default/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. /
      MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-2.6.27.19-5-obj/x86_64/default'
make -C ../../../linux-2.6.27.19-5 O=/usr/src/linux-2.6.27.19-5-obj/x86_64/default/. modules
  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-2.6.27.19-5-obj/x86_64/default'
make -C $PWD SRCROOT=$PWD/. /
      MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-config0/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-config0/vmci-only'
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]