title: I can't start Laravel Homestead on MacOS using VMWare (port collision)
body: <p>I tried to setup a new Laravel project this afternoon and I must have did something to my Homestead/Vagrant configuration that ruined it. I think the command I used was <em>vagrant reload {id}</em>.</p>
  
  <p>Now when I try to start my machine, I get the following error:</p>
  
  <pre><code>Bringing machine 'homestead-7' up with 'vmware_fusion' provider...
  ==&gt; homestead-7: Checking if box 'laravel/homestead' is up to date...
  ==&gt; homestead-7: Verifying vmnet devices are healthy...
  ==&gt; homestead-7: Preparing network adapters...
  Vagrant found a port collision for the specified port and virtual machine.
  While this port was marked to be auto-corrected, the ports in the
  auto-correction range are all also used.
  
  VM: homestead-7
  Forwarded port: 80 =&gt; 8000
  </code></pre>
  
  <p>When I run <em>Vagrant global-status</em>, I get this:</p>
  
  <pre><code>id       name        provider      state       directory                           
  -----------------------------------------------------------------------
  410757f  homestead-7 vmware_fusion not running /Users/Me/Homestead  
  </code></pre>
  
  <p>I can't run <em>vagrant reload 410757f</em> as I get the same error above, and I can't provision the machine because it needs to be running.  </p>
  
  <p>I'm confused as to whats happening here. There is a networking colission, but I don't have any other vagrant boxes. I currently have 4 other Windows VM's, but I made sure I shut down each machine.</p>
  
  <p>I've even tried destroying and recreating the homestead box (no luck). Any ideas?</p>
  
  <p><strong>Edit</strong> To extend on this, I tried looking for the process using <em>sudo lsof -i :8000</em></p>
  
  <pre><code>COMMAND    PID USER   FD   TYPE            DEVICE SIZE/OFF NODE NAME
  vmnet-nat 3943 root   42u  IPv4 0x70d4a03b6f2dddd      0t0  TCP *:irdmi (LISTEN)
  </code></pre>
  
  <p>I killed that using <em>sudo kill -9 3943</em> and ran <em>sudo lsof -i :8000</em> again, which gave me nothing, then running homestead up again gave me the same error.</p>