VMware Communities
brandonban6
Contributor
Contributor
Jump to solution

Workstation 9/Fedora 18 Guest Mounting HGFS Failed

Hi All,

I've googled around on this issue and have tried a couple of recommended  solutions, but have failed to figure out my problem thus far.

I'm running Windows 7 Host with Workstation 9, a Fedora 18 Guest. I've successfully installed vmware-tools, which allows me to mount a shared folder for a few days. Then it stops working out of the blue... I can't get it to re-enable for the life of me. I can uninstall vmware-tools, then re-install vmware tools and it works for a few days... but after an update, this goes away again. Any ideas?

All that shows up in /var/log/messages:

Feb 12 09:46:40 be-fed18vm systemd[1]: Detected virtualization 'vmware'.
Feb 12 09:46:40 be-fed18vm kernel: [    0.000000] Hypervisor detected: VMware
Feb 12 09:46:40 be-fed18vm kernel: [    0.000000] ACPI: SRAT 000000007feedb58 004A8 (v02 VMWARE MEMPLUG  06040000 VMW  00000001)
Feb 12 09:46:40 be-fed18vm kernel: [    0.000000] ACPI: HPET 000000007feedb20 00038 (v01 VMWARE VMW HPET 06040000 VMW  00000001)
Feb 12 09:46:40 be-fed18vm kernel: [    0.000000] ACPI: WAET 000000007feedaf8 00028 (v01 VMWARE VMW WAET 06040000 VMW  00000001)
Feb 12 09:46:40 be-fed18vm kernel: [    2.484092] ata2.00: ATAPI: VMware Virtual IDE CDROM Drive, 00000001, max UDMA/33
Feb 12 09:46:40 be-fed18vm kernel: [    2.487548] scsi 1:0:0:0: CD-ROM            NECVMWar VMware IDE CDR10 1.00 PQ: 0 ANSI: 5
Feb 12 09:46:40 be-fed18vm kernel: [    2.737372] usb 2-1: Product: VMware Virtual USB Mouse
Feb 12 09:46:40 be-fed18vm kernel: [    2.737374] usb 2-1: Manufacturer: VMware
Feb 12 09:46:40 be-fed18vm kernel: [    2.747541] input: VMware VMware Virtual USB Mouse as /devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0/input/input3
Feb 12 09:46:40 be-fed18vm kernel: [    2.747611] hid-generic 0003:0E0F:0003.0001: input,hidraw0: USB HID v1.10 Mouse [VMware VMware Virtual USB Mouse] on usb-0000:02:00.0-1/input0
Feb 12 09:46:40 be-fed18vm kernel: [    2.755439] input: VMware VMware Virtual USB Mouse as /devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.1/input/input4
Feb 12 09:46:40 be-fed18vm kernel: [    2.756729] hid-generic 0003:0E0F:0003.0002: input,hidraw1: USB HID v1.10 Mouse [VMware VMware Virtual USB Mouse] on usb-0000:02:00.0-1/input1
Feb 12 09:46:40 be-fed18vm kernel: [    2.987634] usb 2-2: Product: VMware Virtual USB Hub
Feb 12 09:46:40 be-fed18vm kernel: [    3.026317] scsi 2:0:0:0: Direct-Access     VMware,  VMware Virtual S 1.0  PQ: 0 ANSI: 2
Feb 12 09:46:40 be-fed18vm kernel: [    3.519964] usb 2-2.1: Manufacturer: VMware
Feb 12 09:46:41 be-fed18vm vmware-tools[754]: Checking acpi hot plug[  OK  ]
Feb 12 09:46:41 be-fed18vm vmware-tools[754]: Starting VMware Tools services in the virtual machine:
Feb 12 09:46:44 be-fed18vm vmware-tools[754]: Switching to guest configuration:[  OK  ]
Feb 12 09:46:44 be-fed18vm vmware-tools[754]: VM communication interface:[FAILED]
Feb 12 09:46:44 be-fed18vm vmware-tools[754]: VM communication interface socket family:[FAILED]
Feb 12 09:46:44 be-fed18vm vmware-tools[754]: Guest filesystem driver:[  OK  ]
Feb 12 09:46:44 be-fed18vm vmware-tools[754]: Mounting HGFS shares:[FAILED]
Feb 12 09:46:45 be-fed18vm vmware-tools[754]: Blocking file system:[  OK  ]
Feb 12 09:46:47 be-fed18vm vmware-tools[754]: Guest operating system daemon:[  OK  ]
Feb 12 09:46:47 be-fed18vm systemd[1]: vmware-tools.service: control process exited, code=exited status=1
Feb 12 09:46:47 be-fed18vm systemd[1]: Failed to start SYSV: Manages the services needed to run VMware software.
Feb 12 09:46:47 be-fed18vm systemd[1]: Unit vmware-tools.service entered failed state
Feb 12 09:46:57 be-fed18vm systemd[1]: Starting SYSV: Manages the services needed to run VMware software...
Feb 12 09:46:59 be-fed18vm vmware-tools-thinprint[1503]: Starting Virtual Printing daemon:#033[71G done
Feb 12 09:46:59 be-fed18vm systemd[1]: Started SYSV: Manages the services needed to run VMware software.

0 Kudos
1 Solution

Accepted Solutions
sshetty
VMware Employee
VMware Employee
Jump to solution

Hi,

Even though these steps are for Fedora 16 and there may be furhter checks needed and proper handling only comes in when the product matures further on the kernel and the modules on this new Fedora platfrom. You can try these.

http://kb.vmware.com/kb/2016514

View solution in original post

0 Kudos
2 Replies
sshetty
VMware Employee
VMware Employee
Jump to solution

Hi,

Even though these steps are for Fedora 16 and there may be furhter checks needed and proper handling only comes in when the product matures further on the kernel and the modules on this new Fedora platfrom. You can try these.

http://kb.vmware.com/kb/2016514

0 Kudos
brandonban6
Contributor
Contributor
Jump to solution

Thank you!

After Kernel updates; it looks like I had to reconfigure vmware tools. I'm back online now.

thanks again

0 Kudos