vagrant up fails with VirtualBox 4.2.12

This is for discussing general topics about how to use VirtualBox.

vagrant up fails with VirtualBox 4.2.12

Postby hex » 18. Apr 2013, 09:22

I am running VirtualBox 4.2.12 r84980 on Windows 7 x64 with Vagrant version 1.2.1 and I noticed that vagrant up fails to run when Oracle VM VirtualBox Manager is not running. It throws this error:

Code: Select all   Expand viewCollapse view
Bringing machine 'default' up with 'virtualbox' provider...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["list", "vms"]

Stderr: VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.


If I keep the Oracle VM VirtualBox Manager open everything runs ok.
This started to happen when I upgraded VirtualBox from 4.2.10 r84105 to 4.2.12 r84980.

I was wondering how can I fix this or what is the problem?
hex
 
Posts: 1
Joined: 18. Apr 2013, 09:19

Re: vagrant up fails with VirtualBox 4.2.12

Postby noteirak » 18. Apr 2013, 10:20

Vagrant is a third party product and is not supported here.
About the Virtualbox error, there is no way to tell how you got there in the first place, since the product could have done virtually anything and everything.

Best would be to seek support at Vagrant directly, or use Virtualbox withouth it if you seek support here.
HyperBox - Open-source Entreprise Virtualization Manager - http://hyperbox.altherian.org
Manage your VirtualBox infrastructure the free way!
noteirak
Site Moderator
 
Posts: 3348
Joined: 13. Jan 2012, 11:14
Primary OS: Debian other
VBox Version: OSE Debian
Guest OSses: Debian, Win 2k8, Win 7

Re: vagrant up fails with VirtualBox 4.2.12

Postby irvingpop » 3. May 2013, 18:34

I experienced the same issue, here's how I resolved it:

1. Stop/kill all vagrant and virtualbox processes
2. Go to your home directory (usually C:\Users\<username> )
3. Rename or delete .vagrant.d and .Virtualbox
irvingpop
 
Posts: 1
Joined: 3. May 2013, 18:32


Return to Using VirtualBox

Who is online

Users browsing this forum: No registered users and 6 guests