You are not logged in.

#1 2014-05-13 21:53:29

Skitter
Member
Registered: 2013-09-28
Posts: 36

I can't use shared folders feature in VMware

Arch Linux is the guest system. Windows 7 is the host OS. I'm using VMware Workstation 10.0.1. After installing vmware tools (the original ones) I can't mount my shared folder. It says

~ mount -t vmhgfs .host:/ /mnt
Error: cannot mount filesystem: No such device

I've already searched the forum but I didn't find any solution to my problem.

[Update]
I think that it has something to do with the fact that vmware module sources are not compatible with the new UID and GID types:

  • uid_t -> kuid_t

  • gid_t -> kgid_t

I admit that I have no idea about patching sources. I've found this thread. It helped me with patching the vmhgfs module. Unfortunately the vmci module is still failing to compile because it's not patched yet. I have no idea how to fix this problem.
[Workaround]
Well I gave up. I've chosen the easiest way - Samba.

Additional information:

~ lsmod |grep -i vm
kvm_intel             134316  0 
kvm                   419974  1 kvm_intel
vmw_balloon             6258  0 
vmwgfx                167331  2 
ttm                    66913  1 vmwgfx
vmw_vmci               53487  0 
drm                   242043  3 ttm,vmwgfx
~ vmware-hgfsclient
E
~ vmware-config-tools.pl 
Initializing...


Making sure services for VMware Tools are stopped.

Stopping Thinprint services in the virtual machine:
   Stopping Virtual Printing daemon:                                   done
Stopping VMware Tools services in the virtual machine:
   Guest operating system daemon:                                      done
   Unmounting HGFS shares:                                             done
   Guest filesystem driver:                                            done


sh: : command not found
sh: : command not found

Before you can compile modules, you need to have the following installed... 

make
gcc
kernel headers of the running kernel


Searching for GCC...
Detected GCC binary at "/bin/gcc".
The path "/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no] 

Searching for a valid kernel header path...
Detected the kernel headers at "/lib/modules/3.14.3-2-ARCH/build/include".
The path "/lib/modules/3.14.3-2-ARCH/build/include" appears to be a valid path 
to the 3.14.3-2-ARCH kernel headers.
Would you like to change it? [no] 

make: Entering directory '/tmp/modconfig-jMh2Db/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.14.3-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.14.3-2-ARCH/build'
  CC [M]  /tmp/modconfig-jMh2Db/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-jMh2Db/vmci-only/linux/driver.o
In file included from /tmp/modconfig-jMh2Db/vmci-only/linux/vmciKernelIf.c:57:0:
/tmp/modconfig-jMh2Db/vmci-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
    #define DEPRECATED(_fix) do {} while (0)
 ^
In file included from include/linux/kernel.h:13:0,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/percpu.h:44,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/preempt.h:5,
                 from include/linux/preempt.h:18,
                 from include/linux/spinlock.h:50,
                 from include/linux/mmzone.h:7,
                 from include/linux/gfp.h:5,
                 from include/linux/mm.h:9,
                 from /tmp/modconfig-jMh2Db/vmci-only/linux/vmciKernelIf.c:38:
include/linux/printk.h:96:0: note: this is the location of the previous definition
 #define DEPRECATED "[Deprecated]: "
 ^
In file included from /tmp/modconfig-jMh2Db/vmci-only/./shared/vmware.h:39:0,
                 from /tmp/modconfig-jMh2Db/vmci-only/linux/driver.c:62:
/tmp/modconfig-jMh2Db/vmci-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
    #define DEPRECATED(_fix) do {} while (0)
 ^
In file included from include/linux/kernel.h:13:0,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/percpu.h:44,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/current.h:5,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/processor.h:15,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/atomic.h:6,
                 from /tmp/modconfig-jMh2Db/vmci-only/linux/driver.c:24:
include/linux/printk.h:96:0: note: this is the location of the previous definition
 #define DEPRECATED "[Deprecated]: "
 ^
/tmp/modconfig-jMh2Db/vmci-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/modconfig-jMh2Db/vmci-only/linux/driver.c:740:12: error: incompatible types when assigning to type ‘VMCIHostUser’ from type ‘kuid_t’
       user = current_uid();
            ^
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-jMh2Db/vmci-only/linux/driver.o' failed
make[2]: *** [/tmp/modconfig-jMh2Db/vmci-only/linux/driver.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Makefile:1274: recipe for target '_module_/tmp/modconfig-jMh2Db/vmci-only' failed
make[1]: *** [_module_/tmp/modconfig-jMh2Db/vmci-only] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.3-2-ARCH/build'
Makefile:130: recipe for target 'vmci.ko' failed
make: *** [vmci.ko] Error 2
make: Leaving directory '/tmp/modconfig-jMh2Db/vmci-only'

The communication service is used in addition to the standard communication 
between the guest and the host.  The rest of the software provided by VMware 
Tools is designed to work independently of this feature.
If you wish to have the VMCI 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 ] 

make: Entering directory '/tmp/modconfig-paCEZs/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.14.3-2-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/lib/modules/3.14.3-2-ARCH/build'
  CC [M]  /tmp/modconfig-paCEZs/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/modconfig-paCEZs/vmci-only/linux/driver.o
In file included from /tmp/modconfig-paCEZs/vmci-only/./shared/vmware.h:39:0,
                 from /tmp/modconfig-paCEZs/vmci-only/linux/driver.c:62:
/tmp/modconfig-paCEZs/vmci-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
    #define DEPRECATED(_fix) do {} while (0)
 ^
