How to modify /etc/fstab to load host shared folde...

chunchengch · ‎11-12-2007

I add statement ".host:/media/sda2 /mnt/hgfs vmhgfs defaults 0 0" into /etc/fstab in order to load host shared folder automatically, but it does not seem to work, is there something wrong about this statement?

Thanks for reply!

Liz · ‎11-12-2007

You shouldnt need to add that at all. vmware tools (as long as its actually running) should handle that.

Are you sure you havent installed it but not configured it?

chunchengch · ‎11-13-2007

I ever run command "vmware-toolbox", but there is nothing about shared folder, neither the command " ./vmware-config-tools.pl".

then I try to dig out something from the "Workstation User's Manual"

I run command " mount -t vmhgfs .host:/ /mnt/hgfs" , but it responds error message " Error: cannot mount filesystem: No such device" , then I find in "Workstation User's Manual" a note "Note etc/fstab to specify the location of shared folders. You can edit this file to change or add entries.", so I suppose that I have to modify /etc/fstab to load the host shared folder automatically, but it does not work either.

So, how can I do ? thanks !

AWo · ‎11-13-2007

Like Liz wrote, you shouldn't have to care about. If the vmware tools are installed you should find the following lines in your fstab:

\# Beginning of the block added by the VMware software

.host:/ /mnt/hgfs vmhgfs defaults,ttl=5 0 0

\# End of the block added by the VMware software

Have you enabled and configured the shared folder correctly under the guest options?

AWo

Message was edited by: AWo

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

chunchengch · ‎11-13-2007

Beginning of the block added by the VMware software

.host:/ /mnt/hgfs vmhgfs defaults,ttl=5 0 0

End of the block added by the VMware software

I did not find similar lines in my /etc/fstab after the vmware tools was installed, that is weird.

I am very sure the vmware tools is installed, because I can change the resolution of monitor, here is the link of screenshot

http://picasaweb.google.com/chunchengch/Fedora8/photo#5132271763129958658

AWo · ‎11-13-2007

I guess your second thread points to the same direction, so I'll continue here:

Go to your guest console and enter "ps -e | grep ".vm." You should get a list of some vmware tools processes running:

1765 ? 00:00:00 vmhgfs

3589 ? 00:00:00 vmmemctl

3637 ? 00:00:02 vmware-guestd

4090 ? 00:00:01 vmware-user

Is anyone missing?

Did you use the .rpm or the .tar file for installing vmware tools?

AWo

Message was edited by: AWo

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

Liz · ‎11-13-2007

Please post your vmx file in th is post or the other one.

chunchengch · ‎11-13-2007

Here is the output

$ ps -e | grep ".vm."

1640 ? 00:00:00 vmmemctl

1688 ? 00:00:03 vmware-guestd

I use the .rpm file to install VMware Tools.

chunchengch · ‎11-13-2007

The host is Ubuntu 7.10

Here is the fedora8.vmx file

#!/usr/bin/vmware

config.version = "8"

virtualHW.version = "6"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "512"

MemAllowAutoScaleDown = "FALSE"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Fedora8.vmdk"

ide1:0.present = "FALSE"

ide1:0.autodetect = "TRUE"

ide1:0.deviceType = "cdrom-raw"

floppy0.startConnected = "FALSE"

floppy0.autodetect = "TRUE"

ethernet0.present = "TRUE"

ethernet0.connectionType = "nat"

ethernet0.wakeOnPcktRcv = "FALSE"

usb.present = "TRUE"

ehci.present = "TRUE"

sound.present = "TRUE"

sound.fileName = "-1"

sound.autodetect = "TRUE"

svga.autodetect = "TRUE"

pciBridge0.present = "TRUE"

isolation.tools.hgfs.disable = "FALSE"

displayName = "Fedora8"

guestOS = "other26xlinux"

nvram = "Fedora8.nvram"

deploymentPlatform = "windows"

virtualHW.productCompatibility = "hosted"

RemoteDisplay.vnc.port = "0"

tools.upgrade.policy = "upgradeAtPowerCycle"

numvcpus = "2"

scsi0:1.present = "FALSE"

scsi0:1.autodetect = "TRUE"

scsi0:1.deviceType = "cdrom-raw"

floppy0.fileName = "/dev/fd0"

snapshot.disabled = "TRUE"

annotation = "Fedora 8|0A|0AVMware tools is installed"

ethernet0.addressType = "generated"

uuid.location = "56 4d xx xx xx xx xx xx-xx xx xx 1c 33 82 c4 ad"

uuid.bios = "56 4d xx xx xx xx xx xx-xx xx xx xx xx 82 c4 ad"

scsi0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "32"

sound.pciSlotNumber = "33"

ehci.pciSlotNumber = "34"

ethernet0.generatedAddress = "00:xx:xx:xx:xx:ad"

ethernet0.generatedAddressOffset = "0"

extendedConfigFile = "Fedora8.vmxf"

ide0:0.present = "TRUE"

ide0:0.autodetect = "TRUE"

ide0:0.deviceType = "cdrom-raw"

tools.remindInstall = "FALSE"

sharedFolder.option = "alwaysEnabled"

sharedFolder0.present = "TRUE"

sharedFolder0.enabled = "TRUE"

sharedFolder0.readAccess = "TRUE"

sharedFolder0.writeAccess = "TRUE"

sharedFolder0.hostPath = "/media/sda2"

sharedFolder0.guestName = "sda2"

sharedFolder0.expiration = "never"

sharedFolder.maxNum = "1"

scsi0:1.startConnected = "TRUE"

scsi0:1.fileName = "auto detect"

ide0:0.startConnected = "FALSE"

ide0:0.fileName = "auto detect"

tools.syncTime = "TRUE"

gui.fullScreenAtPowerOn = "TRUE"

chipset.useAcpiBattery = "TRUE"

chipset.useApmBattery = "TRUE"

checkpoint.vmState = "Fedora8.vmss"

AWo · ‎11-13-2007

vmhgfs should be running for using shared folders (even if the option is disabled under the guest settings). I don't know why it isn't running, but can you try to use the vmware tools .tar file? This means you may have to compile the tools, therefore you need the kernel source and a c compiler (gcc) installed. After unpacking it you find a perl script which starts the process.

You can also have a look in you logs, if there were any error message, telling that vmhgfs could not be started. Go to /var/logs and enter 'grep -r "vmhgfs" *' and watch out for errors.

AWo

Message was edited by: AWo

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

Liz · ‎11-13-2007

This may seem an odd question but can you confirm you havent made the guest under workstatino but are now running server (as server doesnt support shared folders)

chunchengch · ‎11-13-2007

I run the command grep -r "vmhgfs" *, but nothing appears.

I re-install VMware Tools with .tar file and then run ./vmware-config-tools.pl, but nothing changes, it is really wierd.

BTW, nothing is added into /etc/fstab after installation.

here are some outputs I run vmware-tools

ps -e | grep ".vm."

1676 ? 00:00:00 vmmemctl

1701 ? 00:00:26 vmware-guestd

vmware-user

Warning: vmware-user failed to initialize blocking driver.

Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": libgnomebreakpad.so: cannot open shared object file: No such file or directory

Warning: Error in the RPC recieve loop: RpcIn: Unable to send

Warning: Another instance of VMwareUser may be running.

vmware-hgfsclient

sda2

./vmware-config-tools.pl

Stopping VMware Tools services in the virtual machine:

Guest operating system daemon:

Guest memory manager:

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)?

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?

Extracting the sources of the vmmemctl module.

Building the vmmemctl module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config15/vmmemctl-only'

make -C /lib/modules/2.6.23.1-49.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'

CC /tmp/vmware-config15/vmmemctl-only/os.o

SHIPPED /tmp/vmware-config15/vmmemctl-only/vmmemctl1.o

LD /tmp/vmware-config15/vmmemctl-only/vmmemctl.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/vmware-config15/vmmemctl-only/vmmemctl.mod.o

LD /tmp/vmware-config15/vmmemctl-only/vmmemctl.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'

cp -f vmmemctl.ko ./../vmmemctl.o

