M1Max Vagrant box cannot mount shared folders

[ilxqx]

When I saw that Alma supports the arm64 parallel vagrant box, I was very happy, so I started to experience it.

Everything went smoothly, except for a problem with the shared directory:

➜  kube-demo2 vagrant up                           
Bringing machine 'default' up with 'parallels' provider...
==> default: Box 'almalinux/9.aarch64' could not be found. Attempting to find and install...
    default: Box Provider: parallels
    default: Box Version: >= 0
==> default: Loading metadata for box 'almalinux/9.aarch64'
    default: URL: https://vagrantcloud.com/almalinux/9.aarch64
==> default: Adding box 'almalinux/9.aarch64' (v9.2.20230717) for provider: parallels
    default: Downloading: https://vagrantcloud.com/almalinux/boxes/9.aarch64/versions/9.2.20230717/providers/parallels.box
==> default: Successfully added box 'almalinux/9.aarch64' (v9.2.20230717) for 'parallels'!
==> default: Registering VM image from the base box 'almalinux/9.aarch64'...
==> 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: Checking if box 'almalinux/9.aarch64' version '9.2.20230717' is up to date...
==> default: Setting the name of the VM: kube-demo2_default_1691573550481_71634
==> default: Preparing network interfaces based on configuration...
    default: Adapter 0: shared
==> default: Clearing any previously set network interfaces...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 10.211.55.8:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    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...
==> default: Parallels Tools were not detected on this VM! They are required
==> default: for shared folders, time sync and more. If shared folders are not
==> default: working on this machine, please install Parallels Tools within the
==> default: virtual machine and reload your VM.
==> default: Mounting shared folders...
    default: /vagrant => /Users/venus/Vagrant/kube-demo2
Vagrant was unable to mount Parallels Desktop shared folders. This is usually
because the filesystem "prl_fs" is not available. This filesystem is
made 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:

mount -t prl_fs -o uid=1000,gid=1000,_netdev vagrant /vagrant

The error output from the command was:

mount: /vagrant: unknown filesystem type 'prl_fs'.

I am not sure if there is a problem inside the Vagrant box, so I am seeking help here. Can you help me?

[LKHN]

Hi,

Thanks for reporting. Please open an issue on https://github.com/AlmaLinux/cloud-images repository.

Thanks!

[Betti2317]

➜ kube-demo2 vagrant up
Bringing machine 'default' up with 'parallels' provider...
==> default: Box 'almalinux/9.aarch64' could not be found. Attempting to find and install...
default: Box Provider: parallels
default: Box Version: >= 0
==> default: Loading metadata for box 'almalinux/9.aarch64'
default: URL: https://vagrantcloud.com/almalinux/9.aarch64
==> default: Adding box 'almalinux/9.aarch64' (v9.2.20230717) for provider: parallels
default: Downloading: https://vagrantcloud.com/almalinux/boxes/9.aarch64/versions/9.2.20230717/providers/parallels.box
==> default: Successfully added box 'almalinux/9.aarch64' (v9.2.20230717) for 'parallels'!
==> default: Registering VM image from the base box 'almalinux/9.aarch64'...
==> 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: Checking if box 'almalinux/9.aarch64' version '9.2.20230717' is up to date...
==> default: Setting the name of the VM: kube-demo2_default_1691573550481_71634
==> default: Preparing network interfaces based on configuration...
default: Adapter 0: shared
==> default: Clearing any previously set network interfaces...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 10.211.55.8:22
default: SSH username: vagrant
default: SSH auth method: private key
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...
==> default: Parallels Tools were not detected on this VM! They are required
==> default: for shared folders, time sync and more. If shared folders are not
==> default: working on this machine, please install Parallels Tools within the
==> default: virtual machine and reload your VM.
==> default: Mounting shared folders...
default: /vagrant => /Users/venus/Vagrant/kube-demo2
Vagrant was unable to mount Parallels Desktop shared folders. This is usually
because the filesystem "prl_fs" is not available. This filesystem is
made 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:

mount -t prl_fs -o uid=1000,gid=1000,_netdev vagrant /vagrant

The error output from the command was:

mount: /vagrant: unknown filesystem type 'prl_fs'.

[bennyvasquez]

Moved this from the wiki to the /cloud-images repo, for better visibility!

[LKHN]

Moved this from the wiki to the /cloud-images repo, for better visibility!

I was planing to ask to create a new one in cloud-images and close the wiki one. Thanks for migrating!

[LKHN]

Hi, It's expected because we don't include the Parallels Tools in our vagrant boxes.
We don't know yet whether it's legally permitted or not, will update this issue once we find out.