Vagrant: Vagrant up forces shutdown of VM

Created on 25 Apr 2017  ·  44Comments  ·  Source: hashicorp/vagrant

Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!

Vagrant version

Vagrant 1.9.4

Host operating system

Windows 7

Guest operating system

bento/centos-7.3

Vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.box = "bento/centos-7.3"
end

Debug output

https://gist.github.com/bbkane/8a207e5fd0a33e5ad9caca0e3ec3c230

Expected behavior

I should have gotten a box

Actual behavior

I got the error messages linked to above

Steps to reproduce

  1. Install Virtualbox from download.virtualbox.org/virtualbox/5.1.20/VirtualBox-5.1.20-114628-Win.exe
  2. Install Vagrant from https://releases.hashicorp.com/vagrant/1.9.4/vagrant_1.9.4.msi
  3. vagrant up

Notes

  • I can use Virtualbox to install an ISO manually as well as use the resulting machine
  • I just downloaded both tools today.
  • I tried messing with config.vm.boot_timeout but that didn't help
  • I disabled my antivirus (Avast) but that didn't seem to make a difference

Truncated Error

For Github searchability

vagrant.exe : C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in `readpartial': An established connection was aborted by the software in your host machine. 
(Errno::ECONNABORTED)
At line:1 char:1
+ & vagrant up 2>&1 >> log.txt
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (C:/HashiCorp/Va...::ECONNABORTED):String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError

References

Are there any other GitHub issues (open or closed) that should be linked here?
For example:

  • GH-7832 look kind of similar (read_nonblock instead of readpartial and vagrant share instead of vagrant up)
  • ...
bug communicatossh
Source
picture bbkane
👍13

Most helpful comment

Update:
Please upgrade vagrant to 1.9.5 as it's released. The version contains fix for this issue.

Following is no longer needed:
Those who want to fix it now in your computer without waiting for 1.9.5 can replace 3 files changed in https://github.com/mitchellh/vagrant/issues/8526 in vagrant installation directory.

For example in windows, those files are located in

  • C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/templates/locales/en.yml
  • C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/errors.rb
  • C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb

replace them with new en.yml, errors.rb and communicator.rb

Then you are good to go. It worked on my Windows 10 machine. One gotcha is in Windows, you have to change folder permission of the directory to edit or create new files.

picture joelhandwell on 27 Apr 2017
👍80 🎉29 ❤23 😄2

All 44 comments

Same here on Vagrant 1.9.4, Windows 10 Home x64 and VirtualBox 5.1.20 with box ubuntu/xenial64 (v20170424.0.0).

famod picture famod on 25 Apr 2017
👍11

I had the same error here (Vagrant 1.9.4, Windows 7 x64, VB 5.1.20 with box ubuntu/xenial64). It looks like an exception Errno::ECONNABORTED is raised if the guest is booting when vagrant tries to connect through ssh.

As a workaround, I added Errno::ECONNABORTED in the array exceptions at line 356 of the file communicators/ssh/communicator.rb as well as a corresponding rescue at line 407.

clamb picture clamb on 25 Apr 2017

@clamb Did that work very well?

bbkane picture bbkane on 25 Apr 2017

Same error for me. I've downgraded to 1.9.3. Works OK.

Deaton64 picture Deaton64 on 25 Apr 2017

Same thing for me for both Vagrant 1.9.3 and 1.9.4, Win 7 and VirtualBox 5.1.20

eineving picture eineving on 25 Apr 2017

Is any fix coming? I am stuck and can't launch any VM since tow days 😞

GhaziTriki picture GhaziTriki on 25 Apr 2017

@bbkane I was able to provision my machine a couple of time, but I am unaware of side effects.

clamb picture clamb on 25 Apr 2017

@chrisroberts Thanks for fixing the issue! I noticed you put it on the 1.9.5 milestone. Pardon my ignorance, but how soon will this change be reflected on the Downloads page?

bbkane picture bbkane on 25 Apr 2017
👍8

Update:
Please upgrade vagrant to 1.9.5 as it's released. The version contains fix for this issue.

Following is no longer needed:
Those who want to fix it now in your computer without waiting for 1.9.5 can replace 3 files changed in https://github.com/mitchellh/vagrant/issues/8526 in vagrant installation directory.

For example in windows, those files are located in

  • C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/templates/locales/en.yml
  • C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/errors.rb
  • C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb

replace them with new en.yml, errors.rb and communicator.rb

Then you are good to go. It worked on my Windows 10 machine. One gotcha is in Windows, you have to change folder permission of the directory to edit or create new files.

joelhandwell picture joelhandwell on 27 Apr 2017
👍80 🎉29 ❤23 😄2

@joelhandwell Thank you!!!
Windows 10 x64 Pro + Vagrant 1.9.4 + VirtualBox 5.1.20
Replaced 3 files & it's all good now :)

vainkop picture vainkop on 27 Apr 2017
👍11

Me too, after replacing 3 files everything goes right. Thanks!

belcebus picture belcebus on 28 Apr 2017

The same for me: Windows 10 x64, VirtualBox Version 5.1.22 , Vagrant 1.9.4. Thanks a lot!

mpaskal picture mpaskal on 1 May 2017
😄1

sorry i have windows 8 i can't fix this problem....can you help me?

fofo13 picture fofo13 on 2 May 2017

This is my error

C:\lab>vagrant up
Bringing machine 'moloch' up with 'virtualbox' provider...
==> moloch: Importing base box 'ubuntu/xenial64'...
==> moloch: Matching MAC address for NAT networking...
==> moloch: Checking if box 'ubuntu/xenial64' is up to date...
==> moloch: Setting the name of the VM: lab_moloch_1493758359300_45989
==> moloch: Clearing any previously set network interfaces...
==> moloch: Preparing network interfaces based on configuration...
moloch: Adapter 1: nat
moloch: Adapter 2: hostonly
==> moloch: Forwarding ports...
moloch: 22 (guest) => 2222 (host) (adapter 1)
==> moloch: Running 'pre-boot' VM customizations...
==> moloch: Booting VM...
==> moloch: Waiting for machine to boot. This may take a few minutes...
moloch: SSH address: 127.0.0.1:2222
moloch: SSH username: ubuntu
moloch: SSH auth method: password
moloch: Warning: Connection reset. Retrying...
==> moloch: Forcing shutdown of VM...
==> moloch: Destroying VM and associated drives...
C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/serv
er_version.rb:54:in readpartial': Connessione interrotta dal software del compu ter host. (Errno::ECONNABORTED) from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t ransport/server_version.rb:54:inblock (2 levels) in negotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t
ransport/server_version.rb:52:in loop' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t ransport/server_version.rb:52:inblock in negotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t
ransport/server_version.rb:50:in loop' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t ransport/server_version.rb:50:innegotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t
ransport/server_version.rb:32:in initialize' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t ransport/session.rb:84:innew'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t
ransport/session.rb:84:in initialize' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.r b:233:innew'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.r
b:233:in start' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commu nicators/ssh/communicator.rb:397:inblock (2 levels) in connect'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in bloc k in timeout' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:inbloc
k in catch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catc h' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatc
h'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in tim eout' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commu nicators/ssh/communicator.rb:371:inblock in connect'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/u
til/retryable.rb:17:in retryable' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commu nicators/ssh/communicator.rb:370:inconnect'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commu
nicators/ssh/communicator.rb:68:in block in wait_for_ready' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:inbloc
k in timeout'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in bloc k in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatc
h'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catc h' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:intim
eout'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commu
nicators/ssh/communicator.rb:46:in wait_for_ready' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/a ction/builtin/wait_for_communicator.rb:16:inblock in call'

fofo13 picture fofo13 on 2 May 2017

I have this error with the current version (1.9.4) with vagrant up command.

_C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in `readpartial': An established connection was aborted by the software in your host machine. (Errno::ECONNABORTED)_

