Connection timeout running "vagrant up" with custom box on Windows

[Rhys Gareth]

I've seen this from two separate Windows users, neither can "vagrant up" a box which I am having no problems with in OS X:

INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "showvminfo", "f6a144a9-5a65-4ef8-a10d-fcadcae93e79", "--machinereadable"]

INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "showvminfo", "f6a144a9-5a65-4ef8-a10d-fcadcae93e79", "--machinereadable"]

INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "showvminfo", "f6a144a9-5a65-4ef8-a10d-fcadcae93e79", "--machinereadable"]

INFO ssh: Attempting SSH connnection...

INFO ssh: Attempting to connect to SSH...

INFO ssh:   - Host: 127.0.0.1

INFO ssh:   - Port: 2222

INFO ssh:   - Username: vagrant

INFO ssh:   - Key Path: ["C:/Users/User/.vagrant.d/insecure_private_key"]

 INFO ssh: SSH not up: #<Vagrant::Errors::SSHConnectionTimeout: Vagrant timed out while attempting to connect via SSH. This usually

means that the VM booted, but there are issues with the SSH configuration

or network connectivity issues. Please try to `vagrant reload` or

`vagrant up` again.>

...

 INFO interface: 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. This can

mean a number of things.

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.

They can run the Vagrant "Getting Started" base box no problems, but they can't vagrant up our VM for the project.

We are using the custom opscode_ubuntu-12.04_chef-11.4.0.box because of a need for chef support. Is this likely to be a network configuration issue (seems unlikely as it's working fine on other host OSes) or a private key problem? Anyway to fix or troubleshoot this, or are there any known working ubuntu/chef base boxes we could switch to, if that would solve it?

Rhys

[Rhys Gareth]

The count is now 3 out of 3 totally independent Windows developers not being able to provision Vagrant. i.e. this is very unlikely to be a quirk of their Windows setups that all three coincidentally have.

I also built my own base box completely from scratch using Packer and http://releases.ubuntu.com/12.04/ubuntu-12.04.4-server-i386.iso, but still it doesn't change the issue.

This is the error message they see when normal trace level is enabled:

==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Error: Connection timeout. Retrying...
    default: Error: Authentication failure. Retrying...
    default: Error: Authentication failure. Retrying...
    default: Error: Authentication failure. Retrying...
    default: Error: Authentication failure. Retrying...
    default: Error: Authentication failure. Retrying...
    default: Error: Authentication failure. Retrying...

[Brien Givens]

Did you solve the problem? I'm running into the same problem trying to provision a Mavericks box on Mavericks.

[Konstantin Shilov]

First, try: to see what vagrant private key in you machine config

    $ vagrant ssh-config

Example:

    $ vagrant ssh-config

    Host default

      HostName 127.0.0.1

      User vagrant

      Port 2222

      UserKnownHostsFile /dev/null

      StrictHostKeyChecking no

      PasswordAuthentication no

      IdentityFile C:/Users/konst/.vagrant.d/insecure_private_key

      IdentitiesOnly yes

      LogLevel FATAL

[http://docs.vagrantup.com/v2/cli/ssh_config.html][1]

Second, do:

Change content of file insecure_private_key with content of yorn own system private key

суббота, 22 марта 2014 г., 19:24:11 UTC+4 пользователь Rhys Gareth написал:

[Konstantin Shilov]

**First, try:** to see what *vagrant private key* in you machine config

    $ vagrant ssh-config

Example:

    $ vagrant ssh-config

    Host default

      HostName 127.0.0.1

      User vagrant

      Port 2222

      UserKnownHostsFile /dev/null

      StrictHostKeyChecking no

      PasswordAuthentication no

      IdentityFile C:/Users/konst/.vagrant.d/insecure_private_key

      IdentitiesOnly yes

      LogLevel FATAL

[http://docs.vagrantup.com/v2/cli/ssh_config.html][1]

**Second, do:**

Change content of file *insecure_private_key* with content of yorn own system *private key*

  [1]: http://docs.vagrantup.com/v2/cli/ssh_config.html

среда, 12 марта 2014 г., 23:21:54 UTC+4 пользователь Rhys Gareth написал:

[Alex Demidov]

I have exactly the same problem - 3 different developers on Windows and two different Vagrant configurations (one uses opscode_ubuntu-12.04_provisionerless base box and another opscode-debian-6.0.8). All fail with 'Connection Timeout. Retrying...'.

[Alvaro Miranda Aguilera]

have you tried testing, with 1.5.2 ? to discard vagrant 1.6

--
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 vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alex Demidov]

I had first reports from developers on April 2, before 1.6 was released. 

I'm currently trying to gather some information from developers and test different boxes and so far I have found that one of developers with Windows 8 pro is unable to run any 64-bit OS even with simplest configuration like 'vagrant init hashicorp/precise64 && vagrant up' but she was able to run precise32. I asked her to check if she has virtualization options enabled in BIOS and Hyper-V disabled and she confirms that everything is OK.

[Alvaro Miranda Aguilera]

On Wed, May 14, 2014 at 10:28 PM, Alex Demidov <alexey...@gmail.com> wrote:

V disabled and she confirms that everything is OK.

can she boot/install a 64 bit without vagrant?

other thing I have read is, when the box get created, in some cases, the vm is created as 64 bitsbut the os installed is 32 bits and fail, not vin your case, but worth to check the vm created after import the template is a 64 bit machine with 64 bit os

once its been imported, can be booted manually without vagrant?

what error shows in the gui?

[Alex Demidov]

Finally got access to developer's PC and when I tried to start 64-bit box from VirtualBox directly it told me that PC doesn't have hardware virtualization support enabled, as I suspected.

[Alvaro Miranda Aguilera]

If it's a core2duo or anything new, is just enable it on the bios..

On Sun, Jun 1, 2014 at 6:06 AM, Alex Demidov <alexey...@gmail.com> wrote:

Finally got access to developer's PC and when I tried to start 64-bit box from VirtualBox directly it told me that PC doesn't have hardware virtualization support enabled, as I suspected.

a

[nagarjuna yelisetty]

Same Problem for me
authentication Problem when Vagrant up