add VirtualBox aarch64 (arm64) Vagrant boxes #376

Activity

1. yuravk

   added a commit that references this issue on Oct 13, 2026

   feat(vagrant): build the VirtualBox aarch64 box under QEMU, the Paral…

   ...

   9eb2982
2. yuravk commented on Oct 13, 2026

   

   yuravk

   on Oct 13, 2026

   Collaborator

   More actions

   Greetings @vchepkov

   Thanks for the request.

   We have a first AlmaLinux 9.8 virtualbox/arm64 box for testing, built with the VirtualBox 7.2.20 Guest Additions. We can't boot VirtualBox ARM guests on our build infrastructure, so we would appreciate it if you could check it on your Apple Silicon Mac:

   vagrant box add --name almalinux/9-arm64-test --architecture arm64 \
     https://almalinux-cloud.s3.amazonaws.com/images/9/9.8/vagrant/20261013101919/AlmaLinux-9-Vagrant-virtualbox-9.8-20261013.aarch64.box
   
   mkdir alma9-arm64-test && cd alma9-arm64-test
   vagrant init almalinux/9-arm64-test
   vagrant up --provider virtualbox
   vagrant ssh -c 'cat /etc/almalinux-release; uname -m; lsmod | grep vbox; mount | grep /vagrant'

   (--architecture arm64 is needed when adding a box from a URL; without it Vagrant registers the box for amd64.)

   Please let us know:

   • whether the box boots and vagrant ssh works;
   • whether /vagrant is mounted (shared folder via vboxsf);
   • your macOS, VirtualBox and Vagrant versions.

   If it works, we will build the AlmaLinux 10 and Kitten 10 boxes the same way.

   Regards.
3. vchepkov commented on Oct 13, 2026

   

   vchepkov

   on Oct 13, 2026

   Author

   More actions

   Thanks @yuravk, tested on Apple Silicon and it works:

   • box boots and 'vagrant ssh' works
   • /vagrant is mounted via vboxsf (rw); Vagrantfile visible
   • macOS 26.6.2 (arm64), VirtualBox 7.2.20r175154, Vagrant 2.4.9

   $ vagrant ssh -c 'cat /etc/almalinux-release; uname -m; lsmod | grep vbox; mount | grep /vagrant'
   AlmaLinux release 9.8 (Olive Jaguar)
   aarch64
   vboxsf                 81920  1
   vboxguest             475136  2 vboxsf
   vagrant on /vagrant type vboxsf (rw,nodev,relatime,iocharset=utf8,uid=1000,gid=1000)
   
4. yuravk commented on Oct 14, 2026

   

   yuravk

   on Oct 14, 2026

   Collaborator

   More actions

   Thanks a lot for testing @vchepkov!

   We now have the AlmaLinux 10.2 and Kitten 10 virtualbox/arm64 boxes built the same way. Could you please check them too, with the same steps as before?

   vagrant box add --name almalinux/10-arm64-test --architecture arm64 \
     https://almalinux-cloud.s3.amazonaws.com/images/10/10.2/vagrant/20261014080914/AlmaLinux-10-Vagrant-virtualbox-10.2-20261014.0.aarch64.box
   
   vagrant box add --name almalinux/10-kitten-arm64-test --architecture arm64 \
     https://almalinux-cloud.s3.amazonaws.com/images/kitten/10/vagrant/20261014085124/AlmaLinux-Kitten-Vagrant-virtualbox-10-20261014.0.aarch64.box

   Then vagrant init almalinux/10-arm64-test (or almalinux/10-kitten-arm64-test) in a new directory, vagrant up --provider virtualbox, and:

   vagrant ssh -c 'cat /etc/almalinux-release; uname -m; lsmod | grep vbox; mount | grep /vagrant'
5. vchepkov commented on Oct 14, 2026

   

   vchepkov

   on Oct 14, 2026

   Author

   More actions

   Thanks @yuravk, both boxes work on Apple Silicon (same host: macOS 26.6.2, VirtualBox 7.2.20r175154, Vagrant 2.4.9):

   • both boot and 'vagrant ssh' works
   • /vagrant is mounted via vboxsf (rw); Vagrantfile visible

   AlmaLinux 10.2:

   AlmaLinux release 10.2 (Lavender Lion)
   aarch64
   6.12.0-211.65.1.el10_2.aarch64
   vboxsf                 86016  1
   vboxguest             466944  2 vboxsf
   vagrant on /vagrant type vboxsf (rw,nodev,relatime,iocharset=utf8,uid=1000,gid=1000,_netdev)
   

   Kitten 10:

   AlmaLinux Kitten release 10 (Lion Cub)
   aarch64
   6.12.0-273.el10.aarch64
   vboxsf                 86016  1
   vboxguest             466944  2 vboxsf
   vagrant on /vagrant type vboxsf (rw,nodev,relatime,iocharset=utf8,uid=1000,gid=1000,_netdev)
   
6. andrewlukoshko

   closed this as completedin #377on Oct 14, 2026
7. yuravk commented on Oct 14, 2026

   

   yuravk

   on Oct 14, 2026

   Collaborator

   More actions

   Thanks again @vchepkov for testing!

   The support is merged (#377), so the virtualbox/arm64 boxes are now part of our builds. As HCP Vagrant no longer accepts new box versions and shuts down on 2026-12-31 (see #363), we publish them through our own catalog on AWS S3:

   export VAGRANT_SERVER_URL=https://almalinux-cloud.s3.us-east-1.amazonaws.com/vagrant
   vagrant box add almalinux/9 --provider virtualbox --architecture arm64
   vagrant box add almalinux/10 --provider virtualbox --architecture arm64
   vagrant box add almalinux/10-kitten --provider virtualbox --architecture arm64

   or set config.vm.box_url = "https://almalinux-cloud.s3.us-east-1.amazonaws.com/vagrant/almalinux/10" (for example) in the Vagrantfile. The catalog is still a preview, and its address may change before HCP shuts down; we will announce the final one.