25oct2017_vagrant_not_launching.rb

eva@eva-CR70-2M-CX70-2OC-CX70-2OD:~$ cd vagrant/rails-dev-box
eva@eva-CR70-2M-CX70-2OC-CX70-2OD:~/vagrant/rails-dev-box$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/yakkety64' is up to date...
==> default: A newer version of the box 'ubuntu/yakkety64' is available! You currently
==> default: have version '20170217.0.0'. The latest is version '20170330.0.0'. Run
==> default: `vagrant box update` to update.
==> 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: 3000 (guest) => 3000 (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: ubuntu
    default: SSH auth method: password
^[[B


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,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
eva@eva-CR70-2M-CX70-2OC-CX70-2OD:~/vagrant/rails-dev-box$ 
eva@eva-CR70-2M-CX70-2OC-CX70-2OD:~/vagrant/rails-dev-box$ 
eva@eva-CR70-2M-CX70-2OC-CX70-2OD:~/vagrant/rails-dev-box$ 
eva@eva-CR70-2M-CX70-2OC-CX70-2OD:~/vagrant/rails-dev-box$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/yakkety64' is up to date...
==> default: A newer version of the box 'ubuntu/yakkety64' is available! You currently
==> default: have version '20170217.0.0'. The latest is version '20170330.0.0'. Run
==> default: `vagrant box update` to update.
==> default: VirtualBox VM is already running.
eva@eva-CR70-2M-CX70-2OC-CX70-2OD:~/vagrant/rails-dev-box$ vagrant ssh
ssh_exchange_identification: read: Connection reset by peer
eva@eva-CR70-2M-CX70-2OC-CX70-2OD:~/vagrant/rails-dev-box$ 


Вылечилось просто запуском 
Vagrant provision