RPC_S_SERVER_UNAVAILABLE error all the time

[panique]

removed

[mitchellh]

Hi,

I'm sorry this is happening. Unfortunately, this is caused by a bug in VirtualBox. VirtualBox 4.2.14 has a serious bug that makes it not work at all (with or without Vagrant). You need to downgrade to 4.2.12.

As for documentation, there most certainly is documentation, a lot of it. http://docs.vagrantup.com

The mailing list is very useful, and thousands of people use it. If you want better support for the completely free open source software you're using, you're more than welcome to pay for it.

[panique]

Thanks for this good answer! That's the problem with open source software: it might be good software, but nobody knows how to handle it. I mean, this issue for example, is known to the devs, but it's not public. The documentation totally lacks of exactly this. If something does not work exactly like in the tutorial, then you are lost. It's a pity, because i think much much much more people would use Vagrant then. The mailing list is not really useable, as it's not possible to get information, it's simply not possible to search & find solutions. In this case, i could not use google and get useful information, i would have to sign up to hte mailing list, verify this, then post a "bug report", then everybody screams because i'm #100 who posts this, then maybe days later somebody posts the solution. and yes, i would pay A LOT for vagrant. good software should be paid for. but it's hard to even get into Vagrant (= try it out) if there's no real possibility to get over blocking issues (like this one). Maybe critical bugs/blockers should be documented to make it easy for people to try out Vagrant.

By the way, this is a very interesting topic...

[mitchellh]

@panique I googled your subject and a solution was the first result: http://d.pr/i/MG1y

[joanbarros]

Hi, @mitchellh, I'm having this error also. VirtualBox 4.2.14.

When you say that VirtualBox doesn't work with or without Vagrant, you mean at all? because I can load VM's via the normal VirtualBox method. i.e: double click the VM in the manager.

If VirtualBox works, should Vagrant work?

PS: Should I have posted this elsewhere?

[mitchellh]

VirtualBox 4.2.16 fixes this issue.

@joanbarros No, VirtualBox broke critical backwards compatibility with previously exported VMs.

[joanbarros]

Hmm.. That's weird... I have 2 VMs that come from an older version and they work perfectly fine.

I'll see if 4.2.16 fixes my problem.

Thanks! :)

PS: Love Vagrant!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.