title: Unable to SSH to vagrant Ubuntu 16.04?
body: <p>I create very simple Vagrantfile:</p>
  
  <pre><code># -*- mode: ruby -*-
  # vi: set ft=ruby :
  
  Vagrant.configure(2) do |config|
    config.vm.box = "boxcutter/ubuntu1604"
    config.vm.hostname = "r1"
    config.vm.network "forwarded_port", guest: 3000, host: 3000
  
    config.vm.network "private_network", ip: "192.168.50.10"
  
    config.vm.provider "virtualbox" do |vb|
       vb.memory = "1024"
    end
  
  end
  </code></pre>
  
  <p>The general purpose to up the Ubuntu 16.04 server. And all is good excepting troubles with SSH connection.</p>
  
  <p>My log:</p>
  
  <p><code>vagrant up</code></p>
  
  <pre><code>Bringing machine 'default' up with 'virtualbox' provider...
  ==&gt; default: Checking if box 'boxcutter/ubuntu1604' is up to date...
  ==&gt; default: Fixed port collision for 22 =&gt; 2222. Now on port 2200.
  ==&gt; default: Clearing any previously set network interfaces...
  ==&gt; default: Preparing network interfaces based on configuration...
      default: Adapter 1: nat
      default: Adapter 2: hostonly
  ==&gt; default: Forwarding ports...
      default: 3000 (guest) =&gt; 3000 (host) (adapter 1)
      default: 22 (guest) =&gt; 2200 (host) (adapter 1)
  ==&gt; default: Running 'pre-boot' VM customizations...
  ==&gt; default: Booting VM...
  ==&gt; default: Waiting for machine to boot. This may take a few minutes...
      default: SSH address: 127.0.0.1:2200
      default: SSH username: vagrant
      default: SSH auth method: private key
  
  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 the box appears to be booting properly, you may want to increase
  the timeout ("config.vm.boot_timeout") value.
  </code></pre>
  
  <p>I replace <strong>config.vm.box = "boxcutter/ubuntu1604"</strong>
  with box name <strong>"ubuntu/trusty64"</strong> and it's worked well, but how to fix with 16.04 ?</p>