title: Laravel Homestead: "VM not created.. moving on"
body: <p>I did a global install of Laravel homestead, edited my <code>~/.homestead/Homestead.yaml</code>-file and spun up the VM with <code>homestead up</code>. Everything worked fine, but then I needed to add another site. I edited <code>Homestead.yaml</code> to contain the new project, the tried to run <code>homestead provision</code> to apply the changes to the VM. The only thing that outputs is:</p>
  
  <pre><code>==&gt; default: VM not created. Moving on...
  </code></pre>
  
  <p>I interpret that as the VM is not running, but it is. The only thing working here is <code>homestead destroy</code> followed by <code>homestead up</code>, but that (by its nature) detroys the VM's saved state. I though that vagrant commands was applicable to homestead as well, but <code>vagrant suspend &amp;&amp; vagrant up --provision</code> doesn't help.</p>
  
  <p>So.. How do I apply my new config to an already-existing homestead VM?</p>