Vmware Tools 설치 – Fedora9

By | 2008/08/12

최근에 작업할 일이 생겨 리눅스를 깨끗하게 설치할 필요가 생겼습니다.

하지만 멀티 부팅으로 작업하기에는 이제 한계에 도달하여

외장 하드에 Vmware 이미지 파일을 저장하는 방식으로 설치하였습니다.

 

Vmware 상에서 리눅스를 제대로 쓰기 위해서는 Vmware Tools를 설치하여야합니다.

따라서 이를 설치하기 위해 시디를 넣었더니 rpm과 tar.gz 두 파일이 나오더군요.

비록 Fedora 9이기는 하지만, tar.gz 파일 압축을 풀어 설치하였습니다.

 

 

그런데 중간에 이런 메시지가 떴습니다.

‘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.’

 

확인해보니 정말 경로가 없었습니다.

그래서 살펴보니 제가 커널 소스를 다운로드 받지 않았음을 알았습니다.

 

따라서 yum install로 해결하였습니다.

‘yum install kernel-devel’

 

처음에 실수로 다른 버전을 설치하였더니 맞지 않다고 하더군요.

결국 지우고 새롭게 확인하여 설치하였습니다.ㅜ

 

 

그렇게 설치를 완료하고 나니 상당히 쓰기 편합니다.

특히 마우스 커서를 바깥으로 옮길 때 그대로 따라나오는 것이 좋습니다.^^

 

다만 KDE3를 사용하다 KDE4를 사용하니 정말 힘드네요.ㅜㅜ

 

 

밑에 글은 출력 메시지들입니다.

이렇게 히스토리를 기록하는 것이 후에 검색할 때 편할 듯싶습니다.

 

 

[[email protected] vmware-tools-distrib]$ ./vmware-install.pl
Please re-run this program as the super user.

Execution aborted.

[[email protected] vmware-tools-distrib]$ su
암 호 :
[[email protected] 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 4).

Keeping the tar4 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 6.0.4 build-93057 for Linux completed successfully.
Thank you for having tried this software.

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]

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.0.4 build-93057 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:                          [  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]

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 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 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 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 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 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 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 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 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 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 not an existing directory.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/src/kernels/2.6.25.11-97.fc9.i586/include/

The directory of kernel headers (version 2.6.25.11-97.fc9.i586) does not match
your running kernel (version 2.6.25.11-97.fc9.i686).  Even if the module were
to compile successfully, it would not load into the running kernel.

What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include] /usr/src/kernels/2.6.25.11-97.fc9.i686/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/kernels/2.6.25.11-97.fc9.i686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25.11-97.fc9.i686′
  CC [M]  /tmp/vmware-config0/vmmemctl-only/os.o
  SHIPPED /tmp/vmware-config0/vmmemctl-only/vmmemctl1.o
  LD [M]  /tmp/vmware-config0/vmmemctl-only/vmmemctl.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: could 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 [M]  /tmp/vmware-config0/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.25.11-97.fc9.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 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/kernels/2.6.25.11-97.fc9.i686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25.11-97.fc9.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 [M]  /tmp/vmware-config0/vmhgfs-only/cpName.o
In file included from include/linux/string.h:11,
                 from /tmp/vmware-config0/vmhgfs-only/cpName.h:18,
                 from /tmp/vmware-config0/vmhgfs-only/cpName.c:18:
include/linux/types.h:40: error: conflicting types for ‘uintptr_t’
/tmp/vmware-config0/vmhgfs-only/vm_basic_types.h:170: error: previous declaration of ‘uintptr_t’ was here
make[2]: *** [/tmp/vmware-config0/vmhgfs-only/cpName.o] 오 류  1
make[1]: *** [_module_/tmp/vmware-config0/vmhgfs-only] 오 류  2
make[1]: Leaving directory `/usr/src/kernels/2.6.25.11-97.fc9.i686′
make: *** [vmhgfs.ko] 오 류  2
make: Leaving directory `/tmp/vmware-config0/vmhgfs-only’
Unable to build the vmhgfs module.

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 ]

pcnet32                30964  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 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-config1/vmxnet-only’
make -C /usr/src/kernels/2.6.25.11-97.fc9.i686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25.11-97.fc9.i686′
  CC [M]  /tmp/vmware-config1/vmxnet-only/vmxnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config1/vmxnet-only/vmxnet.mod.o
  LD [M]  /tmp/vmware-config1/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.25.11-97.fc9.i686′
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-config1/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]

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmblock-only’
make -C /usr/src/kernels/2.6.25.11-97.fc9.i686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.25.11-97.fc9.i686′
  CC [M]  /tmp/vmware-config1/vmblock-only/linux/block.o
  CC [M]  /tmp/vmware-config1/vmblock-only/linux/control.o
  CC [M]  /tmp/vmware-config1/vmblock-only/linux/dbllnklst.o
  CC [M]  /tmp/vmware-config1/vmblock-only/linux/dentry.o
