Updated CentOS Vagrant Images Available (v1610.01)

Tuesday, 15, November 2016 Laurențiu Păncescu announcement 14 Comments

Official Vagrant images for CentOS Linux 6.8 and CentOS Linux 7.2.1511 for x86_64 are now available for download, featuring updated packages to 30 October 2016, as well as the following user-visible changes:

Known Issues

  1. The centos/7 image is based on CentOS Linux 7.2.1511, since CentOS Linux 7.3 is not available yet.
  2. The VirtualBox Guest Additions are not preinstalled; if you need them for shared folders, please install the vagrant-vbguest plugin and add the following line to your Vagrantfile:
    config.vm.synced_folder ".", "/vagrant", type: "virtualbox"

    We recommend using NFS instead of VirtualBox shared folders if possible.

  3. Since the Guest Additions are missing, our images are preconfigured to use rsync for synced folders. Windows users can either use SMB for synced folders, or disable the sync directory by adding the line
    config.vm.synced_folder ".", "/vagrant", disabled: true

    to your Vagrantfile.

  4. Please use Vagrant 1.8.6 (version 1.8.5 is unable to create new Linux boxes due to Vagrant bug #7610, while version 1.8.7 is unable to download or update boxes due to Vagrant bug #7969).
  5. Installing open-vm-tools is not enough for enabling shared folders with Vagrant's VMware provider. Please follow the detailed instructions in https://github.com/mvermaes/centos-vmware-tools.


The official images can be downloaded from Hashicorp’s Atlas. We provide images for libvirt-kvm, VirtualBox and VMware.

If you never used our images before:

$ vagrant box add centos/6 # for CentOS Linux 6
$ vagrant box add centos/7 # for CentOS Linux 7

Existing users can upgrade their images:

$ vagrant box update --box centos/6
$ vagrant box update --box centos/7

If you are using CentOS Linux on the host, we recommend installing Vagrant from SCL and using the libvirt images. In general, the Vagrant packages provided by your Linux distribution are preferable, since they usually backport fixes for some upstream bugs. If you are using Vagrant on other operating systems, please use Vagrant 1.8.6 (see Known issues, item 4).

Verifying the integrity of the images

The SHA256 checksums of the images are signed with the CentOS 7 Official Signing Key. First, download and verify the checksum file:

$ curl http://cloud.centos.org/centos/7/vagrant/x86_64/images/sha256sum.txt.asc -o sha256sum.txt.asc
$ gpg --verify sha256sum.txt.asc

If the check passed, you can use the corresponding checksum when downloading the image with Vagrant:

$ vagrant box add --checksum-type sha256 --checksum ce12f84646efab28b007bdf16f3134686a23fa052f809c4600919561274051da --provider libvirt --box-version 1610.01 centos/7

Unfortunately, this is not possible with vagrant box update.


If you encounter any unexpected issues with the Vagrant images, feel free to ask on the centos-devel mailing list, or via IRC, in #centos on Freenode.


Some of the optimisations in this release were inspired by the Vagrant images from Fedora Cloud and Debian Cloud.

We would also like to thank the following people (in alphabetical order):

14 thoughts on "Updated CentOS Vagrant Images Available (v1610.01)"

  1. Tom Dworzanski says:

    You mention in Known Issue #2 the installation of the vagrant-vbguest plugin in order to use shared folders. This is important for synced folders. However, a Vagrantfile will also need the setting:

    config.vm.synced_folder ".", "/vagrant", type: "virtualbox"

    in order for VirtualBox directory sync to work.

    I would suggest you add that to Known Issue #2 now and in future releases of these boxes.

    Thank you.

    1. Laurențiu Păncescu says:

      Thanks, Tom, I updated the release notes.

  2. Terry Wilson says:

    $ vagrant up --provider vmware_fusion


    The box you attempted to add doesn't match the provider you specified.

    Provider expected: vmware_desktop
    Provider of box: vmware_fusion

    1. Laurențiu Păncescu says:

      Our images currently have vmware_fusion hardcoded in the metadata. We plan to switch to vmware_desktop in one of the next releases, since that would allow both VMware Fusion and Workstation users to use the same images. In the mean time, it's probably best to remove the problematic vmware_desktop box and download the working one with 'vagrant box add centos/7 --provider vmware_fusion'.

      1. Lucky says:

        Kudos to you! I hadn't thoguht of that!

  3. Miguel Angel Velazco says:

    I'm working with vagrant and VirtualBox and I couldn't set an static IP addres. I don't know if it is related to the box or vagrant.

    1. Laurențiu Păncescu says:

      I'm afraid I can't help you without any details about your setup or your Vagrantfile (but then again, blog comments are not a good medium for posting configuration files - if you need help, please use the suggestions in the Feedback section of the announcement).

      That being said, I'm using private networking with a static IP address in the VirtualBox default host network, it works very well:

      config.vm.network "private_network", ip:""

      1. Alex says:

        I'm having this same issue when using this box. Private networks with a static IP works fine with other boxes.

        I looked in /var/log/messages and the only error I could find is:

        Dec 13 14:19:40 localhost NetworkManager[11140]: [1481638780.940000] [platform/nm-linux-platform.c:2883] do_change_link(): platform-linux: do-change-link: failure changing link 3: Address family not supported (11)

        Any ideas?

        1. Laurențiu Păncescu says:

          No, I've never seen that before. I'm currently using Vagrant 1.9.0 on OS X 10.11.6, without any Vagrant plugins or the Guest Additions, with VirtualBox 5.0.30. Do you see this every time? Could you try with another version of VirtualBox? Which OS are you using on the host? You might also be able to find something in the VirtualBox log. If you have an IRC client, you can ask for direct assistance in #centos on FreeNode.

          1. Kees says:

            I have the same issue maybe. puzzles me, and make some teammates picking there nose ;-). I can ifup the hostonly adapter OK after boot, but that's to late for the nfs share to setup. Only way to workaround this is to use dhcp instead of fixed IP

  4. talentles says:

    The kernel included in the box has been removed due to security issues and using the vagrant vbguest plugin to add guest additions no longer works without workarounds. We need an uodated box 🙁

    1. Laurențiu Păncescu says:

      I know. I've tried to build several images based on 7.1611 (since yesterday morning), but the builds failed due to some incompatibilities involving XFS and our build system. We're actively working on this.

      In the mean time, you could use https://github.com/lpancescu/cloud-instance-starter-kit as a workaround, if you have Ansible on the host (or perform the same steps manually and eventually repack the box afterwards).

  5. Giovanni says:

    This box doesn't seem to work with private_network and static IPs.

    It seems to be because it doesn't disable predictable device naming ("net.ifnames=0 biosdevname=0").

    1. We've had these boot parameters (to disable the new device naming) since the very beginning - May 2015. Perhaps you're assigning a network address in an unusual range? Try as an IP - the default subnetwork that VirtualBox uses is

Leave a Reply

Your email address will not be published. Required fields are marked *