Rocky Linux 10 Vagrant box points to deleted image

Rocky Linux Help & Support
, ,
1

The Box configuration for Rocky Linux 10 in Vagrant cloud points to the deleted image: https://dl.rockylinux.org/pub/rocky/10/images/x86_64/Rocky-10-Vagrant-Libvirt-10.0-20250609.1.x86_64.box When trying to bring up the image with current configuration user sees the following error:

2025-12-09T11:59:05 INFO: node001: Downloading: ``https://vagrantcloud.com/rockylinux/boxes/10/versions/0.0.0/providers/libvirt/amd64/vagrant.box
2025-12-09T11:59:08 ERROR: An error occurred while downloading the remote file. The error
2025-12-09T11:59:08 ERROR: message, if any, is reproduced below. Please fix this error and try again.
2025-12-09T11:59:08 ERROR: The requested URL returned error: 404

Please update the configuration in Vagrant cloud, so it would point to the latest image as it is done in Rocky Linux 9 and Rocky Linux 8 cloud configurations.

2

This has probably been an issue for some time now, so i solved it by adding the following to my Vagrantfile

config.vm.box_url = 'https://dl.rockylinux.org/pub/rocky/10/images/x86_64/Rocky-10-Vagrant-Vbox-10.1-20251116.0.x86_64.box'

Just find the latest Vbox-version in this directory
https://dl.rockylinux.org/pub/rocky/10/images/x86_64/

3

I continue this thread with a reply to myself.. I just realized that the rockylinux/10 seems to be missing the Virtualbox Guest additions, because synced_folder do not work. I use now instead bento/rockylinux-10.1 which works as expected

4

rockylinux/9 fails as well. Appears the metadata was not updated to point to newer locations so have to explicitly point to vault currently.

5

I’ve never used a distro supplied Guestadditions. I’ve always downloaded the Guestaddtions directly from Vbox/Oracle. In the guest Mounted the iso to /run/media/user/Virt…Box/, Then visited the directory as root and run the command:

# sh ./VirtualBoxLinuxAdditions install

The full command is in the Vbox documentation. Since I’m not in the vm now I can’t call it up. If the guest is windows it is much simpler.

6

It’s also easy to install the guest additions via dnf.

% dnf install centos-release-kmods
% dnf install kmod-vbox-guest-additions
% systemctl reboot

We are considering on having the guest additions available by default in 9.8 and 10.2.

–

As for the links being updated, we haven’t had a moment to get them fixed due to $dayJob and $life. They will be updated soon.

7

So are the installed modules signed and supplied with Cert that the user can enroll with mokutil thus allowing secure boot to be enabled on the RL guest?

8

https://sigs.centos.org/kmods/secure_boot/ says “no”.

9

@jbkt23 Your suggestion is way better than struggling with mounting guest additions. Much easier when bootstrapping. One thing that’s needed for surviving kernel upgrades, is to add epel-release and dkms that’s found in epel. VBoxService gives the error “VBoxDRMClient: Error: unable to find DRM device” if dkms is missing.

10

Your attribution should go to @label who provided the distro method. Though that is simpler and pulls in the dependencies I often install distro’s in vm’s that are not RL and thus building modules from the Guestadditions iso is necessary and allows me to review the build output.

11

Installing the virtualbox guest additions after the box has booted in vagrant has no effect because the flow in vagrant goes boot => check for virtualbox guest additions => run provisioning so even if you install the virtualbox guest additions manually after boot you still won’t be able to use most virtualbox features as they check only once at boot