title: Vagrant Laravel Homestead doesn't boot up [Windows-7]
body: <h2>Context</h2>
  
  <p>I'm using <code>Vagrant 1.6.3</code> and <code>VirtualBox 4.3.14</code> on a <code>Windows 7</code> box.</p>
  
  <ul>
  <li><em>Homestead.yaml</em> except: </li>
  </ul>
  
  <blockquote>
  <pre><code>---
  ip: "192.xxx.xxx.xxx"
  memory: 2048
  cpus: 1
  
  authorize: C:/Users/me/.ssh/id_rsa.pub
  
  keys:
      - C:/Users/me/.ssh/id_rsa
  
  folders:
      - map: D:/MyVagrant/Code
        to: /home/vagrant/Code
  
  sites:
      - map: homestead.app
        to: /home/vagrant/Code/Laravel/public
  
  variables:
      - key: APP_ENV
        value: local
  </code></pre>
  </blockquote>
  
  <hr>
  
  <h2>Issue</h2>
  
  <p>I can't get <code>Laravel Homestead</code> up and running.</p>
  
  <p>Excerpt of the console output:</p>
  
  <blockquote>
  <pre><code>==&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
      default: Warning: Connection timeout. Retrying...
      ... Idem - many times...
      default: Warning: Connection timeout. Retrying...
  </code></pre>
  </blockquote>
  
  <hr>
  
  <h2>Question</h2>
  
  <p>How could it be fixed provided that Laravel Homestead is Windows 7 32-bit ready?</p>
  
  <hr>
  
  <h2>Nota bene</h2>
  
  <p>This post is similar to "<a href="https://stackoverflow.com/questions/24555255/timeout-while-trying-to-vagrant-up">Timeout while trying to vagrant up</a>" but nevertheless it calls for the following observations:</p>
  
  <ul>
  <li>The latter didn't receive enough attention, no satistactory answer so far (as the time of the post)</li>
  <li>This one provides more (relevant) details.</li>
  </ul>
  
  <hr>
  
  <h2>Updtate</h2>
  
  <p>My bad: I didn't provide sufficient details as I pretended: My computer has not a <strong>VT-x</strong> capable cpu!</p>