vagrant/templates/errors.yml

:box_already_exists: "This box appears to already exist! Please call `vagrant box remove <%= box_name %>`
    and then try to add it again."
:box_remove_doesnt_exist: "The box you're attempting to remove does not exist!"
:box_specified_doesnt_exist: "Specified box `<%= box_name %>` does not exist!

    The box must be added through the `vagrant box add` command. Please view
    the documentation associated with the command for more information."
:box_not_specified: "No base box was specified! A base box is required as a staring point
    for every vagrant virtual machine. Please specify one in your Vagrantfile
    using `config.vm.box`"
:command_box_invalid: "Please specify a valid action to take on the boxes, either
    `add` or `remove`. Examples:

    vagrant box add name uri
    vagrant box remove name
    vagrant box list"
:environment_not_created: "The task you're trying to run requires that the vagrant environment
    already be created, but unfortunately this vagrant still appears to
    have no box! You can setup the environment by setting up your
    <%= Vagrant::Env::ROOTFILE_NAME %> and running `vagrant up`"
:rootfile_already_exists: "It looks like this directory is already setup for vagrant! (A <%= Vagrant::Env::ROOTFILE_NAME %>
    already exists.)"
:rootfile_not_found: "A `<%= Vagrant::Env::ROOTFILE_NAME %>` was not found! This file is required for vagrant to run
    since it describes the expected environment that vagrant is supposed
    to manage. Please create a `<%= Vagrant::Env::ROOTFILE_NAME %>` and place it in your project
    root."
:virtualbox_invalid_version: "Vagrant has detected that you have VirtualBox version <%= version %> installed!
    Vagrant requires that you use at least VirtualBox version 3.1. Please install
    a more recent version of VirtualBox to continue."
:virtualbox_not_detected: "Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
    If VirtualBox is installed, you may need to tweak the paths to the `VBoxManage`
    application which ships with VirtualBox and the path to the global XML configuration
    which VirtualBox typically stores somewhere in your home directory.

    The following shows how to configure VirtualBox. This can be done in the
    Vagrantfile. Note that 90% of the time, you shouldn't need to do this if VirtualBox
    is installed. Please use the various Vagrant support lines to request more information
    if you can't get this working.

    VirtualBox::Command.vboxmanage = \"/path/to/my/VBoxManage\"
    VirtualBox::Global.vboxconfig = \"~/path/to/VirtualBox.xml\""
:virtualbox_xml_not_detected: "Vagrant couldn't find your global VirtualBox.xml file!

    If you just recently installed VirtualBox, make sure you've launched
    it at least once, since the initial launch will typically create this
    file.

    Otherwise, you may need to set the path to the VirtualBox.xml file
    manually. Note that 90% of people should never have to do this, so
    don't be afraid to use the various Vagrant support lines to ask for
    help. To set the path manually:

    VirtualBox::Global.vboxconfig = \"/path/to/VirtualBox.xml\""
:vm_failed_to_boot: "Failed to connect to VM! Failed to boot?"
:vm_power_off_to_move_hd: "The virtual machine must be powered off to move its disk."
:vm_power_off_to_package: "The vagrant virtual environment you are trying to package must be powered off."
:vm_ssh_auth_failed: "SSH authentication failed! While this could be due to a variety of reasons,
    the two most common are: private key path is incorrect or you're using a box
    which was built for Vagrant 0.1.x.

    Vagrant 0.2.x dropped support for password-based authentication. If you're
    tring to `vagrant up` a box which does not support Vagrant's private/public
    keypair, then this error will be raised. To resolve this, read the guide
    on converting base boxes from password-based to keypairs here:

    http://vagrantup.com/docs/converting_password_to_key_ssh.html

    If the box was built for 0.2.x and contains a custom public key, perhaps
    the path to the private key is incorrect. Check your `config.ssh.private_key_path`."