ranss picture ranss on 3 May 2017

Same problem (Version 1.9.4)
C:\vagrant-lamp-56>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Setting the name of the VM: vagrant-lamp-56_default_1493903972602_43191
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 80 (guest) => 8888 (host) (adapter 1)
default: 3306 (guest) => 8889 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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: Warning: Connection reset. Retrying...
==> default: Forcing shutdown of VM...
==> default: Destroying VM and associated drives...
C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in readpartial': Uma conexÒo estabelecida foi anulada pelo software no computador host. (Errno::ECONNABORTED) from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:inblock (2 levels) in negotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:52:in loop' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:52:inblock in negotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:50:in loop' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:50:innegotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:32:in initialize' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/session.rb:84:innew'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/session.rb:84:in initialize' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.rb:233:innew'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.rb:233:in start' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:397:inblock (2 levels) in connect'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in block in timeout' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:inblock in catch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in timeout' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:371:inblock in connect'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/util/retryable.rb:17:in retryable' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:370:inconnect'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:68:in block in wait_for_ready' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:inblock in timeout'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in block in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:intimeout'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:46:in wait_for_ready' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/builtin/wait_for_communicator.rb:16:inblock in call'

MarcusGabriel picture MarcusGabriel on 4 May 2017

I am getting the same error -

