title: Vagrant boots the wrong VirtualBox
body: <p>Picture the following scenario:</p>
  
  <ul>
  <li>Freshly installed, untampered VirtualBox installation</li>
  <li>Freshly installed Vagrant 1.0.6 through gem</li>
  </ul>
  
  <p>And now I try this:</p>
  
  <ul>
  <li><code>vagrant box add box_one [url to box one]</code></li>
  <li><code>vagrant init box_one</code></li>
  <li><code>vagrant up</code></li>
  </ul>
  
  <p>So far, so good. <code>box_one</code> works nicely. It shows up in the VirtualBox Manager, all the port forwardings are set correctly, I can ssh into it, the web server runs - everything is peachy.</p>
  
  <ul>
  <li><code>vagrant halt</code></li>
  <li><code>rm Vagrantfile</code></li>
  </ul>
  
  <p>As far as I understand, this should enable me to do this:</p>
  
  <ul>
  <li><code>vagrant box add box_two [url to box two]</code></li>
  <li><code>vagrant init box_two</code></li>
  <li><code>vagrant up</code></li>
  </ul>
  
  <p>and use <code>box_two</code>. But instead, it clearly uses the configuration of <code>box_two</code> - different ports are forwarded - but it boots the virtual machine of <code>box_one</code>. And in the VirtualBox Manager it shows two machines with different ids - but both are the virtual machines of <code>box_one</code>.</p>
  
  <p>It seems to work for my coworkers, so something on my machine must be triggering that bug. (Or I do something weird, who knows.) </p>
  
  <p>Does anyone have ideas what it could be?</p>