title: Vagrant up fails to start network interface on cloud images
body: <p>Vagrant fails to bring up ubuntu/vivid32.
  During start up vagrant tries to connect several times and eventually times out.
  If I connect to the box via VirtualBox manager ifconfig shows that eth0 is up but no IP is assigned to it.
  I then do </p>
  
  <pre><code>sudo ifdown eth0 &amp;&amp; sudo ifup eth0 
  </code></pre>
  
  <p>After that, ifconfig shows that eth0 has an IP address.
  I can then connect from vagrant with <em>vagrant ssh</em>
  If I power off and power on the guest with VirtualBox manager, the guest comes up ok (with IP address) and vagrant that, ifconfig shows that eth0 has an IP address.
  I can then connect from vagrant with <em>vagrant ssh</em>.</p>
  
  <p>If I power off and power on the guest with VirtualBox manager, the guest comes up ok (with IP address) and vagrant can connect via <em>vagrant ssh</em>.</p>
  
  <p>If I power off via vagrant (<em>vagrant halt</em>) and power on (<em>vagrant up</em>), I get the same problem (timeout on vagrant side and no IP address) and cannot connect to the guest via <em>vagrant ssh</em>.</p>
  
  <p>While vagrant tries to connect, the guest shows: </p>
  
  <pre><code>cloud-init-nonet[4.54]: waiting 10 seconds for network device
  cloud-init-nonet[14.57]: waiting 120 seconds for network device
  cloud-init-nonet[134.57]: gave up waiting for a network device
  </code></pre>
  
  <p>I tried several proposed solutions on the guest side like <a href="https://dmsimard.com/2014/05/02/no-network-on-ubuntu-14-04-cloud-image-with-cloud-init/">this</a>.</p>
  
  <p>Whatever I tried didn't help on the vagrant side.</p>
  
  <p>After initial fix to the IP address in the guest, VirtualBox manager can bring the box up and now several times without problem.
  But if I power off via vagrant (<em>vagrant halt</em>) and power on (<em>vagrant up</em>), I get the same timeout problem and cannot connect to the guest via vagrant ssh.
  I suspect that "vagrant up" clears the network interface and sets it up again and in this process causes the problem to reappear.</p>
  
  <p>(this also happens with guest: ubuntu/trusty32)</p>
  
  <pre><code>f:\Programs\HashiCorp\Vagrant\bin&gt;vagrant up
  Bringing machine 'vivid32' up with 'virtualbox' provider...
  ==&gt; vivid32: Checking if box 'ubuntu/vivid32' is up to date...
  ==&gt; vivid32: Clearing any previously set forwarded ports...
  ==&gt; vivid32: Clearing any previously set network interfaces...
  ==&gt; vivid32: Preparing network interfaces based on configuration...
      vivid32: Adapter 1: nat
  ==&gt; vivid32: Forwarding ports...
      vivid32: 22 =&gt; 2222 (adapter 1)
  ==&gt; vivid32: Booting VM...
  ==&gt; vivid32: Waiting for machine to boot. This may take a few minutes...
      vivid32: SSH address: 127.0.0.1:2222
      vivid32: SSH username: vagrant
      vivid32: SSH auth method: private key
      vivid32: Warning: Connection timeout. Retrying...
      vivid32: Warning: Connection timeout. Retrying...
  ...
      vivid32: Warning: Connection timeout. Retrying...
  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.
  </code></pre>
  
  <ul>
  <li>Vagrant 1.7.4</li>
  <li>VirtualBox - VirtualBox-5.0.0-101573</li>
  <li>Host - Windows Vista </li>
  <li>Guest ubuntu/vivid32 </li>
  </ul>