Kernel Filesystem driver still referecned in /etc/fstab when on Parallels 20.2.x with FUSE driver mount

[Sn0wCrack]

I've noticed that while on Parallels 20.2.0 or above, despite the FUSE driver being used to mount shared folders, the /etc/fstab is still generated with entries that would attempt to mount the same paths using the prl_fs kernel driver.

This doesn't appear to be causing me issues currently, but should these /etc/fstab entries not be using the fuse mount type instead now?

Below is my (redacted slightly) /etc/fstab from an Ubuntu 24.04 vagrant setup.

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
/dev/disk/by-id/dm-uuid-LVM-7vdBRrBadXi6RgoniOgcVyDDdeumIgE0ncAm3EXUaf4WQqwIhNOqaOTtP7KTfHdI / ext4 defaults 0 1
# /boot was on /dev/sda2 during curtin installation
/dev/disk/by-uuid/b54de100-3edd-4ac5-9d9c-973b7b4d83eb /boot ext4 defaults 0 1
# /boot/efi was on /dev/sda1 during curtin installation
/dev/disk/by-uuid/6CC6-97AA /boot/efi vfat defaults 0 1
/swap.img	none	swap	sw	0	0
#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
home_vagrant_redacted /path/to/redacted prl_fs _netdev,uid=1000,gid=1000,_netdev 0 0
vagrant /vagrant prl_fs uid=1000,gid=1000,_netdev 0 0
#VAGRANT-END

[stephenreay]

I'm seeing this too, and it does actually cause an issue: when then VM is rebooted, it tries to mount the shared directory using prl_fs, and fails.

Removing the entry after booting works, but it's put back every time the VM is booted.

This seems to be related to the 'persist_mount_shared_folder' capability on Linux guests https://github.com/hashicorp/vagrant/blob/ab0a515f3b92e2d834c6b075b3ae5fc7ec321d52/plugins/guests/linux/cap/persist_mount_shared_folder.rb

A workaround for now, is to disable fstab modifications in your Vagrantfile (I've done this in a global Vagrantfile, but it should work fine in a project-specific one too):

    config.vm.provider "parallels" do |prl|
            config.vm.allow_fstab_modification = false
    end