Comment 8 for bug 1448134

okay thats specifically a vmblock-fuse service issue.
open-vm-tools-desktop package provides the
/lib/systemd/system/run-vmblock\x2dfuse.mount
which is the service that is taking so long.

This isn't a systemd generated mount from parsing fstab as I first thought.
It should be an explicit unit file on your system placed there and enabled by the open-vm-tools-desktop package.

And I'm not familiar enough with using vmware to suggest how to troubleshoot that particular service.
If you aren't using vmware tools.. you can probably disable that mount unit without loss of functionality.

But since open-vm-tools-desktop has a systemd specific mount file.. for the vmware-fuse mount point... I have to wonder.. how does this particular mount point get mounted when booting under upstart? Or did that fuse mount not get mounted before? I'm not seeing an equivalent upstart job or sysvinit script in trusty/vivid packaging of the open-vm-tools-desktop package that would have ensured the same mount attempt under sysV or upstart. Though I may have just not seen it. This looks like a vivid specific packaging addition to open-vm-tools-desktop. Someone who uses vmware regularly should look into that more closely.