I am using window X and while running vagrant up–>Getting below error:-
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.
And the running–> vagrant status–> Getting below success message
mongod-m103 running (virtualbox)
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,
==> mongod-m103: Running provisioner: shell…
An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.
If the problem persists, please report a bug to the net-ssh project.
timeout during server version negotiating
how can i resolve this error?