title: Cannot vagrant ssh after successful vagrant up?
body: <p>I am on OSX El Capitan, using Vagrant 1.8.1 and Virtualbox 5.0.20 (latest versions in both cases). I am trying to <a href="https://i.stack.imgur.com/rgRwR.png" rel="nofollow noreferrer">set up a VM as described here</a>. </p>
  
  <p>I have run <code>vagrant up</code> with no obvious errors:</p>
  
  <pre><code>$ vagrant up
  
  Bringing machine 'default' up with 'virtualbox' provider...
  ==&gt; default: Importing base box 'trusty32'...
  ==&gt; default: Matching MAC address for NAT networking...
  ==&gt; default: Setting the name of the VM: pybossa-jujucharm_default_1464189010793_35912
  ==&gt; default: Clearing any previously set forwarded ports...
  ==&gt; default: Clearing any previously set network interfaces...
  ==&gt; default: Preparing network interfaces based on configuration...
      default: Adapter 1: nat
  ==&gt; default: Forwarding ports...
      default: 8000 (guest) =&gt; 8000 (host) (adapter 1)
      default: 7000 (guest) =&gt; 7000 (host) (adapter 1)
      default: 7001 (guest) =&gt; 7001 (host) (adapter 1)
      default: 22 (guest) =&gt; 2222 (host) (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
      default:
      default: Vagrant insecure key detected. Vagrant will automatically replace
      default: this with a newly generated keypair for better security.
      default:
      default: Inserting generated public key within guest...
      default: Removing insecure key from the guest if it's present...
      default: Key inserted! Disconnecting and reconnecting using new SSH key...
  ==&gt; default: Machine booted and ready!
  ==&gt; default: Checking for guest additions in VM...
      default: The guest additions on this VM do not match the installed version of
      default: VirtualBox! In most cases this is fine, but in rare cases it can
      default: prevent things such as shared folders from working properly. If you see
      default: shared folder errors, please make sure the guest additions within the
      default: virtual machine match the version of VirtualBox you have installed on
      default: your host and reload your VM.
      default:
      default: Guest Additions Version: 4.3.36
      default: VirtualBox Version: 5.0
  TLD but no host_name given. No patterns will be configured.
  pid-file for killed process 60204 found (/Users/anna/.vagrant.d/tmp/dns/daemon/vagrant-dns.pid), deleting.
  ==&gt; default: Restarted DNS Service
  ==&gt; default: Mounting shared folders...
      default: /vagrant =&gt; /Users/anna/Experiments/pybossa-jujucharm
  ==&gt; default: Running provisioner: shell...
      default: Running: /var/folders/hd/nfp3wlg90ms2ksf9ttkjymtr0000gn/T/vagrant-shell20160525-60263-1tuxdig.sh
  ==&gt; default: stdin: is not a tty
  ==&gt; default: + apt-get update -y
  ==&gt; default: Get:1 http://security.ubuntu.com trusty-security InRelease [65.9 kB]
  ==&gt; default: Ign http://archive.ubuntu.com trusty InRelease
  ==&gt; default: Get:2 http://archive.ubuntu.com trusty-updates InRelease [65.9 kB]
  ==&gt; default: Get:3 http://archive.ubuntu.com trusty-backports InRelease [65.9 kB]
  ==&gt; default: Hit http://archive.ubuntu.com trusty Release.gpg
  ==&gt; default: Get:4 http://security.ubuntu.com trusty-security/main Sources [115 kB]
  </code></pre>
  
  <p>But I can't ssh:</p>
  
  <pre><code>$ vagrant ssh
  VM must be created before running this command. Run `vagrant up` first.
  </code></pre>
  
  <p>And <code>vagrant status</code> says nothing has been created:</p>
  
  <pre><code>$ vagrant status
  Current machine states:
  
  default                   not created (virtualbox)
  
  The environment has not yet been created. Run `vagrant up` to
  create the environment. If a machine is not created, only the
  default provider will be shown. So if a provider is not listed,
  then the machine is not created for that environment.
  </code></pre>
  
  <p>What am I doing wrong?</p>
  
  <p>UPDATE: from the same directory:</p>
  
  <pre><code>$ vboxmanage list runningvms
  $ vboxmanage showvminfo pybossa-jujucharm_default_1464189010793_35912
  VBoxManage: error: Could not find a registered machine named 'pybossa-jujucharm_default_1464189010793_35912'
  VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
  VBoxManage: error: Context: "FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())" at line 2719 of file VBoxManageInfo.cpp
  </code></pre>
  
  <p>I don't have multiple copies of Virtualbox installed (at least not that I can see in Applications). This is what I see when I open Virtualbox:</p>
  
  <p><a href="https://i.stack.imgur.com/rgRwR.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/rgRwR.png" alt="enter image description here"></a></p>