title: Laravel Homestead won't start, always enters 'guru meditation' status
body: <p>I am trying to run <a href="http://laravel.com/docs/4.2/homestead" rel="noreferrer">Laravel Homestead</a> box on DigitalOcean's Ubuntu 14.04 LEMP droplet. I'm following these two tutorials:</p>
  
  <ul>
  <li><a href="https://www.digitalocean.com/community/tutorials/how-to-install-vagrant-on-a-vps-running-ubuntu-12-04" rel="noreferrer">How to install Vagrant on a VPS Running Ubuntu 12.04</a></li>
  <li><a href="http://laravel.com/docs/4.2/homestead" rel="noreferrer">Laravel Homestead</a></li>
  </ul>
  
  <p>But I can't seem to start up the box after the installation. I keep getting this error message:</p>
  
  <pre><code>Bringing machine 'default' up with 'virtualbox' provider...
  ==&gt; default: Importing base box 'laravel/homestead'...
  ==&gt; default: Matching MAC address for NAT networking...
  ==&gt; default: Checking if box 'laravel/homestead' is up to date...
  ==&gt; default: Setting the name of the VM: homestead
  ==&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: 80 =&gt; 22280 (adapter 1)
      default: 443 =&gt; 22443 (adapter 1)
      default: 3306 =&gt; 23306 (adapter 1)
      default: 5432 =&gt; 25432 (adapter 1)
      default: 22 =&gt; 2222 (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:2222
      default: SSH username: vagrant
      default: SSH auth method: private key
  The guest machine entered an invalid state while waiting for it
  to boot. Valid states are 'starting, running'. The machine is in the
  'gurumeditation' state. Please verify everything is configured
  properly and try again.
  
  If the provider you're using has a GUI that comes with it,
  it is often helpful to open that and watch the machine, since the
  GUI often has more helpful error messages than Vagrant can retrieve.
  For example, if you're using VirtualBox, run `vagrant up` while the
  VirtualBox GUI is open.
  </code></pre>
  
  <p>Here is my VirtualBox's error log:</p>
  
  <ul>
  <li><a href="http://www.datafilehost.com/get.php?file=4c47075c" rel="noreferrer">VirtualBox log</a></li>
  </ul>
  
  <hr>