Vagrant 1.8.5 & Virtual Box 5.1.2 Upgrade Troubleshooting

Vagrant 1.8.5 & Virtual Box 5.1.2 Upgrade Troubleshooting.md

Error: ssh-cleanup

(Usually occurs when running Vagrant Up (Evolution ​v1.3.16​) = Vagrant 1.6.5 Virtual Box 4.3)

There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The 'ssh-cleanup' provisioner could not be found.

• Upgrade to Vagrant 1.8.5+ & Virtual Box 5.1.2+

Error: config.vm.boot_timeout

==> local: SSH auth method: private key

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

• Try turning wi-fi off and then on again.
• Try runing vagrant reload
• Try destroying and creating vagrant box. First start server vagrant up then backup local db bundle exec cap local genesis:backup:db or bundle exec cap local evolve:db:backup then these two commands vagrant destory vagrant up. Once new up and running add sql.gz back through Sequal Pro or any other tool using for DB Manamgement.

Error: change_host_name

(Usually occurs when running Vagrant Up (Genesis WordPress ~0.2.64) = Vagrant 1.8.5 ( Virtual Box 4.3 || 5.1.2 ) )

==> local: Setting hostname...

Vagrant attempted to execute the capability 'change_host_name'
on the detect guest OS 'linux', 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.

• Run sudo subl /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/guests/ubuntu/guest.rb
• Replace file with - https://raw.githubusercontent.com/carlosefr/vagrant/1c631c18d1a654405f6954459a42ac19a1a2f096/plugins/guests/ubuntu/guest.rb

Also required this:

grtjn/mlvagrant#56

hash -d vagrant