Did you install openSSH and ensure that it is set to startup when the system starts up?
On Wednesday, June 24, 2015 at 11:54:47 PM UTC-5, Lito Kusnadi wrote: > > Hi, > > I am trying to build a custom box: centos 6.6. I have to use my own build > (cannot download from atlas repo). > > I am trying to do the basic here (in fast mode): > > Install Centos 6.6 minimal on Virtual Box from the ISO cd file > Install couple RPMS e.g. git and apache > Create user vagrant and make it part of "wheel" group > Visudo wheel group so that it requires no password when doing SUDO to be > super user > Disable the requiretty in visudo entry > Create .ssh folder in vagrant home and download the vagrant public key > from https://github.com/mitchellh/vagrant/tree/master/keys > Disable DNS lookup and make sure it looks at %h/.ssh/authorized_keys for > sshd_config > chmod 0700 /home/vagrant/.ssh > chmod 0600 /home/vagrant/.ssh/authorized_keys > Package the box: vagrant package --base test-centos66 > Add the box: vagrant box add test-centos66 package.box > Create a project dir, vagrant init test-centos66 and vagrant up > > For some reason, I am having issue during boot at SSH login: > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection timeout. Retrying... > default: Warning: Connection timeout. Retrying... > ... > default: Warning: Connection timeout. Retrying... > default: Warning: Connection timeout. Retrying... > Timed out while waiting for the machine to boot. This means that > Vagrant was unable to communicate with the guest machine within > > I can telnet to port 2222, something is listening there, but can't get SSH > from it (usually it shows an SSH string when you telnet to the port) > > I cannot ssh manually to port 2222 or 22. > > I checked no firewall rule is running on the base box. > > The box is running, I can login via console of Virtual Box. But I just > cannot login via SSH and the vagrant up process has issue as shown above. > > I turned off the master box where the base came from. So I only have 1 > vbox running. > > Host is windows 7, vagrant is 1.7.2, virtual box 4.3.28 r 100309 > > I was wondering if the problem is with the public key of the SSH or the > route of port forward from 2222 to 22? > > Any hints? Many thanks. > > > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6387e386-bcd7-4887-88f5-7b4e8c46c3f9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
