virtualbox.org

well, it's not the order I suggested which may make a difference. However, did you install anything since 1/8 when things were working again?

smh, why would you install Vagrant again when one, we think that may have caused the problem, and two, we can't help you if you are running Vagrant?

My friend. If you insist on running vagrant it will not help you get response from here. They change so many permissions and run so many specific scripts that it would be impossible since we do not use/support vagrant.

I also would bring up you never mentioned this…

jfarr wrote: Per your comments earlier, this setup is working just fine for other team members.. but we've yet to identify what is different about my setup.

Unless you are all running identical Macs, same model, same year, same CPU, same Applications installed etc., that doesn't really mean anything. There have been certain models of Macs over the years that had a specific problem none of the others had. Mostly firmware issues.

OK. A restart after a fresh VirtualBox 4.3.2 install is working now. I ran vboxmanage and it didn't result in an error, then installed vagrant 1.7.2 and ran the command again, no error.

It's necessary for me to use vagrant, so I'm now proceeding to create a VM through the standard vagrant processes.

I suspect the root cause is an intermittent permissions issue, but as of yet don't have a method to prove/disprove that. Googling for info on vboxmanage logs seems to show info about logging for specific guests, which is a step after where I was getting stopped and as such wasn't helping much. https://blogs.oracle.com/fatbloke/entry ... _log_files

Any other information is greatly appreciated.. at this point I'm expecting to come across this issue again.

loukingjr wrote:I also would bring up you never mentioned this…

jfarr wrote: Per your comments earlier, this setup is working just fine for other team members.. but we've yet to identify what is different about my setup.

Unless you are all running identical Macs, same model, same year, same CPU, same Applications installed etc., that doesn't really mean anything. There have been certain models of Macs over the years that had a specific problem none of the others had. Mostly firmware issues.

My macbook is an older model (2011), if need be I'll request a newer one from IT and have this one nuked.

Just to make it clear, it is possible you run a third-party application that your team is not running that could be causing you a problem.

What I can say is I have been using Macs for going on 30 years. I have three right now running VB 4.3.20. The two in my signature and a Late 2011 iMac. I also have VMWare Fusion 7.1 installed which has an OSX 10.9.5 guest installed in which I installed VB 4.3.20 which I can do because I can pass VT-x/AMD-v through. None of them have your error.