My vmtools installation experience

My vmtools installation experience-general Linux technology-Linux technology and application information. The following is a detailed description. Author: Hua Zi

I used both windows and linux, but it was very convenient to use a virtual machine, so I installed a virtual machine on windows, then, the Fedora 6 version linux is installed on the virtual machine. Next, I was troubled by the fact that vm tools could not be installed. Although I don't care about the display effect, there is still some trouble in file sharing between windows and linux without vm tools.

I follow the installation steps Step by step, but I always prompt that my version is inconsistent. I checked some information on the Internet and said the upgrade would work.

So I use the command
Yun install gcc
And
Yun install kernel-devel

Upgrade successful. The version information displayed in uname-r is the same as that displayed in rpm-q kernel-devel! However, when the vm tools is installed, the same error message still appears, but the installation still fails. After several failed attempts, I finally changed to a new version of vmware, vmware6. Now the installation is successful.

Click the installation menu and decompress the package. The following is a full record of my installation process.

Note: You can choose "yes" for all options on the Internet or press enter directly. This is not the case. One of them should be special.

Note. It is to ask whether to install the communication channel between the host and the vm... this item is [no] by default. If you press enter directly, the main

The host and vm cannot communicate directly.

[Root @ bogon tmp] # ls
Gconfd-root scim-panel-socket: 0-root
Keyring-JEC5MC scim-socket-frontend-root
Mapping-root ssh-wkfPkG2186
Orbit-root virtual-root.UjDoTy
Scim-bridge-0.3.0.lockfile-0 @ localhost: 0.0 VMwareTools-6.0.2-59824.tar.gz
Scim-bridge-0.3.0.socket-0 @ localhost: 0.0 vmware-tools-distrib
Scim-helper-manager-socket-root
[Root @ bogon tmp] # cd vmware-tools-distrib/
[Root @ bogon vmware-tools-distrib] # ls
Bin doc etc files install installer lib vmware-install.pl
[Root @ bogon vmware-tools-distrib] #./vmware-install.pl
A previous installation of VMware Tools has been detected.

The previous installation was made by the tar installer (version 3 ).

Keeping the tar3 installer database format.

Uninstalling the tar installation of VMware Tools.

Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: [OK]

The removal of VMware Tools 5.0.0 build-13124 for Linux completed successfully.
Thank you for having tried this software.

Converting the tar3 installer database format to the tar4 installer database
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/rc. d]

What is the directory that contains the init scripts?
[/Etc/rc. d/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] y

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] y

The installation of VMware Tools 6.0.2 build-59824 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
Invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
This program to invoke the command for you now? [Yes] y


Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: [OK]
Trying to find a suitable vmmemctl module for your running kernel.

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] y

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.18-1.2798.fc6/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.18-1.2798.fc6/build/include/... SUBDIRS = $ pwd srcroot = $ PWD/. modules
Make [1]: Entering directory '/usr/src/kernels/2.6.18-1.2798.fc6-i686'
CC [M]/tmp/vmware-config0/vmmemctl-only/OS. o
SHIPPED/tmp/vmware-config0/vmmemctl-only/vmmemctl1.o
LD [MB]/tmp/vmware-config0/vmmemctl-only/vmmemctl. o
Building modules, stage 2.
MODPOST
WARNING: cocould not find/tmp/vmware-config0/vmmemctl-only/. vmmemctl1.o. cmd for/tmp/vmware-

Config0/vmmemctl-only/vmmemctl1.o
CC/tmp/vmware-config0/vmmemctl-only/vmmemctl. mod. o
LD [MB]/tmp/vmware-config0/vmmemctl-only/vmmemctl. ko
Make [1]: Leaving directory '/usr/src/kernels/2.6.18-1.2798.fc6-i686'
Cp-f vmmemctl. ko ../vmmemctl. o
Make: Leaving directory '/tmp/vmware-config0/vmmemctl-only'
The module loads perfectly in the running kernel.

Trying to find a suitable vmhgfs module for your 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
Your system (you need to have a C compiler installed on your system )? [Yes] y

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.18-1.2798.fc6/build/include/... SUBDIRS = $ pwd srcroot = $ PWD/. modules
Make [1]: Entering directory '/usr/src/kernels/2.6.18-1.2798.fc6-i686'
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 [MB]/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/dbllnklst. o
CC [MB]/tmp/vmware-config0/vmhgfs-only/dentry. o
CC [M]/tmp/vmware-config0/vmhgfs-only/dir. o
CC [M]/tmp/vmware-config0/vmhgfs-only/eventManager. 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/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/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/rpcin. 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 [MB]/tmp/vmware-config0/vmhgfs-only/super. o
LD [MB]/tmp/vmware-config0/vmhgfs-only/vmhgfs. o
Building modules, stage 2.
MODPOST
CC/tmp/vmware-config0/vmhgfs-only/vmhgfs. mod. o
LD [M]/tmp/vmware-config0/vmhgfs-only/vmhgfs. ko
Make [1]: Leaving directory '/usr/src/kernels/2.6.18-1.2798.fc6-i686'
Cp-f vmhgfs. ko ../vmhgfs. o
Make: Leaving directory '/tmp/vmware-config0/vmhgfs-only'
The module loads perfectly in the running kernel.