/tmp/vmware-config1/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate’:
/tmp/vmware-config1/vmblock-only/linux/dentry.c:101: error: ‘struct nameidata’ hasno member named ‘dentry’
/tmp/vmware-config1/vmblock-only/linux/dentry.c:101: error: ‘struct nameidata’ hasno member named ‘dentry’
/tmp/vmware-config1/vmblock-only/linux/dentry.c:102: error: implicit declaration of function ‘path_release’
make[2]: *** [/tmp/vmware-config1/vmblock-only/linux/dentry.o] 오 류  1
make[1]: *** [_module_/tmp/vmware-config1/vmblock-only] 오 류  2
make[1]: Leaving directory `/usr/src/kernels/2.6.25.11-97.fc9.i686′
make: *** [vmblock.ko] 오 류  2
make: Leaving directory `/tmp/vmware-config1/vmblock-only’
Unable to build the vmblock module.

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 Virtual Machine Communication Interface (VMCI) service
provides a new communication capability with the Host, primarily for
development at the moment.  Would you like to enable this feature? [no]

Detected X.org version 0.0.0.

No drivers for X.org version: 0.0.0.

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

[1]  “640×480”
[2]  “800×600”
[3]  “1024×768”
[4]  “1152×864”
[5]  “1280×800”
[6]  “1152×900”
[7]  “1280×1024”
[8]< “1376×1032”
[9]  “1400×900”
[10]  “1400×1050”
[11]  “1440×900”
[12]  “1680×1050”
[13]  “1600×1200”
[14]  “1920×1200”
[15]  “2364×1773”
Please enter a number between 1 and 15:

[8] 3

Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                       [  OK  ]
   Guest memory manager:                                   [  OK  ]
   Guest vmxnet fast network device:                       [  OK  ]
   DMA setup:                                              [  OK  ]
   Guest operating system daemon:                          [  OK  ]

The configuration of VMware Tools 6.0.4 build-93057 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

[[email protected] vmware-tools-distrib]#

14 thoughts on “Vmware Tools 설치 – Fedora9

  1. imc84

    리눅스용 vmware tools도 있는지 몰랐네요. 페도라-KDE에서만 가능한 건가요?

    Reply
    1. NoSyu

      아닐 겁니다.
      상세히 살펴보지 않았지만 RPM 외에 tar.gz로 배포하는 것과
      중간에 컴파일을 하는 것으로 보아 모든 리눅스에서 가능할 것입니다.^^

      Reply
    1. NoSyu

      저도 2년 가량 배웠지만 어느 나라 말인지 모르겠습니다.OTL…..
      영어이나 영어가 아니더군요.ㅜㅜ

      Reply
  2. 까칠한JC

    저는 vm으로 사용하는 것이 답답하더라구요. KDE4에 적응되시면 메인도 fedora9으로 넘어오시지요. ^^
    저야 그놈 유저이기 땜시로 전혀 관계가 없지만요. ^^ 아~ 그리고 VMware, VirtualBox 모두 MS 윈도우, Mac OS X, 모든 종류의 리눅스를 지원합니다. 또한 우분투는 apt-get으로 fedora는 yum또는 rpm으로 쉽게 설치가 가능합니다.

    Reply
    1. NoSyu

      저도 답답하기는 하지만 메인에선 KDE4를 깔 용기(?)가 없습니다.
      제 컴퓨터가 노트북이다보니 모바일 그래픽카드입니다.
      그래서인지 ATI 드라이버를 설치하면 에러가 발생합니다.
      (윈도우든 리눅스든….)
      그래서 윈도우에서는 회사에서 제공하는 것을, 리눅스에서는 기본으로 제공되는 것을 이용하는터라
      윈도우에서는 문제 없이 돌아가지만 리눅스에서는 그래픽 처리 속도가 느립니다.
      따라서 Vmware를 써서 돌리고 있는 현실입니다.ㅜㅜ
      (돈이 있다면 리눅스 전용 컴퓨터를 구입하고 싶습니다.ㅜㅜ)

      Reply
  3. 니트

    이번에 새로 사면 리눅스를 사용해보려고 했는데 아예 못 살 가능성이 높아져서 안습입니다. ㅠㅠ

    Reply
    1. NoSyu

      저런….
      저도 이번에 구입을 망설이고 있습니다만, 역시 쩐의 한계가….ㅜ

      Reply
  4. Mr.Dust

    Vmware 도 마우스 통합기능을 지원하는군요. Virtualbox 의 그 기능에 반해서 넘어왔는데.. :)

    Reply
    1. NoSyu

      네.. 이번에 해보니 되는 것을 확인하였습니다.
      또한, VirtualBox에 비해 가상 OS의 속도가 빠른 것을 확인하였기에 다시 Vmware로 넘어왔습니다.ㅜ

      Reply
  5. 우빈*

    안낭하세요 -0-

    블로그 보면서 저도 설치중인데…

    처음 접한 리눅스라 뭐가 뭔지 도통 모르겠네요;;;;

    저도 커널 버전이 매칭되지 않는다고 하는데….

    여기서 어떻게 해야하나요… ㄷ

    Reply
    1. NoSyu

      반갑습니다.
      그렇다면 root 계정으로 로그인 하신 후
      yum install kernel-devel
      을 해보시길 바랍니다.

      Reply
  6. Robin

    전 우분투로 깔았는데요..
    해상도는 잡히는데 왜 마우스는 바깥으로 따라나오지 않을까요?

    우분투 업데이트도 다 했구요.

    Reply
    1. NoSyu

      반갑습니다.
      저는 우분투를 잘 쓰지 않아 정확하게 잘 기억이 나지 않습니다.
      하지만 제 기억으로는 우분투는 따로 Vmware Tools를 설치할 필요가 없던 것으로 기억합니다.
      그것이 참 신기했고 대단하다는 생각을 한 것으로 기억합니다.
      http://kldp.org/node/88708
      윗글이 도움이 되리라 생각합니다.

      Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.