Virtualbox + Vagrant Failures After El Capitan Upgrade

[This blog post was originally written by Triet Le]

The TL;DR version: make sure to upgrade your VirtualBox and Vagrant to the latest version(i.e v 5.0.6, v 1.7.4  respectively).Oracle VirtualBox

This is a follow up to our previous Vagrant post. After upgrading to El Capitan, I was unable to start any of my local Vagrant instances. When I tried to do a vagrant up, I got this from the command line:

The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'aborted' 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.

vagrant status return this

$ vagrant status
Current VM states:

default                  aborted

The VM is in an aborted state. This means that it was abruptly
stopped without properly closing the session. Run `vagrant up`
to resume this virtual machine. If any problems persist, you may
have to destroy and restart the virtual machine.

Even after vagrant reload and a vagrant destroy, I was still unable to get vagrant up (even though the status of those instances are now powered off). My new hypothesis was that this was related to Virtual Box. When I tried to manually start those VMs via the Virtual Box UI, I saw these messages in the log:

Kernel driver not installed (rc=-1908)  ..

00:02:17.385877 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={480b372c-c0b5-4c23-9bd7-dcbb85b1594c} aComponent={Display} aText={The console is not powered up}, preserve=false

00:02:17.401242 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={The object is not ready}, preserve=false

Long story short, after reading through their latest release change log, an upgrade to v 5.0.6 seems to fix the problem. Depending on what your current version of Vagrant is (mine was 1 year old), you also need to upgrade your Vagrant version to the latest (v 1.7.4).