PDA

View Full Version : VMWARE tools shared folders & sharing files over a network



brianblaze
28th October 2012, 12:54 AM
Hello everyone.

I have been playing with Fedora 18 on my virtual machine and I have two problems. When I install vmware tools everything works properly except for the shared folders. I can not share folders and I get an error:



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


My next question is how do I share folders over the network if I have this fedora 18 box and the rest are windows? I am already sharing over a workgroup so I figure it shouldn't be too difficult...

THANK YOU YOU BEAUTIFUL PEOPLE!

brianblaze
29th October 2012, 05:20 PM
I just realised it's probably because the kernel is too new since the kernel for 18 is 3.6.3-3 and my kernel for 16 (works fine) 3.6.2-1

AdamW
30th October 2012, 01:33 AM
That's often the case with VMware, yeah. It takes them a bit of time to catch up with upstream kernel changes. There used to be an unofficial patchset for the VMware modules called any-any, which would patch the VMware stuff for upstream API changes faster than VMware managed to do it, but I don't know if that's still extant, it's a long time since I played with VMware stuff.