almalinux/9.aarch64 vagrant box not working with m1 mac

[paulmaunders]

Hello!

I tried to run the AlmaLinux 9 aarch64 vagrant box with my M2 Macbook Air today but it failed at the Mounting shared folder step because Parallels Tools are not installed.

Here is the full output:

paulmaunders@pauls-air-m2 test-parallels-alma9 % 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.0.20220905) for provider: parallels
    default: Downloading: https://vagrantcloud.com/almalinux/boxes/9.aarch64/versions/9.0.20220905/providers/parallels.box
    default: Calculating and comparing box checksum...
==> default: Successfully added box 'almalinux/9.aarch64' (v9.0.20220905) 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.0.20220905' is up to date...
==> default: Setting the name of the VM: test-parallels-alma9_default_1666801345265_43507
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> 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: :22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection refused. Retrying...
    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...
==> 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/paulmaunders/Documents/Code/test-parallels-alma9
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'.

[paulmaunders]

I couldn't find any support for the AlmaLinux 9 aarch64 box in this project so I have added configuration to support it in this pull request: https://github.com/AlmaLinux/cloud-images/pull/115

This mostly works but has the same problem with the parallels tools not being installed correctly.

[paulmaunders]

It looks like this is a known problem with Parallels Tools not currently supporting RHEL 9: https://forum.parallels.com/threads/parallels-tools-do-not-install-on-rhel9.357546

[klesher]

It looks like this is a known problem with Parallels Tools not currently supporting RHEL 9: https://forum.parallels.com/threads/parallels-tools-do-not-install-on-rhel9.357546

I was able to successfully install Parallels Tools as of yesterday (2023-02-23). Another comment in that post also notes they were successful.

I'm running: Parallels v18.2.0 (53488) AlmaLinux 9.1 via Vagrant Box almalinux/9.aarch64 (v9.1.20230122)

@paulmaunders - Based on the work you did in AlmaLinux/wiki#115, do we maybe just need a new box version released at this point?

[klesher]

Also confirmed that enabling guest tool updates in the Vagrant file completes successfully. I can use this as a workaround in the meantime, but having Parallels Tools baked into the Vagrant box would save some significant boot time. My use-case is testing Ansible changes, so I'm spinning boxes up & down constantly as I make changes.

node.vm.provider "parallels" do |prl|
    prl.update_guest_tools = true
end

==> alma9: Machine booted and ready!
==> alma9: Checking for Parallels Tools installed on the VM...
==> alma9: Parallels Tools were not detected on this VM! They are required
==> alma9: for shared folders, time sync and more. If shared folders are not
==> alma9: working on this machine, please install Parallels Tools within the
==> alma9: virtual machine and reload your VM.
==> alma9: Installing the proper version of Parallels Tools. This may take a few minutes...
==> alma9: Parallels Tools have been installed. Rebooting the VM...
==> alma9: Attempting graceful shutdown of VM...
==> alma9: Booting VM...
==> alma9: Waiting for machine to boot. This may take a few minutes...
==> alma9: Machine booted and ready!
==> alma9: Mounting shared folders...
    alma9: /vagrant => /Users/klesher/code/ansible/tests

[ilxqx]

Same issue: https://github.com/AlmaLinux/cloud-images/issues/163