VMware Communities
djd_oz
Contributor
Contributor

Shard drives unavailable on Ubuntu Guest Machine

Hey there,

Previously I've setup a shared folder and it has been working fine for many months. I believe on my Windows hosts there has been some updates recently, I'm currently running WIndows 10 19042.746.

Initially when I first started up VMWare, I noticed that the shared folder settings in VMWare was greyed out and I was unable to modify this. I then updated to the latest VMWare Tools to 11.0.5.17716 (build-15389592) and this seems to fix the issue where this was greyed out. However, the shared drives were still not appearing under /mnt/hgfs.

Some other messages that I've been seeing now which weren't previosly there are,

1) Cannot connect the virtual device satapi0:1 because no corresponding device is available on the host.

2) SMBus Host controller not available

I've alredy tried the below remedies however, it hasn't resolved the issue.

1) Turn off Windows Defender Firewall

2) Change the Windows Registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order to "vmhgfs,RDPNP, LanmanWorkstation,webclient"

3)Restart/Reboot both the Host and Guest Machines

Is there anything else that I can check/troubleshoot?

 

Reply
0 Kudos
2 Replies
djd_oz
Contributor
Contributor

o.k. I found a workaround.

Firstly, I checked the /etc/fstab file and it does not contain an entry to automount the Shared Folders. I then manually added the following line into this file as per the article in the below link. 

.host:/ /mnt/hgfs vmhgfs defaults 0 0

https://docs.vmware.com/en/VMware-Workstation-Player-for-Windows/12.0/com.vmware.player.win.using.do...

After rebooting the guest machine, it still didn't work and came up with some error messages that it could not mount what I added above.

And then, I tried manully mounting this with the below command and it worked.

sudo mount -t fuse.vmhgfs-fuse .host:/ /mnt/hgfs -o allow_other

 

Reply
0 Kudos
djd_oz
Contributor
Contributor

**bleep**, it stoped working again and the workaround didn't work this time.

Reply
0 Kudos