vagrant up - ssh-agent refusal/blocking issues

[d t]

Hey,

So I know this is not really a new issue, in fact for the past three plus days I have been going through different forums on the same topic and have tested everything suggested or even hinted at and still nothing.  This is getting really frustrating as what I have been unable to do in nearly 4 days on this Windows 10 laptop - I was able to do on a 2008 Macbook at home in less than 4 minutes.

So before we get into it some particulars:

Machine: Alienware M17XR4 - i7-3840QM CPU (VT-X supported); 32 GB RAM
OS: Windows 10 Pro
Git: v.2.8.1
VirtualBox: v.5.0.18 (With 5.0.18 Extension Pack installed)
Vagrant: v.1.8.1

Note: Windows firewall is off, AV is disabled, Hyper-V is not installed and Virtualization is enabled in BIOS

I have tried with three different base Vagrant Boxes with the same result.

> vagrant init hashicorp/precise64
> set VAGRANT_LOG=debug
> vagrant up

Everything appears to run fine from here - until it gets to the SSH connection.  When I enable GUI in the vagrantfile - the VM window that opens, shows a proper boot and then sits on the login screen, which would tell me that there is nothing wrong with this part of "vagrant up". The issue comes from a refusal or a block during Net-SSH connection.  After capturing the debug output which is attached this is the pattern that i am noticing:

...
...
 INFO ssh: Attempting SSH connection...
 INFO ssh: Attempting to connect to SSH...
 INFO ssh:   - Host: 127.0.0.1
 INFO ssh:   - Port: 2222
 INFO ssh:   - Username: vagrant
 INFO ssh:   - Password? false
 INFO ssh:   - Key Path: ["C:/Users/jaedhan/.vagrant.d/insecure_private_key"]
 INFO subprocess: Starting process: ["C:/Program Files/Oracle/VirtualBox/VBoxManage.exe", "showvminfo", "9d6c4814-6de0-4c62-975f-e30d3db30bb4", "--machinereadable"]
 INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: name="precise64_default_1461862816217_13622"

groups="/"

ostype="Ubuntu (64-bit)"
...
...
...
...
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG ssh: == Net-SSH connection debug-level log START ==
DEBUG ssh: D, [2016-04-28T10:00:23.012890 #7664] DEBUG -- net.ssh.transport.session[2223888]: establishing connection to 127.0.0.1:2222

DEBUG ssh: == Net-SSH connection debug-level log END ==
 INFO ssh: SSH not ready: #<Vagrant::Errors::NetSSHException: 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.

This process repeats until it finally times itself out.  Altering the value for config.vm.boot_timeout only adjusts how long it will repeat before timing out.  As seen this issue has something to do with the ssh-agent, unfortunately I am not sure what it could be and have not been able to find anything online that would point to something to try.  Outside of this I have no issues SSH'ing into any machine on the network through either putty or XShell.

Any information someone might have would be very much appreciated.

Thanks
Dallas

[Alvaro Miranda Aguilera]

hello,

if you ope virtualbox, and try to shutdown and start the vm from there, any errors?

Can you test hashicorp/precise32 box ?

Alvaro.

--
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 vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/98de7100-57e5-4e91-b104-d0bd42187c4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[d t]

hello,

Sorry for not posting this in the original post.  I have already tested shutdowns and starts from VirtualBox without any problems and among the other boxes I have tested precise32 and trusty32 were included.  It does not seem to matter whether I am working with a 32-bit box or a 64-bit box I am getting the same error.  The bios already has 64-bit virtualization enabled.

Thanks for the response.

I am looking into the network config at the moment, however this does not make sense really as virtualbox is showing 127.0.0.1 and proper port forwarding.  I have even tried changing the port from 2222 to port 2230 - and still nothing.  Should I try setting a static IP configuration for eth0 in the VagrantFile to see if there is something going on with the auto-config that is causing a collision anywhere?

Thanks
Dallas