make: Leaving directory `/tmp/vmware-config15/vmmemctl-only'

The module loads perfectly in the running kernel.

Extracting the sources of the vmhgfs module.

Building the vmhgfs module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config15/vmhgfs-only'

make -C /lib/modules/2.6.23.1-49.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'

CC /tmp/vmware-config15/vmhgfs-only/backdoor.o

CC /tmp/vmware-config15/vmhgfs-only/backdoorGcc32.o

CC /tmp/vmware-config15/vmhgfs-only/bdhandler.o

CC /tmp/vmware-config15/vmhgfs-only/cpName.o

CC /tmp/vmware-config15/vmhgfs-only/cpNameLinux.o

CC /tmp/vmware-config15/vmhgfs-only/cpNameLite.o

CC /tmp/vmware-config15/vmhgfs-only/dbllnklst.o

CC /tmp/vmware-config15/vmhgfs-only/dentry.o

CC /tmp/vmware-config15/vmhgfs-only/dir.o

CC /tmp/vmware-config15/vmhgfs-only/eventManager.o

CC /tmp/vmware-config15/vmhgfs-only/file.o

/tmp/vmware-config15/vmhgfs-only/file.c:100: error: unknown field ‘sendfile’ specified in initializer

/tmp/vmware-config15/vmhgfs-only/file.c:100: warning: initialization from incompatible pointer type

/tmp/vmware-config15/vmhgfs-only/file.c: In function ‘HgfsSendfile’:

/tmp/vmware-config15/vmhgfs-only/file.c:1011: error: implicit declaration of function ‘generic_file_sendfile’

make[2]: *** Error 1

make[1]: *** ~~module/tmp/vmware-config15/vmhgfs-only~~ Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'

make: *** Error 2

make: Leaving directory `/tmp/vmware-config15/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.

pcnet32 31429 0

Unloading pcnet32 module

Extracting the sources of the vmxnet module.

Building the vmxnet module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config16/vmxnet-only'

make -C /lib/modules/2.6.23.1-49.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'

CC /tmp/vmware-config16/vmxnet-only/vmxnet.o

/tmp/vmware-config16/vmxnet-only/vmxnet.c: In function ‘vmxnet_tx’:

/tmp/vmware-config16/vmxnet-only/vmxnet.c:1220: error: ‘struct sk_buff’ has no member named ‘nh’

/tmp/vmware-config16/vmxnet-only/vmxnet.c:1222: error: ‘struct sk_buff’ has no member named ‘nh’

/tmp/vmware-config16/vmxnet-only/vmxnet.c:1223: error: ‘struct sk_buff’ has no member named ‘h’

/tmp/vmware-config16/vmxnet-only/vmxnet.c:1226: error: ‘struct sk_buff’ has no member named ‘nh’

/tmp/vmware-config16/vmxnet-only/vmxnet.c:1367: error: ‘struct sk_buff’ has no member named ‘h’

/tmp/vmware-config16/vmxnet-only/vmxnet.c:1368: error: ‘struct sk_buff’ has no member named ‘nh’

/tmp/vmware-config16/vmxnet-only/vmxnet.c:1445: error: ‘struct sk_buff’ has no member named ‘h’

/tmp/vmware-config16/vmxnet-only/vmxnet.c:1446: error: ‘struct sk_buff’ has no member named ‘h’

make[2]: *** Error 1

make[1]: *** ~~module/tmp/vmware-config16/vmxnet-only~~ Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'

make: *** Error 2

make: Leaving directory `/tmp/vmware-config16/vmxnet-only'

Unable to build the vmxnet module.

The fast network device driver (vmxnet module) is used only for our fast

networking interface. The rest of the software provided by VMware Tools is

designed to work independently of this feature.

If you wish to have the fast network driver enabled, 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.

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config17/vmblock-only'

make -C /lib/modules/2.6.23.1-49.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'

CC /tmp/vmware-config17/vmblock-only/linux/block.o

/tmp/vmware-config17/vmblock-only/linux/block.c: In function ‘BlockInit’:

/tmp/vmware-config17/vmblock-only/linux/block.c:66: error: too many arguments to function ‘kmem_cache_create’

make[2]: *** Error 1

make[1]: *** ~~module/tmp/vmware-config17/vmblock-only~~ Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'

make: *** Error 2

make: Leaving directory `/tmp/vmware-config17/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.

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?

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config18/vmci-only'

make -C /lib/modules/2.6.23.1-49.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'

CC /tmp/vmware-config18/vmci-only/dbllnklst.o

CC /tmp/vmware-config18/vmci-only/kernelStubsLinux.o

CC /tmp/vmware-config18/vmci-only/vmciDatagram.o

CC /tmp/vmware-config18/vmci-only/vmci_drv.o

/tmp/vmware-config18/vmci-only/vmci_drv.c: In function ‘vmci_exit’:

/tmp/vmware-config18/vmci-only/vmci_drv.c:206: error: void value not ignored as it ought to be

make[2]: *** Error 1

make[1]: *** ~~module/tmp/vmware-config18/vmci-only~~ Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'

make: *** Error 2

