vmware에서 unity기능을 사용하려고하는데 느낌표뜨고 안되네요~

The virtual machine cannot enter Unity mode because:

-Unity is not supported on this guest operating system.
-The guest operating system's resolution cannot be changed.

------------------------------------------------------
vmware tool설치시 메시지 첨부하겠습니다.

[root@localhost mszeta]# /usr/bin/vmware-config-tools.pl

Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: [ OK ]
Virtual Printing daemon: [ OK ]
VMware User Agent (vmware-user): [ OK ]
Blocking file system: [ OK ]
Unmounting HGFS shares: [ OK ]
Guest filesystem driver: [ OK ]
Guest memory manager: [ OK ]
VM communication interface socket family: [ OK ]
VM communication interface: [ OK ]
File system sync driver: [ OK ]
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.27.15-170.2.24.fc10.i686/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-config4/vmmemctl-only'
make -C /lib/modules/2.6.27.15-170.2.24.fc10.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
CC [M] /tmp/vmware-config4/vmmemctl-only/backdoorGcc32.o
CC [M] /tmp/vmware-config4/vmmemctl-only/os.o
CC [M] /tmp/vmware-config4/vmmemctl-only/vmballoon.o
LD [M] /tmp/vmware-config4/vmmemctl-only/vmmemctl.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmmemctl-only/vmmemctl.mod.o
LD [M] /tmp/vmware-config4/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-config4/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-config4/vmhgfs-only'
make -C /lib/modules/2.6.27.15-170.2.24.fc10.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
CC [M] /tmp/vmware-config4/vmhgfs-only/backdoor.o
CC [M] /tmp/vmware-config4/vmhgfs-only/backdoorGcc32.o
CC [M] /tmp/vmware-config4/vmhgfs-only/bdhandler.o
CC [M] /tmp/vmware-config4/vmhgfs-only/cpName.o
CC [M] /tmp/vmware-config4/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/vmware-config4/vmhgfs-only/cpNameLite.o
CC [M] /tmp/vmware-config4/vmhgfs-only/dentry.o
CC [M] /tmp/vmware-config4/vmhgfs-only/dir.o
CC [M] /tmp/vmware-config4/vmhgfs-only/file.o
CC [M] /tmp/vmware-config4/vmhgfs-only/filesystem.o
CC [M] /tmp/vmware-config4/vmhgfs-only/fsutil.o
CC [M] /tmp/vmware-config4/vmhgfs-only/hgfsBd.o
CC [M] /tmp/vmware-config4/vmhgfs-only/hgfsEscapeLinux.o
CC [M] /tmp/vmware-config4/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/vmware-config4/vmhgfs-only/inode.o
CC [M] /tmp/vmware-config4/vmhgfs-only/kernelStubsLinux.o
CC [M] /tmp/vmware-config4/vmhgfs-only/link.o
CC [M] /tmp/vmware-config4/vmhgfs-only/message.o
CC [M] /tmp/vmware-config4/vmhgfs-only/messageBackdoor.o
CC [M] /tmp/vmware-config4/vmhgfs-only/module.o
CC [M] /tmp/vmware-config4/vmhgfs-only/page.o
CC [M] /tmp/vmware-config4/vmhgfs-only/request.o
CC [M] /tmp/vmware-config4/vmhgfs-only/rpcout.o
CC [M] /tmp/vmware-config4/vmhgfs-only/staticEscape.o
CC [M] /tmp/vmware-config4/vmhgfs-only/stubs.o
CC [M] /tmp/vmware-config4/vmhgfs-only/super.o
LD [M] /tmp/vmware-config4/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/vmware-config4/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-config4/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-config4/vmxnet-only'
make -C /lib/modules/2.6.27.15-170.2.24.fc10.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
CC [M] /tmp/vmware-config4/vmxnet-only/vmxnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmxnet-only/vmxnet.mod.o
LD [M] /tmp/vmware-config4/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-config4/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-config4/vmblock-only'
make -C /lib/modules/2.6.27.15-170.2.24.fc10.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
CC [M] /tmp/vmware-config4/vmblock-only/linux/block.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/control.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/dbllnklst.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/dentry.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/file.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/filesystem.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/inode.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/module.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/stubs.o
CC [M] /tmp/vmware-config4/vmblock-only/linux/super.o
LD [M] /tmp/vmware-config4/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmblock-only/vmblock.mod.o
LD [M] /tmp/vmware-config4/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config4/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?
[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]

Extracting the sources of the vmsync module.

