Skip to content

AppArmor blocking prl_fsd/fusermount3 calls by default in Ubuntu 26.04 #522

@mpdude

Description

@mpdude

I recently updates Paralles to version 26.3.3 (57507) and started a new Ubuntu 26.04 box for the first time. Upon boot, mounting the prl_fsd filesystem fails.

I built the box myself based on the "Bento" project and I can tell for sure that Parallels Tools are installed in the most recent version.

$ vagrant up
Bringing machine 'default' up with 'parallels' provider...
==> default: Registering VM image from the base box 'webfactory-de/ubuntu-26.04'...
==> default: Creating new virtual machine as a linked clone of the box image...
==> default: Unregistering the box VM image...
==> default: Setting the default configuration for VM...
==> default: Setting the name of the VM: wf-development-vm-2604
==> default: Preparing network interfaces based on configuration...
    default: Adapter 0: shared
    default: Adapter 1: hostonly
==> default: Clearing any previously set network interfaces...
==> default: Forwarding ports...
    default: 22 => 2227
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 10.211.55.94:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection refused. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for Parallels Tools installed on the VM...
vagrant-dns: trying to stop process with pid 24072 sending TERM and waiting 20s ...
vagrant-dns: process with pid 24072 successfully stopped.
vagrant-dns: process with pid 27326 started.
==> default: Restarted DNS Service
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /Volumes/Projekte => /var/www
Vagrant was unable to mount Parallels Desktop shared folders. This is usually
because the filesystem "prl_fs" is not available OR you are passing
unsupported mount options to prl_fsd daemon for supported options please refer
to the prl_fsd --help in VM.
"prl_fs"/"prl_fsd" are available via the Parallels Tools and kernel module.
Please verify that these guest tools are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

            if [ -f /usr/bin/prl_fsd ]; then
              prl_fsd /var/www -o nonempty,noatime,nodev,nosuid,big_writes,fsname=var_www,subtype=prl_fsd --share --sf=var_www
            else
              mount -t prl_fs -o share,nonempty,noatime,nodev,nosuid,uid=1000,gid=1000,_netdev var_www /var/www
            fi


The error output from the command was:

fusermount: mount failed: Permission denied

It's a bit hard to tell where this might come from. The same Vagrantfile previously worked on an Ubuntu 24.04 box.

What would be helpful for troubleshooting?

Running sudo prl_fsd /var/www -o nonempty,noatime,nodev,nosuid,big_writes,fsname=var_www,subtype=prl_fsd --share --sf=var_www from inside the box gives the same error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions