Open reliztrent opened 8 years ago
Hey @reliztrent, are you running Ubuntu? If so, what release?
@reliztrent nevermind, you have that in your ticket :smile:
Can you try installing a more recent version of VirtualBox? I'm 5.0.14_Ubuntu r105127 locally, and that seems to be working.
I am also running into this issue with CentOS 7, do you want me to open another issue?
CentOS 7 VBox 5.4.14r112924 Vagrant 1.9.1
@dnapier : Have you tried the suggestions mentioned here?
@awoods : I did, same result unfortunately. We're going to use one of the other build methods for now. If that doesn't work out I'll revisit this thread.
Running into what may be an ssh authentication issue on installation when running "vagrant up."
Environment:
Steps:
vagrant up
Result:
$ sudo vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
. . .==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2200
default: SSH username: vagrant
default: 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.
Attempted fixes: