Add a check for prl_fsd and use that to mount if it exists.

[WardF]

• Fixes prl_fs filesystem not found with latest parallels version (20.2.0) #483

I've been encountering the same issue outlined in #483 and other places. This change checks for prl_fsd and, if found, uses it to mount the defined shares in the expected locations; otherwise it falls back to the old mount command, accommodating older installs as well as VMs on Parallels 20 that have not yet updated the tools to 20.2.0+.

My test matrix for this is very narrow, but it works; Parallels, and Vagrant, are essential to my own developer workflow. I've been using Parallels since version 2.0, I'm not inclined to move away from it unless I had to, but this issue going unresolved has threatened that. Hopefully it helps!

For anybody wanting to test this locally, this file should replace the one in

${HOME}/.vagrant.d/gems/3.3.6/gems/vagrant-parallels-2.4.2/lib/vagrant-parallels/guest_cap/linux

[sai-kumar-peddireddy]

@WardF thanks for your contribution... proposed solution is LGTM..this was supposed to be raised by me but due to my internal setup and vagrant box issues I was not able to do this on time.

[bjoernhaeuser]

Hi team,

thanks for the quick merge on this! I see that a new version is tagged, but missing on rubygems. Not sure if this is expected, but it would be lovely to get the new version also to rubygems so that it can be easily installed locally.

Thank you!

[BodoHuber]

@WardF thanks for committing that patch. Please let me ask for the unmount part of the code where no such check for prl_fsd is done. Shouldn't be the same if then else construction when unmounting to call fusermount instead of umount? I also wonder about not existing mount options, e.g. the option share seems to be not supported, I got errors when accidentally using it.

[WardF]

Thanks to the team for getting this merged, glad it's helpful, I'm not a Ruby dev so it took me a while to figure out even where to look to change this XD. Are there public facing development docs anywhere?

@BodoHuber I wish I had an answer for you; umount appears to work fine for me, but mounting and unmounting beyond at-boot/at-provisioning is not part of my workflow, nor are there any (that I'm aware of) prl_fs-specific components to my daily use. I just need /vagrant to exist when I expect it to, or a number of my workflows will fail, including provisioning and building of my local Vagrant boxes. I've been getting by well enough by just not updating Parallels Tools, but that's just not a long term solution.

I hope they're able to figure this out; I adore Parallels as my VM provider. But kernel/filesystem level development is not my area of expertise, and frankly, I'm glad there are folk who love it to do that work instead of me XD. I'll stick to system library work.

That's a lot of words to say "I haven't noticed a problem with umount" but, as mentioned in the PR notes, my use case and test matrix is very, very narrow. I work with Ubuntu 20.04-24.10, sometimes debian, and I just need /vagrant to exist at boot.