C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/serv
er_version.rb:54:in readpartial': An established connection was aborted by the software in your host machine. (Errno::ECONNABORTED) from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t ransport/server_version.rb:54:inblock (2 levels) in negotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t
ransport/server_version.rb:52:in loop' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t ransport/server_version.rb:52:inblock in negotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t
ransport/server_version.rb:50:in loop' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t ransport/server_version.rb:50:innegotiate!'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t
ransport/server_version.rb:32:in initialize' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t ransport/session.rb:84:innew'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/t
ransport/session.rb:84:in initialize' from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.r b:233:innew'
from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.r
b:233:in start' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commu nicators/ssh/communicator.rb:397:inblock (2 levels) in connect'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in bloc k in timeout' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:inbloc
k in catch'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catc h' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatc
h'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in tim eout' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commu nicators/ssh/communicator.rb:371:inblock in connect'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/u
til/retryable.rb:17:in retryable' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commu nicators/ssh/communicator.rb:370:inconnect'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commu
nicators/ssh/communicator.rb:68:in block in wait_for_ready' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:inbloc
k in timeout'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in bloc k in catch' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatc
h'
from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catc h' from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:intim
eout'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commu
nicators/ssh/communicator.rb:46:in wait_for_ready' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/a ction/builtin/wait_for_communicator.rb:16:inblock in call'

c:\Tools\rkt\rkt>vagrant version
Installed Version: 1.9.4
Latest Version: 1.9.4

You're running an up-to-date version of Vagrant!

Windows Version 7

knusher picture knusher on 4 May 2017

to fix this kind of problem you could replace 3 files like above:

For example in windows, those files are located in

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/templates/locales/en.yml
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/errors.rb
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb
replace them with new en.yml, errors.rb and communicator.rb

and then try

vagrant halt

vagrant provision \ vagrant destroy

vagrant up

fofo13 picture fofo13 on 4 May 2017
👍1

Thank you. The fix has worked in windows 8.1 pro.

ksunilsurya picture ksunilsurya on 6 May 2017

You can also back to 1.9.3 until 1.9.5 is out. Both solutions worked for me
on w7
Regards.

El sáb., 6 may. 2017 6:58, ksunilsurya notifications@github.com escribió:

Thank you. The fix has worked in windows 8.1 pro.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mitchellh/vagrant/issues/8520#issuecomment-299615943,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQs54ZXIRwm9w2Vd2t6fEH2pqf-PFDQ9ks5r2_3rgaJpZM4NHCZL
.

belcebus picture belcebus on 6 May 2017

@joelhandwell Thank you so much! You really saved my day! I really owe you one!

NaruAna picture NaruAna on 6 May 2017

@NaruAna all the credit should go @chrisroberts who fixed this issue with https://github.com/mitchellh/vagrant/pull/8526 . I'm not the one who spend time and effort for debugging. Thank you @chrisroberts, you saved my day, and all others who arrived this issue. Also if Vagrant is written in golang like terraform and released as binary, this fix was not possible. So this fix was possible with the scripting language called Ruby.

joelhandwell picture joelhandwell on 6 May 2017
🎉2 👍2

@joelhandwell thank you! The 3 file substitution fix resolved my Vagrant issue with Hyperledger Fabric.