Pcnet32 38213 0
Unloading pcnet32 module

Trying to find a suitable vmxnet module for your 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
Your system (you need to have a C compiler installed on your system )? [Yes] y

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.18-1.2798.fc6/build/include/... SUBDIRS = $ pwd srcroot = $ PWD/. modules
Make [1]: Entering directory '/usr/src/kernels/2.6.18-1.2798.fc6-i686'
CC [MB]/tmp/vmware-config0/vmxnet-only/vmxnet. o
Building modules, stage 2.
MODPOST
HTTP/tmp/vmware-config0/vmxnet-only/vmxnet. mod. o
LD [M]/tmp/vmware-config0/vmxnet-only/vmxnet. ko
Make [1]: Leaving directory '/usr/src/kernels/2.6.18-1.2798.fc6-i686'
Cp-f vmxnet. ko./../vmxnet. o
Make: Leaving directory '/tmp/vmware-config0/vmxnet-only'
The module loads perfectly in the running kernel.

Trying to find a suitable vmblock module for your 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] y

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.18-1.2798.fc6/build/include/... SUBDIRS = $ pwd srcroot = $ PWD/. modules
Make [1]: Entering directory '/usr/src/kernels/2.6.18-1.2798.fc6-i686'
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
CC/tmp/vmware-config0/vmblock-only/vmblock. mod. o
LD [M]/tmp/vmware-config0/vmblock-only/vmblock. ko
Make [1]: Leaving directory '/usr/src/kernels/2.6.18-1.2798.fc6-i686'
Cp-f vmblock. ko ../vmblock. o
Make: Leaving directory '/tmp/vmware-config0/vmblock-only'
The module loads perfectly in the running kernel.

[EXPERIMENTAL] The Virtual Machine Communication Interface (VMCI) service
Provides a new communication capability with the Host, primarily
Development at the moment. wocould you like to enable this feature? [No] y

Trying to find a suitable vmci module for your running kernel.

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
Your system (you need to have a C compiler installed on your system )? [Yes] y

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.18-1.2798.fc6/build/include/... SUBDIRS = $ pwd srcroot = $ PWD/. modules
Make [1]: Entering directory '/usr/src/kernels/2.6.18-1.2798.fc6-i686'
CC [M]/tmp/vmware-config0/vmci-only/dbllnklst. o
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/vmciProcess. o
CC [M]/tmp/vmware-config0/vmci-only/vmciResource. o
CC [M]/tmp/vmware-config0/vmci-only/vmciSharedMemory. o
CC [M]/tmp/vmware-config0/vmci-only/vmciTest. o
CC [M]/tmp/vmware-config0/vmci-only/vmciUtil. o
LD [M]/tmp/vmware-config0/vmci-only/vmci. o
Building modules, stage 2.
MODPOST
CC/tmp/vmware-config0/vmci-only/vmci. mod. o
LD [M]/tmp/vmware-config0/vmci-only/vmci. ko
Make [1]: Leaving directory '/usr/src/kernels/2.6.18-1.2798.fc6-i686'
Cp-f vmci. ko ../vmci. o
Make: Leaving directory '/tmp/vmware-config0/vmci-only'
The module loads perfectly in the running kernel.


Detected X.org version 7.1.


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

[1] "640x480"
[2] <"800x600"
[3] "1024x768"
[4] "1152x864"
[5] "1280x800"
[6] "1152x900"
[7] "1280x1024"
[8] "1376x1032"
[9] "1400x900"
[10] "1400x1050"
[11] "1440x900"
[12] "1680x1050"
[13] "1600x1200"
[14] "1920x1200"
[15] "2364x1773"
Please enter a number between 1 and 15:

[2] 3


X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.9-34. ELsmp i686 Red Hat, Inc.
Current Operating System: Linux bogon 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006

I686
Create Date: 04 October 2006
Build ID: xorg-x11-server 1.1.1-47. fc6
Before reporting problems, checking 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. 2583", Time: Wed Jan 9 14:28:51 2008
(++) Using config file: "/tmp/vmware-config0/XF86Config. 2583"

X is running fine with the new config file.

(EE) AIGLX: Screen 0 is not DRI capable
FreeFontPath: FPE "unix/: 7100" refcount is 2, shocould be 1; fixing.
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: [OK]
Guest filesystem driver: [OK]
Mounting HGFS shares: [failed]
Guest memory manager: [OK]
Guest vmxnet fast network device: [OK]
New Host-Guest communications path: [OK]
Blocking file system: [OK]
DMA setup: [OK]
Guest operating system daemon: [OK]

The configuration of VMware Tools 6.0.2 build-59824 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 use the vmxnet driver, restart networking using the following commands:
/Etc/init. d/network stop
Rmmod pcnet32
Rmmod vmxnet
Modprobe vmxnet
/Etc/init. d/network start

To make use of the virtual printer, you will need to restart the CUPS service

Enjoy,

-- The VMware team

[Root @ bogon vmware-tools-distrib] #

Create a shared folder after installation. In the vm menu, add the corresponding settings to vm-setting-option-shared folders. Note: It's not over yet. Disable the firewall of virtual machines, including Selinux.

Now, the shared windows folder can be viewed in the file:/mnt/hgfs directory of the virtual machine. The folder host and vm can be used to transfer files.