Общие папки VMware Workstation 8 не работают с моей клиентской установкой Fedora 17

У меня есть Windows7, на котором запущен урезанный сервер Fedora 17 (без графического интерфейса), работающий внутри VMware 8 Workstation. Когда я приступаю к установке vmware-tools, компонент общих папок не может скомпилировать модуль vmhgfs, хотя у меня установлены все утилиты, например, gcc, make, kernel-headers, binutils и т. Д. В сети я не нашел никакой информации, которая решает эту проблему. Я нахожу все виды взлома исходного кода vmware для работы с другими версиями Fedora, но не для версии 17 (Beefy Miracle). Если я попытаюсь включить общие папки и указать на локальную папку, в /mnt/hgfs ничего не будет. Если у кого-то есть опыт исправления этой проблемы или статьи, патча и т. Д., Пожалуйста, дайте мне знать. Хотелось бы, чтобы эта функция работала.

Вот ошибка, которую я получаю:

/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function â__check_disable_hostâ:
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2498:1: warning: return from incompatible pointer type [enabled by
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function â__check_disable_guestâ:
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2501:1: warning: return from incompatible pointer type [enabled by
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function â__check_disable_msiâ:
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2504:1: warning: return from incompatible pointer type [enabled by
/tmp/vmware-root/modules/vmci-only/linux/driver.c: In function â__check_disable_msixâ:
/tmp/vmware-root/modules/vmci-only/linux/driver.c:2507:1: warning: return from incompatible pointer type [enabled by
  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmci-only/vmci.mod.o
  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/kernels/3.4.3-1.fc17.x86_64'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
 Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmhgfs-only'
make -C /lib/modules/3.4.3-1.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.4.3-1.fc17.x86_64'
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/message.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/dir.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/rpcout.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/filesystem.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpName.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/request.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/link.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/module.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/hgfsUtil.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/stubs.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/tcp.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/hgfsEscape.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/file.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/super.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/dentry.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/inode.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/bdhandler.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/vmci.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/transport.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/fsutil.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpNameLinux.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/hgfsBd.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/backdoor.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/backdoorGcc64.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpNameLite.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/kernelStubsLinux.o
  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/page.o
/tmp/vmware-root/modules/vmhgfs-only/file.c:128:4: warning: initialization from incompatible pointer type [enabled by
/tmp/vmware-root/modules/vmhgfs-only/file.c:128:4: warning: (near initialization for âHgfsFileFileOperations.fsyncâ)
/tmp/vmware-root/modules/vmhgfs-only/filesystem.c: In function âHgfsGetRootDentryâ:
/tmp/vmware-root/modules/vmhgfs-only/filesystem.c:379:4: error: implicit declaration of function âd_alloc_rootâ [-Wer
/tmp/vmware-root/modules/vmhgfs-only/filesystem.c:379:19: warning: assignment makes pointer from integer without a ca
cc1: some warnings being treated as errors
make[2]: *** [/tmp/vmware-root/modules/vmhgfs-only/filesystem.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/tmp/vmware-root/modules/vmhgfs-only/inode.c:121:4: warning: initialization from incompatible pointer type [enabled b
/tmp/vmware-root/modules/vmhgfs-only/inode.c:121:4: warning: (near initialization for âHgfsDirInodeOperations.createâ
/tmp/vmware-root/modules/vmhgfs-only/inode.c:124:4: warning: initialization from incompatible pointer type [enabled b
/tmp/vmware-root/modules/vmhgfs-only/inode.c:124:4: warning: (near initialization for âHgfsDirInodeOperations.mkdirâ)
make[1]: *** [_module_/tmp/vmware-root/modules/vmhgfs-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/3.4.3-1.fc17.x86_64'
make: *** [vmhgfs.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only'

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 ]

1 ответ

Решение

Проблема решена. Вместо этого я загрузился в ядре 3.3.4, и теперь все работает. Я думаю, vmware-tools еще не поддерживают ядра 3.4.

Другие вопросы по тегам