to_specs': Could not find 'net-ssh' (< 2.8.0, >= 2.6.6) - did find: [net-ssh-2.9.0] (Gem::LoadError) from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/specification.rb:1295:inblock in activate_dependencies'
each' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/specification.rb:1284:inactivate_dependencies'
activate' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems.rb:196:inrescue in try_activate'
try_activate' from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:132:inrescue in require'
require' from /usr/lib64/ruby/gems/1.9.1/gems/vagrant-1.4.3/bin/vagrant:27:in<top (required)>'
load' from /usr/bin/vagrant:8:in<main>'
==> default: Starting container...
==> default: Waiting for machine to boot. This may take a few minutes...
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,
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.