szoghybe picture szoghybe on 8 May 2017

Still doesn't work for me.

Setup: Windows 10 + VirtualBox 5.1.22 + Vagrant 1.9.4

Tried:

  1. Downgrading to 1.9.3
  2. Replacing the 3 files
  3. Replacing the entire contents of the vagrant-1.9.4 gem with the content of the master branch

Still getting errors. Any chance of an expedited fix or another workaround? This prevents me from being able to work.

DannyBen picture DannyBen on 9 May 2017

Thanks @joelhandwell ! the 3 files fix the problem.

raulrotundo picture raulrotundo on 9 May 2017

Fixed by uninstalling v1.9.4 and installing v1.9.3.

davidkirk451 picture davidkirk451 on 10 May 2017

Thank's @joelhandwell, your suggestion resolved my problem.

maikenunes picture maikenunes on 10 May 2017

@chrisroberts Thanks! It worked for me on Win10, VM 5.1.18, Vagrant 1.9.4,

elambro picture elambro on 10 May 2017

@joelhandwell Thank you so much! I have hearattack already comming ;)

sqfaru picture sqfaru on 10 May 2017

@joelhandwell Replacing the three files fixed it.
After all that
vagrant halt
vagrant up
and ran ok but had problems with vagrant ssh.
So i would also suggest after replacing the 3 files
vagrant destroy && vagrant up --provision
will fix all the issues. It did for me

slavensaka picture slavensaka on 10 May 2017
👍1

Thank's @joelhandwell <3
I'm using Windows 10 x64 + Vagrant 1.9.4 + VirtualBox 5.1.22 r115126 (Qt5.6.2)

tiagodurante picture tiagodurante on 10 May 2017

@joelhandwell Thank you so much!

joelrojas picture joelrojas on 12 May 2017

@joelhandwell Thank you so much man!

nivekze picture nivekze on 12 May 2017

Thank you! @joelhandwell

blueyi picture blueyi on 13 May 2017

I had same problem of attempting to "vagrant up" with latest version of Vagrant v1.9.4 while attempting vagrant based setup of Mesosphere DC/OS with Windows 10 and VirtualBox. The VM setup kept shutting down at these lines:

default: SSH auth method: private key
default: Warning: Connection reset. Retrying...
==> default: Forcing shutdown of VM...

Tried several times then found this report from "dnsmichi" at https://monitoring-portal.org/index.php?thread/40651-icinga2-vagrant-problem-up-ing-on-windows-10-machine/

Indeed reverting from Vagrant v1.9.4 back to v1.9.3 fixed the problem.

javajon picture javajon on 13 May 2017

do 1.9.5 fix this?

pwnedDesal picture pwnedDesal on 16 May 2017

Yes, it does:

communicators/ssh: Retry on aborted connections [GH-8526, GH-8520]
(https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md)

mwld picture mwld on 16 May 2017

@joelhandwell Thank you!

puneetverma05 picture puneetverma05 on 16 Jun 2017

I'm getting this issue after a fresh install of Windows 10, Virtual Box 5.1.22 and Vagrant 1.9.5. Any recommendations?

cklmercer picture cklmercer on 29 Jun 2017

check @joelhandwell answer. Have the same setup and fixed it.

slavensaka picture slavensaka on 29 Jun 2017

@joelhandwell Yes it did solve the issue. Thanks man!

claide picture claide on 10 Jul 2017

Getting same issue with Win10, Vagrant 1.9.7 and Virtualbox 5.1.24

PapaBearNZ picture PapaBearNZ on 22 Jul 2017

I'm getting the error as well on Vagrant 1.9.7 and VirtualBox 5.0.6 & 5.1.24 (tried upgrading)

johnnyvf24 picture johnnyvf24 on 26 Jul 2017

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

hashibot[bot] picture hashibot[bot] on 31 Mar 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

dorinlazar picture dorinlazar  ·  3Comments
jazzfog picture jazzfog  ·  3Comments
jsirex picture jsirex  ·  3Comments
StefanScherer picture StefanScherer  ·  3Comments
rhencke picture rhencke  ·  3Comments