make: Leaving directory `/tmp/vmware-config18/vmci-only'

Unable to build the vmci module.

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.

Detected X.org version 1.3.

No drivers for X.org version: 1.3.

Do you want to change the display size that X starts with? (yes/no)

Starting VMware Tools services in the virtual machine:

Switching to guest configuration:

Guest memory manager:

DMA setup:

Guest operating system daemon:

The configuration of VMware Tools 6.0.0 build-45731 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 make use of the virtual printer, you will need to restart the CUPS service

If you wish to configure any experimental features, please run the following

command: "vmware-config-tools.pl --experimental".

Enjoy,

--the VMware team

rchin · ‎11-13-2007

test

WS 5.5.1-19175

Host: XP Pro SP2

Guests: XP Pro, Ubuntu7.04.

WS 6.5.1-126130 Host: Vista SP1 Guests: Ubuntu 8.04, XP

Liz · ‎11-14-2007

> Building the vmhgfs module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config15/vmhgfs-only'
make -C /lib/modules/2.6.23.1-49.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'
CC /tmp/vmware-config15/vmhgfs-only/backdoor.o
CC /tmp/vmware-config15/vmhgfs-only/backdoorGcc32.o
CC /tmp/vmware-config15/vmhgfs-only/bdhandler.o
CC /tmp/vmware-config15/vmhgfs-only/cpName.o
CC /tmp/vmware-config15/vmhgfs-only/cpNameLinux.o
CC /tmp/vmware-config15/vmhgfs-only/cpNameLite.o
CC /tmp/vmware-config15/vmhgfs-only/dbllnklst.o
CC /tmp/vmware-config15/vmhgfs-only/dentry.o
CC /tmp/vmware-config15/vmhgfs-only/dir.o
CC /tmp/vmware-config15/vmhgfs-only/eventManager.o
CC /tmp/vmware-config15/vmhgfs-only/file.o
/tmp/vmware-config15/vmhgfs-only/file.c:100: error: unknown field ‘sendfile’ specified in initializer
/tmp/vmware-config15/vmhgfs-only/file.c:100: warning: initialization from incompatible pointer type
/tmp/vmware-config15/vmhgfs-only/file.c: In function ‘HgfsSendfile’:
/tmp/vmware-config15/vmhgfs-only/file.c:1011: error: implicit declaration of function ‘generic_file_sendfile’
make[2]: *** Error 1
make[1]: *** ~~module/tmp/vmware-config15/vmhgfs-only~~ Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-49.fc8-i686'
make: *** Error 2
make: Leaving directory `/tmp/vmware-config15/vmhgfs-only'
Unable to build the vmhgfs module.

this seems to be your problem, it couldnt make the shared folders part of your kernel - you probably need the any-any update.

AWo · ‎11-14-2007

this seems to be your problem, it couldnt make the shared folders part of your kernel - you probably need the any-any update.

any-any update?

AWo

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

chunchengch · ‎11-14-2007

yes, I had download vmware-any-any-update114.tar.bz2 and run the runme.pl, but the problem is still there.

any more solution? thanks a lot!

Liz · ‎11-14-2007

im guessing a newer any-any is possibly needed or you need to revert to an older kernel in the guest

bigDavefromTren · ‎05-13-2010

Our linux team has some concern with the following line in the fstab stating:

fstab entries can sometimes result in a server not coming back up when

rebooted. We would recommend commenting this entry out."

Do you know the purpose of the following entry in /etc/fstab being

added by VMware Tools on Linux? Do you see any reason to keep it?

Beginning of the block added by the VMware software

.host:/ /mnt/hgfs vmhgfs defaults,ttl=5 0 0

End of the block added by the VMware software

BigD

mpg187 · ‎09-04-2016

"You shouldnt need to add that at all. vmware tools (as long as its actually running) should handle that."

You're right it does mount them, but I had to edit fstab to change to the mount point I wanted to use.

grokit · ‎09-27-2016

The information in this thread is out of date for Ubuntu Server 16.04 as of 2016-09-27

vmware-tools in not installed nor do you need it. open-vm-tools is automagically installed and works fine.

The correct /etc/fstab entry is:

.host:/ /mnt/hgfs fuse.vmhgfs-fuse uid=1000,gid=1000,defaults 0 0

You may not need the uid and gid but I prefer to explicitly define root as the owner on a server.

That line also assumes the folder /mnt/hgfs exists, you can of course change it to anything you want.

All

How to modify /etc/fstab to load host shared folder automatically?