Building the vmsync module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config4/vmsync-only'
make -C /lib/modules/2.6.27.15-170.2.24.fc10.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
CC [M] /tmp/vmware-config4/vmsync-only/sync.o
LD [M] /tmp/vmware-config4/vmsync-only/vmsync.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmsync-only/vmsync.mod.o
LD [M] /tmp/vmware-config4/vmsync-only/vmsync.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
cp -f vmsync.ko ./../vmsync.o
make: Leaving directory `/tmp/vmware-config4/vmsync-only'
The vmsync module loads perfectly into the 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 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-config4/vmci-only'
make -C /lib/modules/2.6.27.15-170.2.24.fc10.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
CC [M] /tmp/vmware-config4/vmci-only/kernelStubsLinux.o
CC [M] /tmp/vmware-config4/vmci-only/vmciDatagram.o
CC [M] /tmp/vmware-config4/vmci-only/vmciEvent.o
CC [M] /tmp/vmware-config4/vmci-only/vmciGuestDs.o
CC [M] /tmp/vmware-config4/vmci-only/vmciGuestKernelIf.o
CC [M] /tmp/vmware-config4/vmci-only/vmciKernelIf.o
CC [M] /tmp/vmware-config4/vmci-only/vmciProcess.o
CC [M] /tmp/vmware-config4/vmci-only/vmciQueuePair.o
CC [M] /tmp/vmware-config4/vmci-only/vmciUtil.o
CC [M] /tmp/vmware-config4/vmci-only/vmci_drv.o
LD [M] /tmp/vmware-config4/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config4/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-config4/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-config4/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-config4/vsock-only'
make -C /lib/modules/2.6.27.15-170.2.24.fc10.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
CC [M] /tmp/vmware-config4/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-config4/vsock-only/linux/driverLog.o
CC [M] /tmp/vmware-config4/vsock-only/linux/util.o
CC [M] /tmp/vmware-config4/vsock-only/linux/vsockAddr.o
LD [M] /tmp/vmware-config4/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: "VMCIDatagram_CreateHnd" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_DestroyHnd" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Subscribe" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_DeviceGet" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyFromQueueV" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Detach" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCI_GetContextID" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCIDatagram_Send" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCIQueuePair_Alloc" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCIEvent_Unsubscribe" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
WARNING: "VMCIMemcpyToQueueV" [/tmp/vmware-config4/vsock-only/vsock.ko] undefined!
CC /tmp/vmware-config4/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config4/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.27.15-170.2.24.fc10.i686'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config4/vsock-only'
The vsock module loads perfectly into the running kernel.

Detected X.org version 7.4.3.

No drivers for X.org version: 7.4.3.

The configuration file /etc/X11/xorg.conf can not be found. Do you want to
create a new one? (yes/no) [yes]

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

X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-92.1.18.el5 i686
Current Operating System: Linux localhost.localdomain 2.6.27.15-170.2.24.fc10.i686 #1 SMP Wed Feb 11 23:58:12 EST 2009 i686
Build Date: 16 February 2009 01:58:52AM
Build ID: xorg-x11-server 1.5.3-13.fc10
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
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-config4/XF86ConfigLog.19955", Time: Thu Mar 5 21:10:43 2009
(++) Using config file: "/tmp/vmware-config4/XF86Config.19955"
Parse error on line 13 of section Files in file /tmp/vmware-config4/XF86Config.19955
"RgbPath" is not a valid keyword in this section.
(EE) Problem parsing the config file
(EE) Error parsing the config file

Fatal server error:
no screens found
Details in /tmp/vmware-config4/XF86ConfigLog.19955

The updated X config file does not work well. See
/tmp/vmware-config4/XF86ConfigLog.19955 for details. Do you want to create a
new one from template? Warning: if you choose to create a new one, all old
settings will be gone! (yes/no) [yes]

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

Warning: unable to close filehandle CHILD properly.

X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-92.1.18.el5 i686
Current Operating System: Linux localhost.localdomain 2.6.27.15-170.2.24.fc10.i686 #1 SMP Wed Feb 11 23:58:12 EST 2009 i686
Build Date: 16 February 2009 01:58:52AM
Build ID: xorg-x11-server 1.5.3-13.fc10
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
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-config4/XF86ConfigLog.19955", Time: Thu Mar 5 21:10:52 2009
(++) Using config file: "/tmp/vmware-config4/XF86Config.19955"
Parse error on line 13 of section Files in file /tmp/vmware-config4/XF86Config.19955
"RgbPath" is not a valid keyword in this section.
(EE) Problem parsing the config file
(EE) Error parsing the config file

Fatal server error:
no screens found
Details in /tmp/vmware-config4/XF86ConfigLog.19955
Checking acpi hot plug [ OK ]
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: [ OK ]
Guest filesystem driver: [ OK ]
Mounting HGFS shares: [실패]
Guest memory manager: [ OK ]
Guest vmxnet fast network device: [ OK ]
VM communication interface: [ OK ]
VM communication interface socket family: [ OK ]
Blocking file system: [ OK ]
File system sync driver: [ OK ]
Guest operating system daemon: [ OK ]
Virtual Printing daemon: [ OK ]

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/network stop
rmmod pcnet32
rmmod vmxnet
modprobe vmxnet
/etc/init.d/network 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

[root@localhost mszeta]#