vagrant-parallels 0.0.1.dev

data/lib/vagrant-parallels/errors.rb

@@ -0,0 +1,23 @@
+require "vagrant"
+
+module VagrantPlugins
+  module Parallels
+    module Errors
+      class VagrantParallelsError < Vagrant::Errors::VagrantError
+        error_namespace("vagrant_parallels.errors")
+      end
+
+      class ParallelsError < VagrantParallelsError
+        error_key(:prlctl_error)
+      end
+
+      class ParallelsErrorNotFoundError < VagrantParallelsError
+        error_key(:not_found_error)
+      end
+
+      class ParallelsErrorKernelModuleNotLoaded < VagrantParallelsError
+        error_key(:kernel_module_not_loaded)
+      end
+    end
+  end
+end

data/lib/vagrant-parallels/plugin.rb

@@ -0,0 +1,79 @@
+require "vagrant"
+
+begin
+  require "vagrant"
+rescue LoadError
+  raise "The Vagrant Parallels plugin must be run within Vagrant."
+end
+
+# This is a sanity check to make sure no one is attempting to install
+# this into an early Vagrant version.
+if Vagrant::VERSION < "1.2.0"
+  raise "The Vagrant Parallels plugin is only compatible with Vagrant 1.2+"
+end
+
+module VagrantPlugins
+  module Parallels
+
+    class Plugin < Vagrant.plugin("2")
+      name "Parallels"
+      description <<-EOF
+      The Parallels provider allows Vagrant to manage and control
+      Parallels-based virtual machines.
+      EOF
+
+      provider(:parallels) do
+        require File.expand_path("../provider", __FILE__)
+
+        setup_logging
+        setup_i18n
+
+        Provider
+      end
+
+      # This initializes the internationalization strings.
+      def self.setup_i18n
+        I18n.load_path << File.expand_path("locales/en.yml", Parallels.source_root)
+        I18n.reload!
+      end
+
+      # This sets up our log level to be whatever VAGRANT_LOG is.
+      def self.setup_logging
+        require "log4r"
+
+        level = nil
+        begin
+          level = Log4r.const_get(ENV["VAGRANT_LOG"].upcase)
+        rescue NameError
+          # This means that the logging constant wasn't found,
+          # which is fine. We just keep `level` as `nil`. But
+          # we tell the user.
+          level = nil
+        end
+
+        # Some constants, such as "true" resolve to booleans, so the
+        # above error checking doesn't catch it. This will check to make
+        # sure that the log level is an integer, as Log4r requires.
+        level = nil if !level.is_a?(Integer)
+
+        # Set the logging level on all "vagrant" namespaced
+        # logs as long as we have a valid level.
+        if level
+          logger = Log4r::Logger.new("vagrant_parallels")
+          logger.outputters = Log4r::Outputter.stderr
+          logger.level = level
+          logger = nil
+        end
+      end
+
+      # config(:parallels, :provider) do
+      #   require File.expand_path("../config", __FILE__)
+      #   Config
+      # end
+    end
+
+    module Driver
+      autoload :PrlCtl, File.expand_path("../driver/prl_ctl", __FILE__)
+    end
+  end
+end

data/lib/vagrant-parallels/provider.rb

@@ -0,0 +1,68 @@
+require "log4r"
+require "vagrant"
+
+module VagrantPlugins
+  module Parallels
+    class Provider < Vagrant.plugin("2", :provider)
+      attr_reader :driver
+
+      def initialize(machine)
+        @logger = Log4r::Logger.new("vagrant::provider::parallels")
+        @machine = machine
+        @driver = Parallels::Driver::PrlCtl.new(machine.id)
+      end
+
+      # @see Vagrant::Plugin::V2::Provider#action
+      def action(name)
+        # Attempt to get the action method from the Action class if it
+        # exists, otherwise return nil to show that we don't support the
+        # given action.
+        action_method = "action_#{name}"
+        return Action.send(action_method) if Action.respond_to?(action_method)
+        nil
+      end
+
+      # Returns the SSH info for accessing the Parallels VM.
+      def ssh_info
+        # If the VM is not created then we cannot possibly SSH into it, so
+        # we return nil.
+        return nil if state.id == :not_created
+
+        # Return ip from running machine, use ip from config if available
+        return {
+          :host => @machine.config.ssh.host || @driver.ip,
+          :port => @driver.ssh_port(@machine.config.ssh.guest_port)
+        }
+      end
+
+      # Return the state of Parallels virtual machine by actually
+      # querying PrlCtl.
+      #
+      # @return [Symbol]
+      def state
+        # Determine the ID of the state here.
+        state_id = nil
+        state_id = :not_created if !@driver.uuid
+        state_id = @driver.read_state if !state_id
+        state_id = :unknown if !state_id
+
+        # Translate into short/long descriptions
+        short = state_id.to_s.gsub("_", " ")
+        long  = I18n.t("vagrant.commands.status.#{state_id}")
+
+        # Return the state
+        Vagrant::MachineState.new(state_id, short, long)
+      end
+
+      # Returns a human-friendly string version of this provider which
+      # includes the machine's ID that this provider represents, if it
+      # has one.
+      #
+      # @return [String]
+      def to_s
+        id = @machine.id ? @machine.id : "new VM"
+        "Parallels (#{id})"
+      end
+    end
+  end
+end

data/lib/vagrant-parallels/version.rb

@@ -0,0 +1,5 @@
+module VagrantPlugins
+  module Parallels
+    VERSION = "0.0.1.dev"
+  end
+end

data/locales/en.yml