In file included from include/linux/kernel.h:13:0,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/percpu.h:44,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/current.h:5,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/processor.h:15,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/atomic.h:6,
                 from /tmp/modconfig-paCEZs/vmci-only/linux/driver.c:24:
include/linux/printk.h:96:0: note: this is the location of the previous definition
 #define DEPRECATED "[Deprecated]: "
 ^
In file included from /tmp/modconfig-paCEZs/vmci-only/linux/vmciKernelIf.c:57:0:
/tmp/modconfig-paCEZs/vmci-only/./shared/vm_assert.h:259:0: warning: "DEPRECATED" redefined
    #define DEPRECATED(_fix) do {} while (0)
 ^
In file included from include/linux/kernel.h:13:0,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/percpu.h:44,
                 from /usr/lib/modules/3.14.3-2-ARCH/build/arch/x86/include/asm/preempt.h:5,
                 from include/linux/preempt.h:18,
                 from include/linux/spinlock.h:50,
                 from include/linux/mmzone.h:7,
                 from include/linux/gfp.h:5,
                 from include/linux/mm.h:9,
                 from /tmp/modconfig-paCEZs/vmci-only/linux/vmciKernelIf.c:38:
include/linux/printk.h:96:0: note: this is the location of the previous definition
 #define DEPRECATED "[Deprecated]: "
 ^
/tmp/modconfig-paCEZs/vmci-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:
/tmp/modconfig-paCEZs/vmci-only/linux/driver.c:740:12: error: incompatible types when assigning to type ‘VMCIHostUser’ from type ‘kuid_t’
       user = current_uid();
            ^
scripts/Makefile.build:308: recipe for target '/tmp/modconfig-paCEZs/vmci-only/linux/driver.o' failed
make[2]: *** [/tmp/modconfig-paCEZs/vmci-only/linux/driver.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Makefile:1274: recipe for target '_module_/tmp/modconfig-paCEZs/vmci-only' failed
make[1]: *** [_module_/tmp/modconfig-paCEZs/vmci-only] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.14.3-2-ARCH/build'
Makefile:130: recipe for target 'vmci.ko' failed
make: *** [vmci.ko] Error 2
make: Leaving directory '/tmp/modconfig-paCEZs/vmci-only'

The VM communication interface socket family is used in conjunction with the VM
communication interface to provide a new communication path among guests and 
host.  The rest of this software provided by VMware Tools is designed to work 
independently of this feature.  If you wish to have the VSOCK 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 the Enter key to continue.] 

The module vmxnet3 from this package is not supported for kernels >= 3.10. 
Please enable this module in your kernel. You may also have to enable 
HYPERVISOR_GUEST.

The module pvscsi from this package is not supported for kernels >= 3.10. 
Please enable this module in your kernel. You may also have to enable 
HYPERVISOR_GUEST.

The module vmmemctl from this package is not supported for kernels >= 3.10. 
Please enable this module in your kernel. You may also have to enable 
HYPERVISOR_GUEST.

The VMware Host-Guest Filesystem allows for shared folders between the host OS 
and the guest OS in a Fusion or Workstation virtual environment.  Do you wish 
to enable this feature? [yes] 

The vmxnet driver is no longer supported on kernels 3.3 and greater. Please 
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)

The vmblock enables dragging or copying files between host and guest in a 
Fusion or Workstation virtual environment.  Do you wish to enable this feature?
[yes] 

NOTICE:  It appears your system does not have the required fuse packages 
installed.  The VMware blocking filesystem requires the fuse packages and its 
libraries to function properly.  Please install the fuse or fuse-utils package 
using your systems package management utility and re-run this script in order 
to enable the VMware blocking filesystem. 

VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be

enabled/disabled by re-running vmware-config-tools.pl.

Would you like to enable VMware automatic kernel modules?
[no] 



Detected X server version 1.15.1



Distribution provided drivers for Xorg X server are used.

Skipping X configuration because X drivers are not included.


Warning: This script could not find mkinitrd or update-initramfs and cannot 
remake the initrd file!

   Starting Virtual Printing daemon:                                   done
   Checking acpi hot plug                                              done
Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                                   done
   Guest operating system daemon:                                      done
The configuration of VMware Tools 9.6.1 build-1378637 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 "/usr/bin/vmware-toolbox-cmd" from the
command line.

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.

Enjoy,

--the VMware team

Last edited by Skitter (2014-05-14 16:51:50)

Offline

#2 2014-06-05 09:14:08

Coolgeek
Member
Registered: 2014-06-05
Posts: 2

Re: I can't use shared folders feature in VMware

Hi.

I managed to compile open-vm-tools and the kernel module against 3.14.5 kernel.  Here is the tarball with the all the files.

I still have an issue : With vmware-player 6.0.2, I can't acces my shared folder :

root@P146S011b ~ # lsmod | grep hgfs
vmhgfs                 41622  0 
vmw_vmci               47960  2 vmw_vsock_vmci_transport,vmhgfs
root@P146S011b ~ # vmware-hgfsclient 
R
D
C
root@P146S011b ~ # mount -t vmhgfs .host:/R /mnt
Could not add entry to mtab, continuing
root@P146S011b ~ # tail -1 /etc/mtab 
.host:/R /mnt vmhgfs rw,relatime 0 0
root@P146S011b ~ # cd /mnt      
cd:cd:6: not a directory: /mnt
1 root@P146S011b ~ #                 

Forgot to add an install file with a depmod -a inside. You will have to run it by yourself

Offline

Board footer

Powered by FluxBB