@@ -0,0 +1,1137 @@
+en:
+  vagrant_parallels:
+    cfengine_bootstrapping: |-
+      Bootstrapping CFEngine with policy server: %{policy_server}...
+    cfengine_bootstrapping_policy_hub: |-
+      Performing additional bootstrap for policy hubs...
+    cfengine_cant_autodetect_ip: |-
+      Vagrant was unable to automatically detect the IP address of the
+      running machine to use as the policy server address. Please specify
+      the policy server address manually, or verify that the networks are
+      configured properly internally.
+    cfengine_cant_detect: |-
+      Vagrant doesn't support detecting whether CFEngine is installed
+      for the guest OS running in the machine. Vagrant will assume it is
+      installed and attempt to continue.
+    cfengine_detected_ip: |-
+      Detected policy server IP address: %{address}...
+    cfengine_installing: |-
+      Installing CFEngine onto machine...
+    cfengine_installing_files_path: |-
+      Copying the 'files_path' files...
+    cfengine_no_bootstrap: |-
+      CFEngine doesn't require bootstrap. Not bootstrapping.
+    cfengine_single_run: |-
+      CFEngine running in "single run" mode. Will execute one file.
+    cfengine_single_run_execute: |-
+      Executing run file for CFEngine...
+    chef_run_list_empty: |-
+      Warning: Chef solo run list is empty. This may not be what you want.
+
+    cfengine_config:
+      classes_array: |-
+        The 'classes' configuration must be an array.
+      files_path_not_directory: |-
+        The 'files_path' must point to a valid directory.
+      invalid_mode: |-
+        The mode must be 'bootstrap' or 'single_run'
+      policy_server_address: |-
+        The policy server address must be set for bootstrapping.
+      run_file_not_found: |-
+        The 'run_file' specified could not be found.
+
+    general:
+      batch_unexpected_error: |-
+        An unexpected error ocurred when executing the action on the
+        '%{machine}' machine. Please report this as a bug:
+
+        %{message}
+      batch_vagrant_error: |-
+        An error occurred while executing the action on the '%{machine}'
+        machine. Please handle this error then try again:
+
+        %{message}
+      config_upgrade_messages: |-
+        There were warnings and/or errors while loading your Vagrantfile.
+        Your Vagrantfile was written for an earlier version of Vagrant,
+        and while Vagrant does the best it can to remain backwards
+        compatible, there are some cases where things have changed
+        significantly enough to warrant a message. These messages are
+        shown below.
+
+        %{output}
+      moving_home_dir: "Moving old Vagrant home directory to new location: %{directory}"
+      home_dir_migration_failed: |-
+        Both an old and new Vagrant home directory exist. Only the new one will
+        be used. Please merge the old directory into the new directory if you'd
+        like to use the old data as well.
+
+        Old: %{old}
+        New: %{new}
+      in_bundler: |-
+        You appear to be running Vagrant in a Bundler environment. Because
+        Vagrant should be run within installers (outside of Bundler), Vagrant
+        will assume that you're developing plugins and will change its behavior
+        in certain ways to better assist plugin development.
+      not_in_installer: |-
+        You appear to be running Vagrant outside of the official installers.
+        Note that the installers are what ensure that Vagrant has all required
+        dependencies, and Vagrant assumes that these dependencies exist. By
+        running outside of the installer environment, Vagrant may not function
+        properly. To remove this warning, install Vagrant using one of the
+        official packages from vagrantup.com.
+      upgraded_v1_dotfile: |-
+        A Vagrant 1.0.x state file was found for this environment. Vagrant has
+        gone ahead and auto-upgraded this to the latest format. Everything
+        should continue working as normal. Beware, however, that older versions
+        of Vagrant may no longer be used with this environment.
+
+        However, in case anything went wrong, the old dotfile was backed up
+        to the location below. If everything is okay, it is safe to remove
+        this backup.
+
+        Backup: %{backup_path}
+
+#-------------------------------------------------------------------------------
+# Translations for exception classes
+#-------------------------------------------------------------------------------
+    errors:
+      active_machine_with_different_provider: |-
+        An active machine was found with a different provider. Vagrant
+        currently allows each machine to be brought up with only a single
+        provider at a time. A future version will remove this limitation.
+        Until then, please destroy the existing machine to up with a new
+        provider.
+
+        Machine name: %{name}
+        Active provider: %{active_provider}
+        Requested provider: %{requested_provider}
+      ansible_playbook_app_not_found: |-
+        The "ansible-playbook" program could not be found! Please verify
+        that "ansible-playbook" is available on the PATH of your host
+        system, and try again.
+
+        If you haven't installed Ansible yet, please install Ansible
+        on your system. Vagrant can't do this for you in a safe, automated
+        way. Please see ansible.cc for more info.
+      base_vm_not_found: The base VM with the name '%{name}' was not found.
+      batch_multi_error: |-
+        An error occurred while executing multiple actions in parallel.
+        Any errors that occurred are shown below.
+
+        %{message}
+      box_config_changing_box: |-
+        While loading the Vagrantfile, the provider override specified
+        a new box. This box, in turn, specified a different box. This isn't
+        allowed, as it could lead to infinite recursion of Vagrant configuration
+        loading. Please fix this.
+      box_metadata_file_not_found: |-
+        The "metadata.json" file for the box '%{name}' was not found.
+        Boxes require this file in order for Vagrant to determine the
+        provider it was made for. If you made the box, please add a
+        "metadata.json" file to it. If someone else made the box, please
+        notify the box creator that the box is corrupt. Documentation for
+        box file format can be found at the URL below:
+
+        http://docs.vagrantup.com/v2/boxes/format.html
+      box_not_found: Box '%{name}' could not be found.
+      box_provider_doesnt_match: |-
+        The box you attempted to add doesn't match the provider you specified.
+
+        Provider expected: %{expected}
+        Provider of box: %{actual}
+      box_upgrade_required: |-
+        The box '%{name}' is still stored on disk in the Vagrant 1.0.x
+        format. This box must be upgraded in order to work properly with
+        this version of Vagrant.
+      cfengine_bootstrap_failed: |-
+        Failed to bootstrap CFEngine. Please see the output above to
+        see what went wrong and address the issue.
+      cfengine_install_failed: |-
+        After installing CFEngine, Vagrant still can't detect a proper
+        CFEngine installation. Please verify that CFEngine was properly
+        installed, as the installation may have failed.
+      cfengine_not_installed: |-
+        CFEngine appears to not be installed on the guest machine. Vagrant
+        can attempt to install CFEngine for you if you set the "install"
+        setting to "true", but this setting was not set. Please install
+        CFEngine on the guest machine or enable the "install" setting for
+        Vagrant to attempt to install it for you.
+      cli_invalid_options: |-
+        An invalid option was specified. The help for this command
+        is available below.
+
+        %{help}
+      cli_invalid_usage: |-
+        This command was not invoked properly. The help for this command is
+        available below.
+
+        %{help}
+      command_unavailable: |-
+        The executable '%(file)' Vagrant is trying to run was not
+        found in the PATH variable. This is an error. Please verify
+        this software is installed and on the path.
+      command_unavailable_windows: |-
+        The executable '%(file)' Vagrant is trying to run was not
+        found in the %PATH% variable. This is an error. Please verify
+        this software is installed and on the path.
+      config_invalid: |-
+        There are errors in the configuration of this machine. Please fix
+        the following errors and try again:
+
+        %{errors}
+      config_upgrade_errors: |-
+        Because there were errors upgrading your Vagrantfiles, Vagrant
+        can no longer continue. Please fix the errors above and try again.
+      copy_private_key_failed: |-
+        Vagrant failed to copy the default insecure private key into your
+        home directory. This is usually caused by a permissions error.
+        Please make sure the permissions of the source is readable and
+        the destination is writable.
+
+        Source: %{source}
+        Destination: %{destination}
+      destroy_requires_force: |-
+        Destroy doesn't have a TTY to ask for confirmation. Please pass the
+        `--force` flag to force a destroy, otherwise attach a TTY so that
+        the destroy can be confirmed.
+      dotfile_is_directory: |-
+        The local file Vagrant uses to store data ".vagrant" already exists
+        and is a directory! If you are in your home directory, then please run
+        this command in another directory. If you aren't in a home directory,
+        then please rename ".vagrant" to something else, or configure Vagrant
+        to use another filename by modifying `config.vagrant.dotfile_name`.
+      dotfile_upgrade_json_error: |-
+        A Vagrant 1.0.x local state file was found. Vagrant is able to upgrade
+        this to the latest format automatically, however various checks are
+        put in place to verify data isn't incorrectly deleted. In this case,
+        the old state file was not valid JSON. Vagrant 1.0.x would store state
+        as valid JSON, meaning that this file was probably tampered with or
+        manually edited. Vagrant's auto-upgrade process cannot continue in this
+        case.
+
+        In most cases, this can be resolve by simply removing the state file.
+        Note however though that if Vagrant was previously managing virtual
+        machines, they may be left in an "orphan" state. That is, if they are
+        running or exist, they'll have to manually be removed.
+
+        If you're unsure what to do, ask the Vagrant mailing list or contact
+        support.
+
+        State file path: %{state_file}
+      downloader_error: |-
+        An error occurred while downloading the remote file. The error
+        message, if any, is reproduced below. Please fix this error and try
+        again.
+
+        %{message}
+      downloader_interrupted: |-
+        The download was interrupted by an external signal. It did not
+        complete.
+      environment_locked: |-
+        An instance of Vagrant is already running. Only one instance of Vagrant
+        may run at any given time to avoid problems with Parallels Desktop inconsistencies
+        occurring. Please wait for the other instance of Vagrant to end and then
+        try again.
+      forward_port_adapter_not_found: |-
+        The adapter to attach a forwarded port to was not found. Please
+        verify that the given adapter is setup on the machine as a NAT
+        interface.
+
+        Host port: %{host}
+        Guest port: %{guest}
+        Adapter: %{adapter}
+      gem_command_in_bundler: |-
+        You cannot run the `vagrant plugin` command while in a bundler environment.
+        This should generally never happen unless Vagrant is installed outside
+        of the official installers or another gem is wrongly attempting to
+        use Vagrant internals directly. Please properly install Vagrant to
+        fix this. If this error persists, please contact support.
+      guest_capability_invalid: |-
+        The registered guest capability '%{cap}' for the
+        detected guest OS '%{guest}' is invalid. The capability does
+        not implement the proper method. This is a bug with Vagrant or the
+        plugin that implements this capability. Please report a bug.
+      guest_capability_not_found: |-
+        Vagrant attempted to execute the capability '%{cap}'
+        on the detect guest OS '%{guest}', but the guest doesn't
+        support that capability. This capability is required for your
+        configuration of Vagrant. Please either reconfigure Vagrant to
+        avoid this capability or fix the issue by creating the capability.
+      guest_not_detected: |-
+        The guest operating system of the machine could not be detected!
+        Vagrant requires this knowledge to perform specific tasks such
+        as mounting shared folders and configuring networks. Please add
+        the ability to detect this guest operating system to Vagrant
+        by creating a plugin or reporting a bug.
+      home_dir_not_accessible: |-
+        The home directory you specified is not accessible. The home
+        directory that Vagrant uses must be both readable and writable.
+
+        You specified: %{home_path}
+      interrupted: |-
+        Vagrant exited after cleanup due to external interrupt.
+      local_data_dir_not_accessible: |-
+        The directory Vagrant will use to store local environment-specific
+        state is not accessible. The directory specified as the local data
+        directory must be both readable and writable for the user that is
+        running Vagrant.
+
+        Local data directory: %{local_data_path}
+      linux_mount_failed: |-
+        Failed to mount folders in Linux guest. This is usually beacuse
+        the "vboxsf" file system is not available. Please verify that
+        the Parallels Tools are properly installed in the guest and
+        can work properly. The command attempted was:
+
+        %{command}
+      linux_nfs_mount_failed: |-
+        Mounting NFS shared folders failed. This is most often caused by the NFS
+        client software not being installed on the guest machine. Please verify
+        that the NFS client software is properly installed, and consult any resources
+        specific to the linux distro you're using for more information on how to
+        do this.
+      linux_shell_expand_failed: |-
+        Vagrant failed to determine the shell expansion of the guest path
+        for one of your shared folders. This is an extremely rare error case
+        and most likely indicates an unusual configuration of the guest system.
+        Please report a bug with your Vagrantfile.
+      machine_guest_not_ready: |-
+        Guest-specific operations were attempted on a machine that is not
+        ready for guest communication. This should not happen and a bug
+        should be reported.
+      machine_not_found: |-
+        The machine with the name '%{name}' was not found configured for
+        this Vagrant environment.
+      machine_state_invalid: |-
+        An internal error has occurred! The provider of the machine you're
+        trying to work with reported an invalid state. This is a bug with
+        the provider you're using, and not with Vagrant itself or with
+        any configuration you may have done. Please report this bug to
+        the proper location.
+      multi_vm_required: |-
+        A multi-vm environment is required for name specification to this command.
+      multi_vm_target_required: |-
+        This command requires a specific VM name to target in a multi-VM environment.
+      nfs_no_guest_ip: |-
+        No guest IP was given to the Vagrant core NFS helper. This is an
+        internal error that should be reported as a bug.
+      nfs_no_host_ip: |-
+        No host IP was given to the Vagrant core NFS helper. This is
+        an internal error that should be reported as a bug.
+      nfs_no_hostonly_network: |-
+        NFS requires a host-only network with a static IP to be created.
+        Please add a host-only network with a static IP to the machine
+        for NFS to work.
+      no_env: |-
+        A Vagrant environment is required to run this command. Run `vagrant init`
+        to set one up in this directory, or change to a directory with a
+        Vagrantfile and try again.
+      plugin_gem_error: |-
+        An error occurred within RubyGems, the underlying system used to
+        manage Vagrant plugins. The output of the errors are shown below:
+
+        %{output}
+      plugin_install_bad_entry_point: |-
+        Attempting to load the plugin '%{name}' failed, because
+        the entry point doesn't exist. The entry point attempted was
+        '%{entry_point}'. If this is not correct, please manually
+        specify an `--entry-point` when installing the plugin.
+      plugin_install_license_not_found: |-
+        The license file to install could not be found. Please verify
+        the path you gave is correct. The path to the license file given
+        was: '%{path}'
+      plugin_install_not_found: |-
+        The plugin '%{name}' could not be found in local or remote
+        repositories. Please check the name of the plugin and try again.
+      plugin_load_error: |-
+        The plugin "%{plugin}" could not be found. Please make sure that it is
+        properly installed via `vagrant plugin`. Note that plugins made for
+        Vagrant 1.0.x are not compatible with 1.1+ and this error will likely
+        continue to show when you use `plugin install` with a 1.0.x plugin.
+      plugin_load_failed: |-
+        Failed to load the "%{plugin}" plugin. View logs for more details.
+      plugin_load_failed_with_output: |-
+        Failed to load the "%{plugin}" plugin. The output from loading
+        the plugin is shown below. View the logs for complete details.
+
+        stdout: %{stdout}
+
+        stderr: %{stderr}
+      plugin_not_found: |-
+        The plugin '%{name}' could not be found. Please install this plugin
+        prior to attempting to do anything with it.
+      port_collision_resume: |-
+        This VM cannot be resumed, because the forwarded ports would collide
+        with a running program (it could be another virtual machine). Normally,
+        Vagrant will attempt to fix this for you but Parallels Desktop only allows
+        forwarded ports to change if the VM is powered off. Therefore, please
+        reload your VM or stop the other program to continue.
+      provider_not_found: |-
+        The provider '%{provider}' could not be found, but was requested to
+        back the machine '%{machine}'. Please use a provider that exists.
+      scp_permission_denied: |-
+        Failed to upload a file to the guest VM via SCP due to a permissions
+        error. This is normally because the user running Vagrant doesn't have
+        read permission on the file. Please set proper permissions on the file:
+
+        %{path}
+      scp_unavailable: |-
+        SSH server on the guest doesn't support SCP. Please install the necessary
+        software to enable SCP on your guest operating system.
+      shared_folder_create_failed: |-
+        Failed to create the following shared folder on the host system. This is
+        usually because Vagrant does not have sufficient permissions to create
+        the folder.
+
+        %{path}
+
+        Please create the folder manually or specify another path to share.
+      ssh_authentication_failed: |-
+        SSH authentication failed! This is typically caused by the public/private
+        keypair for the SSH user not being properly set on the guest VM. Please
+        verify that the guest VM is setup with the proper public key, and that
+        the private key path for Vagrant is setup properly as well.
+      ssh_bad_exit_status: |-
+        The following SSH command responded with a non-zero exit status.
+        Vagrant assumes that this means the command failed!
+
+        %{command}
+      ssh_connect_eacces: |-
+        SSH is getting permission denied errors when attempting to connect
+        to the IP for SSH. This is usually caused by network rules and not being
+        able to connect to the specified IP. Please try changing the IP on
+        which the guest machine binds to for SSH.
+      ssh_connection_refused: |-
+        SSH connection was refused! This usually happens if the VM failed to
+        boot properly. Some steps to try to fix this: First, try reloading your
+        VM with `vagrant reload`, since a simple restart sometimes fixes things.
+        If that doesn't work, destroy your VM and recreate it with a `vagrant destroy`
+        followed by a `vagrant up`. If that doesn't work, contact a Vagrant
+        maintainer (support channels listed on the website) for more assistance.
+      ssh_connection_reset: |-
+        SSH connection was reset! This usually happens when the machine is
+        taking too long to reboot. First, try reloading your machine with
+        `vagrant reload`, since a simple restart sometimes fixes things.
+        If that doesn't work, destroy your machine and recreate it with
+        a `vagrant destroy` followed by a `1vagrant up`. If that doesn't work,
+        contact support.
+      ssh_connection_timeout: |-
+        Vagrant timed out while attempting to connect via SSH. This usually
+        means that the VM booted, but there are issues with the SSH configuration
+        or network connectivity issues. Please try to `vagrant reload` or
+        `vagrant up` again.
+      ssh_disconnected: |-
+        The SSH connection was unexpectedly closed by the remote end. This
+        usually indicates that SSH within the guest machine was unable to
+        properly start up. Please boot the VM in GUI mode to check whether
+        it is booting properly.
+      ssh_host_down: |-
+        While attempting to connect with SSH, a "host is down" (EHOSTDOWN)
+        error was received. Please verify your SSH settings are correct
+        and try again.
+      ssh_is_putty_link: |-
+        The `ssh` executable found in the PATH is a PuTTY Link SSH client.
+        Vagrant is only compatible with OpenSSH SSH clients. Please install
+        an OpenSSH SSH client or manually SSH in using your existing client
+        using the information below.
+
+        Host: %{host}
+        Port: %{port}
+        Username: %{username}
+        Private key: %{key_path}
+      ssh_key_bad_owner: |-
+        The private key to connect to the machine via SSH must be owned
+        by the user running Vagrant. This is a strict requirement from
+        SSH itself. Please fix the following key to be owned by the user
+        running Vagrant:
+
+        %{key_path}
+      ssh_key_bad_permissions: |-
+        The private key to connect to this box via SSH has invalid permissions
+        set on it. The permissions of the private key should be set to 0600, otherwise SSH will
+        ignore the key. Vagrant tried to do this automatically for you but failed. Please set the
+        permissions on the following file to 0600 and then try running this command again:
+
+        %{key_path}
+      ssh_key_type_not_supported: |-
+        The private key you're attempting to use with this Vagrant box uses
+        an unsupported encryption type. The SSH library Vagrant uses does not support
+        this key type. Please use `ssh-rsa` or `ssh-dss` instead. Note that
+        sometimes keys in your ssh-agent can interfere with this as well,
+        so verify the keys are valid there in addition to standard
+        file paths.
+      ssh_not_ready: |-
+        The provider for this Vagrant-managed machine is reporting that it
+        is not yet ready for SSH. Depending on your provider this can carry
+        different meanings. Make sure your machine is created and running and
+        try again. Additionally, check the output of `vagrant status` to verify
+        that the machine is in the state that you expect. If you continue to
+        get this error message, please view the documentation for the provider
+        you're using.
+      ssh_port_not_detected: |-
+        Vagrant couldn't determine the SSH port for your VM! Vagrant attempts to
+        automatically find a forwarded port that matches your `config.ssh.guest_port`
+        (default: 22) value and uses this for SSH. Alternatively, if `config.ssh.port`
+        is set, it will use this.
+
+        However, in this case Vagrant was unable to find a forwarded port that matches
+        the guest port and `config.ssh.port` is not set!
+
+        Please make sure that you have a forwarded port that goes to the configured
+        guest port value, or specify an explicit SSH port with `config.ssh.port`.
+      ssh_unavailable: "`ssh` binary could not be found. Is an SSH client installed?"
+      ssh_unavailable_windows: |-
+        `ssh` executable not found in any directories in the %PATH% variable. Is an
+        SSH client installed? Try installing Cygwin, MinGW or Git, all of which
+        contain an SSH client. Or use the PuTTY SSH client with the following
+        authentication information shown below:
+
+        Host: %{host}
+        Port: %{port}
+        Username: %{username}
+        Private key: %{key_path}
+      ui_expects_tty: |-
+        Vagrant is attempting to interface with the UI in a way that requires
+        a TTY. Most actions in Vagrant that require a TTY have configuration
+        switches to disable this requirement. Please do that or run Vagrant
+        with TTY.
+      unimplemented_provider_action: |-
+        Vagrant attempted to call the action '%{action}' on the provider
+        '%{provider}', but this provider doesn't support this action. This
+        is probably a bug in either the provider or the plugin calling this
+        action, and should be reported.
+      vagrantfile_exists: |-
+        `Vagrantfile` already exists in this directory. Remove it before
+        running `vagrant init`.
+      vagrantfile_load_error: |-
+        There was an error loading a Vagrantfile. The file being loaded
+        and the error message are shown below. This is usually caused by
+        a syntax error.
+
+        Path: %{path}
+        Message: %{message}
+      vagrantfile_syntax_error: |-
+        There is a syntax error in the following Vagrantfile. The syntax error
+        message is reproduced below for convenience:
+
+        %{file}
+      prlctl_error: |-
+        There was an error while executing `prlctl`, a CLI used by Vagrant
+        for controlling Parallels Desktop. The command and stderr is shown below.
+
+        Command: %{command}
+
+        Stderr: %{stderr}
+      prlctl_not_found_error: |-
+        The "prlctl" command or one of its dependencies could not
+        be found. Please verify Parallels Desktop is properly installed. You can verify
+        everything is okay by running "prlctl --version" and verifying
+        that the Parallels Desktop version is outputted.
+      virtualbox_invalid_version: |-
+        Vagrant has detected that you have a version of Parallels Desktop installed
+        that is not supported. Please install one of the supported versions
+        listed below to use Vagrant:
+
+        %{supported_versions}
+      virtualbox_kernel_module_not_loaded: |-
+        Parallels Desktop is complaining that the kernel module is not loaded. Please
+        run `prlctl --version` or open the Parallels Desktop GUI to see the error
+        message which should contain instructions on how to fix this error.
+      virtualbox_install_incomplete: |-
+        Parallels Desktop is complaining that the installation is incomplete. Please
+        run `prlctl --version` to see the error message which should contain
+        instructions on how to fix this error.
+      virtualbox_no_room_for_high_level_network: |-
+        There is no available slots on the Parallels Desktop VM for the configured
+        high-level network interfaces. "private_network" and "public_network"
+        network configurations consume a single network adapter slot on the
+        Parallels Desktop VM. Parallels Desktop limits the number of slots to 8, and it
+        appears that every slot is in use. Please lower the number of used
+        network adapters.
+      virtualbox_not_detected: |-
+        Vagrant could not detect Parallels Desktop! Make sure Parallels Desktop is properly installed.
+        Vagrant uses the `prlctl` binary that ships with Parallels Desktop, and requires
+        this to be available on the PATH. If Parallels Desktop is installed, please find the
+        `prlctl` binary and add it to the PATH environmental variable.
+      vm_creation_required: |-
+        VM must be created before running this command. Run `vagrant up` first.
+      vm_inaccessible: |-
+        Your VM has become "inaccessible." Unfortunately, this is a critical error
+        with Parallels Desktop that Vagrant can not cleanly recover from. Please open Parallels Desktop
+        and clear out your inaccessible virtual machines or find a way to fix
+        them.
+      vm_name_exists: |-
+        A Parallels Desktop virtual machine with the name '%{name}' already exists.
+        Please use another name or delete the machine with the existing
+        name, and try again.
+      vm_no_match: |-
+        No virtual machines matched the regular expression given.
+      vm_not_found: |-
+        A VM by the name of %{name} was not found.
+      vm_not_running: |-
+        VM must be running to open SSH connection. Run `vagrant up`
+        to start the virtual machine.
+
+#-------------------------------------------------------------------------------
+# Translations for config validation errors
+#-------------------------------------------------------------------------------
+    config:
+      common:
+        bad_field: "The following settings don't exist: %{fields}"
+        error_empty: "`%{field}` must be not be empty."
+      chef:
+        cookbooks_path_empty: "Must specify a cookbooks path for chef solo."
+        cookbooks_path_missing: |-
+          Cookbook path doesn't exist: %{path}
+        server_url_empty: "Chef server URL must be populated."
+        validation_key_path: "Validation key path must be valid path to your chef server validation key."
+      loader:
+        bad_v1_key: |-
+          Unknown configuration section '%{key}'. If this section was part of
+          a Vagrant 1.0.x plugin, note that 1.0.x plugins are incompatible with 1.1+.
+      root:
+        bad_key: |-
+          Unknown configuration section '%{key}'.
+      ssh:
+        private_key_missing: "`private_key_path` file must exist: %{path}"
+      vm:
+        base_mac_invalid: "Base MAC address for eth0/NAT must be set. Contact box maintainer for more information."
+        box_missing: "A box must be specified."
+        box_not_found: "The box '%{name}' could not be found."
+        hostname_invalid_characters: |-
+          The hostname set for the VM should only contain letters, numbers,
+          and hyphens.
+        network_invalid: |-
+          The network type '%{type}' is not valid. Please use
+          'hostonly' or 'bridged'.
+        network_ip_required: |-
+          Host only networks require an IP as an argument.
+        network_ip_invalid: |-
+          The host only network IP '%{ip}' is invalid.
+        network_ip_ends_one: |-
+          The host only network IP '%{ip}' must not end in a 1, as this
+          is reserved for the host machine.
+        nfs_not_supported: |-
+          It appears your machine doesn't support NFS, or there is not an
+          adapter to enable NFS on this machine for Vagrant. Please verify
+          that `nfsd` is installed on your machine, and try again. If you're
+          on Windows, NFS isn't supported. If the problem persists, please
+          contact Vagrant support.
+        nfs_requires_host: |-
+          Using NFS shared folders requires a host to be specified
+          using `config.vagrant.host`.
+        network_ip_required: |-
+          An IP is required for a private network.
+        network_fp_host_not_unique: |-
+          Forwarded port '%{host}' (host port) is declared multiple times
+        network_fp_requires_ports: |-
+          Forwarded port definitions require a "host" and "guest" value
+        network_type_invalid: |-
+          Network type '%{type}' is invalid. Please use a valid network type.
+        provisioner_not_found: |-
+          The '%{name}' provisioner could not be found.
+        shared_folder_guestpath_duplicate: |-
+          A shared folder guest path is used multiple times. Shared
+          folders must all map to a unique guest path: %{path}
+        shared_folder_guestpath_relative: |-
+          The shared folder guest path must be absolute: %{path}
+        shared_folder_hostpath_missing: |-
+          The host path of the shared folder is missing: %{path}
+        shared_folder_nfs_owner_group: |-
+          Shared folder that have NFS enabled do no support owner/group
+          attributes. Host path: %{path}
+
+#-------------------------------------------------------------------------------
+# Translations for commands. e.g. `vagrant x`
+#-------------------------------------------------------------------------------
+    commands:
+      common:
+        vm_already_running: |-
+          Parallels Desktop VM is already running.
+        vm_not_created: "VM not created. Moving on..."
+        vm_not_running: "VM is not currently running. Please bring it up to run this command."
+      box:
+        no_installed_boxes: "There are no installed boxes! Use `vagrant box add` to add some."
+        removing: |-
+          Removing box '%{name}' with provider '%{provider}'...
+      destroy:
+        confirmation: "Are you sure you want to destroy the '%{name}' VM? [y/N] "
+        will_not_destroy: |-
+          The VM '%{name}' will not be destroyed, since the confirmation
+          was declined.
+      init:
+        success: |-
+          A `Vagrantfile` has been placed in this directory. You are now
+          ready to `vagrant up` your first virtual environment! Please read
+          the comments in the Vagrantfile as well as documentation on
+          `vagrantup.com` for more information on using Vagrant.
+      plugin:
+        installed_license: |-
+          The license for '%{name}' was successfully installed!
+        installing_license: |-
+          Installing license for '%{name}'...
+        no_plugins: |-
+          No plugins installed.
+        installed: |-
+          Installed the plugin '%{name} (%{version})'!
+        installing: |-
+          Installing the '%{name}' plugin. This can take a few minutes...
+        uninstalling: |-
+          Uninstalling the '%{name}' plugin...
+      status:
+        aborted: |-
+          The VM is in an aborted state. This means that it was abruptly
+          stopped without properly closing the session. Run `vagrant up`
+          to resume this virtual machine. If any problems persist, you may
+          have to destroy and restart the virtual machine.
+        gurumeditation: |-
+          The VM is in the "guru meditation" state. This is a rare case which means
+          that an internal error in VitualBox caused the VM to fail. This is always
+          the sign of a bug in Parallels Desktop. You can try to bring your VM back online
+          with a `vagrant up`.
+        inaccessible: |-
+          The VM is inaccessible! This is a rare case which means that Parallels Desktop
+          can't find your VM configuration. This usually happens when upgrading
+          Parallels Desktop, moving to a new computer, etc. Please consult Parallels
+          for how to handle this issue.
+        output: |-
+          Current machine states:
+
+          %{states}
+
+          %{message}
+        not_created: |-
+          The environment has not yet been created. Run `vagrant up` to
+          create the environment. If a machine is not created, only the
+          default provider will be shown. So if a provider is not listed,
+          then the machine is not created for that environment.
+        paused: |-
+          The VM is paused. This VM may have been paused via the Parallels Desktop
+          GUI or the prlctl command line interface. To unpause, please
+          use the Parallels Desktop GUI and/or prlctl command line interface so
+          that vagrant would be able to control the VM again.
+        poweroff: |-
+          The VM is powered off. To restart the VM, simply run `vagrant up`
+        running: |-
+          The VM is running. To stop this VM, you can run `vagrant halt` to
+          shut it down forcefully, or you can run `vagrant suspend` to simply
+          suspend the virtual machine. In either case, to restart it again,
+          simply run `vagrant up`.
+        saving: |-
+          The VM is currently saving its state. In a few moments this state
+          should transition to "saved." Please run `vagrant status` again
+          in a few seconds.
+        saved: |-
+          To resume this VM, simply run `vagrant up`.
+        stuck: |-
+          The VM is "stuck!" This is a very rare state which means that
+          Parallels Desktop is unable to recover the current state of the VM.
+          The only known solution to this problem is to restart your
+          machine, sorry.
+        listing: |-
+          This environment represents multiple VMs. The VMs are all listed
+          above with their current state. For more information about a specific
+          VM, run `vagrant status NAME`.
+      up:
+        upping: |-
+          Bringing machine '%{name}' up with '%{provider}' provider...
+      version:
+        output: "Vagrant version %{version}"
+
+#-------------------------------------------------------------------------------
+# Translations for Vagrant middleware acions
+#-------------------------------------------------------------------------------
+    actions:
+      runner:
+        waiting_cleanup: "Waiting for cleanup before exiting..."
+        exit_immediately: "Exiting immediately, without cleanup!"
+      vm:
+        boot:
+          booting: Booting VM...
+          waiting: Waiting for VM to boot. This can take a few minutes.
+          ready: VM booted and ready for use!
+          failed: Failed to connect to VM!
+          failed_to_boot: |-
+            Failed to connect to VM via SSH. Please verify the VM successfully booted
+            by looking at the Parallels Desktop GUI.
+          failed_to_run: |-
+            The VM failed to remain in the "running" state while attempting to boot.
+            This is normally caused by a misconfiguration or host system incompatibilities.
+            Please open the Parallels Desktop GUI and attempt to boot the virtual machine
+            manually to get a more informative error message.
+        bridged_networking:
+          available: |-
+            Available bridged network interfaces:
+          bridging: |-
+            Bridging adapter #%{adapter} to '%{bridge}'
+          enabling: |-
+            Enabling bridged network...
+          preparing: |-
+            Preparing bridged networking...
+          specific_not_found: |-
+            Specific bridge '%{bridge}' not found. You may be asked to specify
+            which network to bridge to.
+        check_box:
+          not_found: |-
+            Box '%{name}' was not found. Fetching box from specified URL for
+            the provider '%{provider}'. Note that if the URL does not have
+            a box for this provider, you should interrupt Vagrant now and add
+            the box yourself. Otherwise Vagrant will attempt to download the
+            full box prior to discovering this error.
+          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`
+          does_not_exist: |-
+            Specified 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.
+        check_guest_tools:
+          not_detected: |-
+            No Parallels Tools were detected on the base box for this VM! Parallels
+            Tools are required for forwarded ports, shared folders, host only
+            networking, and more. If SSH fails on this machine, please install
+            the Parallels Tools and repackage the box to continue.
+
+            This is not an error message; everything may continue to work properly,
+            in which case you may ignore this message.
+          version_mismatch: |-
+            The Parallels Tools on this VM do not match the installed version of
+            Parallels Desktop! In most cases this is fine, but in rare cases it can
+            cause things such as shared folders to not work properly. If you see
+            shared folder errors, please update the Parallels Tools within the
+            virtual machine and reload your VM.
+
+            Parallels Tools Version: %{tools_version}
+            Parallels Desktop Version: %{parallels_version}
+        clear_forward_ports:
+          deleting: Clearing any previously set forwarded ports...
+        clear_network_interfaces:
+          deleting: Clearing any previously set network interfaces...
+        clear_shared_folders:
+          deleting: Cleaning previously set shared folders...
+        customize:
+          failure: |-
+            A customization command failed:
+
+            %{command}
+
+            The following error was experienced:
+
+            %{error}
+
+            Please fix this customization and try again.
+          running: Running any VM customizations...
+        destroy:
+          destroying: Destroying VM and associated drives...
+        destroy_network:
+          destroying: Destroying unused networking interface...
+        disable_networks:
+          disabling: Disabling host only networks...
+        discard_state:
+          discarding: Discarding saved state of VM...
+        export:
+          create_dir: Creating temporary directory for export...
+          exporting: Exporting VM...
+          power_off: "The Vagrant virtual environment you are trying to package must be powered off."
+        forward_ports:
+          auto_empty: |-
+            Vagrant found a port collision for the specified port and virtual machine.
+            While this port was marked to be auto-corrected, the ports in the
+            auto-correction range are all also used.
+
+            VM: %{vm_name}
+            Forwarded port: %{guest_port} => %{host_port}
+          collision_error: |-
+            Vagrant cannot forward the specified ports on this VM, since they
+            would collide with some other application that is already listening
+            on these ports. The forwarded port to %{host_port} is already in use
+            on the host machine.
+
+            To fix this, modify your current projects Vagrantfile to use another
+            port. Example, where '1234' would be replaced by a unique host port:
+
+              config.vm.network :forwarded_port, guest: %{guest_port}, host: 1234
+
+            Sometimes, Vagrant will attempt to auto-correct this for you. In this
+            case, Vagrant was unable to. This is usually because the guest machine
+            is in a state which doesn't allow modifying port forwarding.
+          fixed_collision: |-
+            Fixed port collision for %{guest_port} => %{host_port}. Now on port %{new_port}.
+          forwarding: Forwarding ports...
+          forwarding_entry: |-
+            -- %{guest_port} => %{host_port} (adapter %{adapter})
+          non_nat: |-
+            Parallels Desktop network adapter #%{adapter} not configured as "NAT". Skipping port
+            forwards on this adapter.
+          privileged_ports: |-
+            You are trying to forward to privileged ports (ports <= 1024). Most
+            operating systems restrict this to only privileged process (typically
+            processes running as an administrative user). This is a warning in case
+            the port forwarding doesn't work. If any problems occur, please try a
+            port higher than 1024.
+        halt:
+          force: Forcing shutdown of VM...
+          graceful: Attempting graceful shutdown of VM...
+          waiting: Waiting for VM to shutdown. This can take a few minutes.
+          failed: Failed to gracefully shutdown the VM.
+          done: VM shutdown complete!
+        hostname:
+          setting: "Setting hostname..."
+        import:
+          importing: Importing base box '%{name}'...
+          failure: |-
+            The VM import failed! Try running `prlctl import` on the box file
+            manually for more verbose error output.
+        match_mac:
+          matching: Matching MAC address for NAT networking...
+          no_base_mac: |-
+            No base MAC address was specified. This is required for the NAT networking
+            to work properly (and hence port forwarding, SSH, etc.). Specifying this
+            MAC address is typically up to the box and box maintiner. Please contact
+            the relevant person to solve this issue.
+        network:
+          adapter_collision: |-
+            More than one network have been assigned to the same adapter. Please
+            make sure your networks you've configured in your Vagrantfile do not
+            overlap.
+          configuring: |-
+            Configuring and enabling network interfaces...
+          dhcp_already_attached: |-
+            A host only network interface you're attempting to configure via DHCP
+            already has a conflicting host only adapter with DHCP enabled. The
+            DHCP on this adapter is incompatible with the DHCP settings. Two
+            host only network interfaces are not allowed to overlap, and each
+            host only network interface can have only one DHCP server. Please
+            reconfigure your host only network or remove the virtual machine
+            using the other host only network.
+          no_adapters: |-
+            No available adapters on the virtual machine were found to accomodate
+            for all configured networks. Parallels Desktop virtual machines have 8
+            network interfaces available usually, so please lower the number of
+            networks to below 8.
+          preparing: |-
+            Preparing network interfaces based on configuration...
+        host_only_network:
+          collides: |-
+            The specified host network collides with a non-hostonly network!
+            This will cause your specified IP to be inaccessible. Please change
+            the IP or name of your host only network to not match that of
+            a bridged or non-hostonly network.
+          creating: "Creating new host only network for environment..."
+          enabling: "Enabling host only network..."
+          not_found: |-
+            The specified host network could not be found: '%{name}.'
+            If the name specification is removed, Vagrant will create a new
+            host only network for you. Alternatively, please create the
+            specified network manually.
+          preparing: "Preparing host only network..."
+        nfs:
+          exporting: Exporting NFS shared folders...
+          mounting: Mounting NFS shared folders...
+        persist:
+          dotfile_error: |-
+            The dotfile which Vagrant uses to store the UUID of the project's
+            virtual machine already exists and is not a file! The dotfile is
+            currently configured to be '%{dotfile_path}'
+
+            To change this value, please see `config.vagrant.dotfile_name`
+
+            Are you trying to use Vagrant from your home directory? This is the
+            leading cause of this error message. To resolve this, simply use a
+            different directory. Or, if you really want to run Vagrant from your
+            home directory, modify the `config.vagrant.dotfile_name` configuration
+            key.
+          persisting: "Persisting the VM UUID (%{uuid})..."
+        provision:
+          beginning: "Running provisioner: %{provisioner}..."
+        resume:
+          resuming: Resuming suspended VM...
+          unpausing: |-
+            Unpausing the VM...
+        share_folders:
+          creating: Creating shared folders metadata...
+          mounting: Mounting shared folders...
+          mounting_entry: "-- %{guest_path}"
+          nomount_entry: "-- Automounting disabled: %{host_path}"
+        set_name:
+          setting_name: |-
+            Setting the name of the VM...
+        suspend:
+          suspending: Saving VM state and suspending execution...
+
+      box:
+        unpackage:
+          untar_failure: |-
+            The box failed to unpackage properly. Please verify that the box
+            file you're trying to add is not corrupted and try again. The
+            output from attempting to unpackage (if any):
+
+            %{output}
+          already_exists: |-
+            The box you're attempting to add already exits:
+
+            Name: %{name}
+            Provider: %{provider}
+        add:
+          adding: |-
+            Extracting box...
+          added: |-
+            Successfully added box '%{name}' with provider '%{provider}'!
+        destroy:
+          destroying: "Deleting box '%{name}'..."
+        download:
+          cleaning: "Cleaning up downloaded box..."
+          downloading: "Downloading or copying the box..."
+          interrupted: "Box download was interrupted. Exiting."
+        verify:
+          verifying: "Verifying box..."
+          failed: |-
+            The box file you're attempting to add is invalid. This can be
+            commonly attributed to typos in the path given to the box add
+            command. Another common case of this is invalid packaging of the
+            box itself.
+
+      general:
+        package:
+          packaging: "Packaging additional file: %{file}"
+          compressing: "Compressing package to: %{tar_path}"
+          output_exists: |-
+            The specified file to save the package as already exists. Please
+            remove this file or specify a different file name for outputting.
+          output_is_directory: |-
+            The specified output is a directory. Please specify a path including
+            a filename.
+          requires_directory: |-
+            A directory was not specified to package. This should never happen
+            and is a result of an internal inconsistency.
+          include_file_missing: |-
+            Package include file doesn't exist: %{file}
+
+    downloaders:
+      file:
+        download: "Copying box to temporary location..."
+        file_missing: "The specified path to a file doesn't exist."
+      http:
+        connection_reset: |-
+          The remote server unexpectedly closed the connection. Vagrant was
+          unable to finish downloading the box. Please try again. If this
+          problem persists, please try downloading the box manually outside
+          of Vagrant, then adding the box from the filesystem.
+        connection_timeout: |-
+          Vagrant timed out while attempting to connect to the HTTP host.
+          Please check your internet and proxy settings and try again.
+        download: "Downloading box: %{url}"
+        socket_error: |-
+          An error occurred while trying to download the specified box. This most
+          often happens if there is no internet connection or the address is
+          invalid.
+        status_error: |-
+          Bad status code: %{status}
+
+          Please verify that the box exists and is accessible. Also verify that
+          this computer is properly connected to the internet.
+
+    hosts:
+      bsd:
+        nfs_export: |-
+          Preparing to edit /etc/exports. Administrator privileges will be required...
+        nfs_prune: |-
+          Pruning invalid NFS exports. Administrator privileges will be required...
+      linux:
+        nfs_export: |-
+          Preparing to edit /etc/exports. Administrator privileges will be required...
+        nfs_prune: |-
+          Pruning invalid NFS exports. Administrator privileges will be required...
+      arch:
+        nfs_export:
+          prepare: "Preparing to edit /etc/exports. Administrator privileges will be required..."
+      freebsd:
+        nfs_whitespace: |-
+          FreeBSD hosts do not support sharing directories with whitespace in
+          their path. Please adjust your path accordingly.
+
+    provisioners:
+      chef:
+        chef_not_detected: |-
+          The chef binary (either `chef-solo` or `chef-client`) was not found on
+          the VM and is required for chef provisioning. Please verify that chef
+          is installed and that the binary is available on the PATH.
+        cookbook_folder_not_found_warning:
+          "The cookbook path '%{path}' doesn't exist. Ignoring..."
+        json: "Generating chef JSON and uploading..."
+        client_key_folder: "Creating folder to hold client key..."
+        upload_validation_key: "Uploading chef client validation key..."
+        upload_encrypted_data_bag_secret_key: "Uploading chef encrypted data bag secret key..."
+        running_client: "Running chef-client..."
+        running_client_again: "Running chef-client again (failed to converge)..."
+        running_solo: "Running chef-solo..."
+        running_solo_again: "Running chef-solo again (failed to converge)..."
+        missing_shared_folders: |-
+          Shared folders that Chef requires are missing on the virtual machine.
+          This is usually due to configuration changing after already booting the
+          machine. The fix is to run a `vagrant reload` so that the proper shared
+          folders will be prepared and mounted on the VM.
+        no_convergence: |-
+          Chef never successfully completed! Any errors should be visible in the
+          output above. Please fix your recipes so that they properly complete.
+        not_detected: |-
+          The `%{binary}` binary appears to not be in the PATH of the guest. This
+          could be because the PATH is not properly setup or perhaps chef is not
+          installed on this guest. Chef provisioning can not continue without
+          chef properly installed.
+        server_url_required: |-
+          Chef server provisioning requires that the `config.chef.chef_server_url` be set to the
+          URL of your chef server. Examples include "http://12.12.12.12:4000" and
+          "http://myserver.com:4000" (the port of course can be different, but 4000 is the default)
+        server_validation_key_required: |-
+          Chef server provisioning requires that the `config.chef.validation_key_path` configuration
+          be set to a path on your local machine of the validation key used to register the
+          VM with the chef server.
+        server_validation_key_doesnt_exist: |-
+          The validation key set for `config.chef.validation_key_path` does not exist! This
+          file needs to exist so it can be uploaded to the virtual machine.
+
+      puppet:
+        not_detected: |-
+          The `%{binary}` binary appears to not be in the PATH of the guest. This
+          could be because the PATH is not properly setup or perhaps Puppet is not
+          installed on this guest. Puppet provisioning can not continue without
+          Puppet properly installed.
+        running_puppet: "Running Puppet with %{manifest}..."
+        manifest_missing: |-
+          The configured Puppet manifest is missing. Please specify a path to an
+          existing manifest:
+
+          %{manifest}
+        manifests_path_missing: "The manifests path specified for Puppet does not exist: %{path}"
+        missing_shared_folders: |-
+          Shared folders that Puppet requires are missing on the virtual machine.
+          This is usually due to configuration changing after already booting the
+          machine. The fix is to run a `vagrant reload` so that the proper shared
+          folders will be prepared and mounted on the VM.
+        module_path_missing: "The configured module path doesn't exist: %{path}"
+
+      puppet_server:
+        not_detected: |-
+          The `%{binary}` binary appears to not be in the PATH of the guest. This
+          could be because the PATH is not properly setup or perhaps Puppet is not
+          installed on this guest. Puppet provisioning can not continue without
+          Puppet properly installed.
+        running_puppetd: "Running Puppet agent..."
+
+      shell:
+        args_not_string: "Shell provisioner `args` must be a string."
+        no_path_or_inline: "One of `path` or `inline` must be set."
+        path_and_inline_set: "Only one of `path` or `inline` may be set."
+        path_invalid: "`path` for shell provisioner does not exist on the host system: %{path}"
+        running: "Running: %{script}"
+        upload_path_not_set: "`upload_path` must be set for the shell provisioner."
+
+      ansible:
+        no_playbook: "`playbook` must be set for the Ansible provisioner."
+        playbook_path_invalid: "`playbook` for the Ansible provisioner does not exist on the host system: %{path}"
+        inventory_file_path_invalid: "`inventory_file` for the Ansible provisioner does not exist on the host system: %{path}"
+        extra_vars_not_hash: "`extra_vars` for the Ansible provisioner must be a hash"