vagrant up fails with VirtualBox 4.2.12 #1622

Closed
hex opened this Issue Apr 18, 2013 · 24 comments

Comments

Projects
None yet
@hex

hex commented Apr 18, 2013

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:

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.

@mitchellh

This comment has been minimized.

Show comment
Hide comment
@mitchellh

mitchellh Apr 18, 2013

Member

This is an issue with VirtualBox. I'd recommend asking the VirtualBox forum for more info on this. If there is a way Vagrant can avoid the issue, I'm happy to look into it, though.

Member

mitchellh commented Apr 18, 2013

This is an issue with VirtualBox. I'd recommend asking the VirtualBox forum for more info on this. If there is a way Vagrant can avoid the issue, I'm happy to look into it, though.

@mitchellh mitchellh closed this Apr 18, 2013

@gabrielfgularte

This comment has been minimized.

Show comment
Hide comment
@gabrielfgularte

gabrielfgularte Apr 27, 2013

I've read the @hex post in VirtualBox's forum asking for help. The answer:

"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 without it if you seek support here."

Someone have done with it? I have the same issue here... =/

I've read the @hex post in VirtualBox's forum asking for help. The answer:

"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 without it if you seek support here."

Someone have done with it? I have the same issue here... =/

@benletib

This comment has been minimized.

Show comment
Hide comment
@benletib

benletib Apr 27, 2013

Similar for me, but it doesn't work more with opened vb manager gui.

I've tried with vb 4.2.6, and an up-to-date vb 4.2.12.
A vboxmanage process is created, but nothing happens. I have to kill the process to see the error.

C:\WEB-DEV\Ruby>vagrant up
 INFO global: Vagrant version: 1.2.2
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/box/plugin.rb
 INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/destroy/plugin.rb
 INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/halt/plugin.rb
 INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/init/plugin.rb
 INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/package/plugin.rb
 INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/plugin/plugin.rb
 INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/provision/plugin.rb
 INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/reload/plugin.rb
 INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/resume/plugin.rb
 INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/ssh/plugin.rb
 INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/ssh_config/plugin.rb
 INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/status/plugin.rb
 INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/suspend/plugin.rb
 INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/up/plugin.rb
 INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/communicators/ssh/plugin.rb
 INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/arch/plugin.rb
 INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/debian/plugin.rb
 INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/fedora/plugin.rb
 INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/linux/plugin.rb
 INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/openbsd/plugin.rb
 INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/pld/plugin.rb
 INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/redhat/plugin.rb
 INFO manager: Registered plugin: RedHat guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/solaris/plugin.rb
 INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/suse/plugin.rb
 INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/ubuntu/plugin.rb
 INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/arch/plugin.rb
 INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/bsd/plugin.rb
 INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/fedora/plugin.rb
 INFO manager: Registered plugin: Fedora host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/linux/plugin.rb
 INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/opensuse/plugin.rb
 INFO manager: Registered plugin: OpenSUSE host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/windows/plugin.rb
 INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/kernel_v1/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/kernel_v2/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/plugin.rb
 INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/provisioners/ansible/plugin.rb
 INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/provisioners/cfengine/plugin.rb
 INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/provisioners/chef/plugin.rb
 INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/provisioners/puppet/plugin.rb
 INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/provisioners/shell/plugin.rb
 INFO manager: Registered plugin: shell
 INFO vagrant: `vagrant` invoked: ["up"]
DEBUG vagrant: Creating Vagrant environment
 INFO environment: Environment initialized (#<Vagrant::Environment:0x2a68640>)
 INFO environment:   - cwd: C:/WEB-DEV/Ruby
 INFO environment: Home path: C:/Users/Ben LeTibetain/.vagrant.d
 INFO environment: Local data path: C:/WEB-DEV/Ruby/.vagrant
DEBUG environment: Creating: C:/WEB-DEV/Ruby/.vagrant
DEBUG environment: Loading plugins from: C:/Users/Ben LeTibetain/.vagrant.d/plugins.json
 INFO environment: Running hook: environment_load
 INFO environment: Initializing config...
 INFO loader: Set :default = "C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/config/default.rb"
DEBUG loader: Populating proc cache for "C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/config/default.rb"
DEBUG loader: Load procs for pathname: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/config/default.rb
 INFO loader: Set :root = #<Pathname:C:/WEB-DEV/Ruby/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:C:/WEB-DEV/Ruby/Vagrantfile>
DEBUG loader: Load procs for pathname: C:/WEB-DEV/Ruby/Vagrantfile
 INFO loader: Loading configuration in order: [:default, :home, :root]
DEBUG loader: Loading from: default (evaluating)
DEBUG loader: Loading from: root (evaluating)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG hosts: Host path search classes: [VagrantPlugins::HostWindows::Host, VagrantPlugins::HostOpenSUSE::Host, VagrantPlugins::Hos
tArch::Host, VagrantPlugins::HostFedora::Host, VagrantPlugins::HostFreeBSD::Host, VagrantPlugins::HostGentoo::Host, VagrantPlugins
::HostLinux::Host, VagrantPlugins::HostBSD::Host]
 INFO hosts: Host class: VagrantPlugins::HostWindows::Host
 INFO runner: Running action: #<Vagrant::Action::Builder:0x2f0e638>
 INFO cli: CLI: [] "up" []
DEBUG cli: Invoking command class: VagrantPlugins::CommandUp::Command []
DEBUG command: 'Up' each target VM...
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command:  -- names: []
DEBUG command:  -- options: {:provider=>nil}
DEBUG command: Loading all machines...
 INFO environment: Getting machine: default (virtualbox)
 INFO environment: Uncached load of machine.
 INFO loader: Set :vm_default = []
 INFO loader: Loading configuration in order: [:default, :home, :root, :vm_default]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
 INFO environment: Provider-supported box formats: [:virtualbox]
 INFO box_collection: Searching for box: precise64 (virtualbox) in C:/Users/Ben LeTibetain/.vagrant.d/boxes/precise64/virtualbox/met
adata.json
 INFO box_collection: Box found: precise64 (virtualbox)
 INFO environment: Box found with format: virtualbox
 INFO environment: Box exists with Vagrantfile. Reloading machine config.
 INFO loader: Set :box_precise64_virtualbox = #<Pathname:C:/Users/Ben LeTibetain/.vagrant.d/boxes/precise64/virtualbox/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:C:/Users/Ben LeTibetain/.vagrant.d/boxes/precise64/virtualbox/Vagrantfile>
DEBUG loader: Load procs for pathname: C:/Users/Ben LeTibetain/.vagrant.d/boxes/precise64/virtualbox/Vagrantfile
 INFO loader: Loading configuration in order: [:default, :box_precise64_virtualbox, :home, :root, :vm_default]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: box_precise64_virtualbox (evaluating)
DEBUG loader: Upgrading config from version 1 to 2
DEBUG loader: Upgrading config to version 2
DEBUG loader: Upgraded to version 2 with 0 warnings and 0 errors
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
 INFO machine: Initializing machine: default
 INFO machine:   - Provider: VagrantPlugins::ProviderVirtualBox::Provider
 INFO machine:   - Box: #<Vagrant::Box:0x2a1eac8>
 INFO machine:   - Data dir: C:/WEB-DEV/Ruby/.vagrant/machines/default/virtualbox
DEBUG virtualbox: Instantiating the driver for machine ID: nil
DEBUG base: Windows. Trying VBOX_INSTALL_PATH for VBoxManage
DEBUG base: VBOX_INSTALL_PATH value: C:\Program Files\Oracle\VirtualBox\
 INFO base: VBoxManage path: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
 INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "--version"]


*****************************************************************
===> Stucked here, so I killed the vboxmanage process
*****************************************************************


DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
 INFO environment: Running hook: environment_unload
 INFO runner: Running action: #<Vagrant::Action::Builder:0x349c368>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr: >
ERROR vagrant: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr:
ERROR vagrant: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/driver/base.rb:316:in `execute'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/driver/meta.rb:123:in `read_version'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/driver/meta.rb:34:in `initialize'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/provider.rb:34:in `new'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/provider.rb:34:in `machine_id_changed'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/provider.rb:14:in `initialize'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/machine.rb:116:in `new'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/machine.rb:116:in `initialize'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:417:in `new'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:417:in `machine'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/plugin/v2/command.rb:131:in `block in with_target_vms'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/plugin/v2/command.rb:164:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/plugin/v2/command.rb:164:in `block in with_target_vms'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/plugin/v2/command.rb:163:in `map'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/plugin/v2/command.rb:163:in `with_target_vms'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/up/command.rb:42:in `block in execute'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:206:in `block (2 levels) in batch'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:204:in `tap'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:204:in `block in batch'
<internal:prelude>:10:in `synchronize'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:203:in `batch'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/up/command.rb:41:in `execute'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/cli.rb:46:in `execute'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:467:in `cli'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/bin/vagrant:84:in `<top (required)>'
C:/HashiCorp/Vagrant/bin//../embedded/../embedded/gems/bin/vagrant:23:in `load'
C:/HashiCorp/Vagrant/bin//../embedded/../embedded/gems/bin/vagrant:23:in `<main>'
 INFO interface: error: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr:
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr:

Similar for me, but it doesn't work more with opened vb manager gui.

I've tried with vb 4.2.6, and an up-to-date vb 4.2.12.
A vboxmanage process is created, but nothing happens. I have to kill the process to see the error.

C:\WEB-DEV\Ruby>vagrant up
 INFO global: Vagrant version: 1.2.2
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/box/plugin.rb
 INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/destroy/plugin.rb
 INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/halt/plugin.rb
 INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/init/plugin.rb
 INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/package/plugin.rb
 INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/plugin/plugin.rb
 INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/provision/plugin.rb
 INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/reload/plugin.rb
 INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/resume/plugin.rb
 INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/ssh/plugin.rb
 INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/ssh_config/plugin.rb
 INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/status/plugin.rb
 INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/suspend/plugin.rb
 INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/up/plugin.rb
 INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/communicators/ssh/plugin.rb
 INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/arch/plugin.rb
 INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/debian/plugin.rb
 INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/fedora/plugin.rb
 INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/linux/plugin.rb
 INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/openbsd/plugin.rb
 INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/pld/plugin.rb
 INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/redhat/plugin.rb
 INFO manager: Registered plugin: RedHat guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/solaris/plugin.rb
 INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/suse/plugin.rb
 INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/guests/ubuntu/plugin.rb
 INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/arch/plugin.rb
 INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/bsd/plugin.rb
 INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/fedora/plugin.rb
 INFO manager: Registered plugin: Fedora host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/freebsd/plugin.rb
 INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/gentoo/plugin.rb
 INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/linux/plugin.rb
 INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/opensuse/plugin.rb
 INFO manager: Registered plugin: OpenSUSE host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/hosts/windows/plugin.rb
 INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/kernel_v1/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/kernel_v2/plugin.rb
 INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/plugin.rb
 INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/provisioners/ansible/plugin.rb
 INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/provisioners/cfengine/plugin.rb
 INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/provisioners/chef/plugin.rb
 INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/provisioners/puppet/plugin.rb
 INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/provisioners/shell/plugin.rb
 INFO manager: Registered plugin: shell
 INFO vagrant: `vagrant` invoked: ["up"]
DEBUG vagrant: Creating Vagrant environment
 INFO environment: Environment initialized (#<Vagrant::Environment:0x2a68640>)
 INFO environment:   - cwd: C:/WEB-DEV/Ruby
 INFO environment: Home path: C:/Users/Ben LeTibetain/.vagrant.d
 INFO environment: Local data path: C:/WEB-DEV/Ruby/.vagrant
DEBUG environment: Creating: C:/WEB-DEV/Ruby/.vagrant
DEBUG environment: Loading plugins from: C:/Users/Ben LeTibetain/.vagrant.d/plugins.json
 INFO environment: Running hook: environment_load
 INFO environment: Initializing config...
 INFO loader: Set :default = "C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/config/default.rb"
DEBUG loader: Populating proc cache for "C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/config/default.rb"
DEBUG loader: Load procs for pathname: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/config/default.rb
 INFO loader: Set :root = #<Pathname:C:/WEB-DEV/Ruby/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:C:/WEB-DEV/Ruby/Vagrantfile>
DEBUG loader: Load procs for pathname: C:/WEB-DEV/Ruby/Vagrantfile
 INFO loader: Loading configuration in order: [:default, :home, :root]
DEBUG loader: Loading from: default (evaluating)
DEBUG loader: Loading from: root (evaluating)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG hosts: Host path search classes: [VagrantPlugins::HostWindows::Host, VagrantPlugins::HostOpenSUSE::Host, VagrantPlugins::Hos
tArch::Host, VagrantPlugins::HostFedora::Host, VagrantPlugins::HostFreeBSD::Host, VagrantPlugins::HostGentoo::Host, VagrantPlugins
::HostLinux::Host, VagrantPlugins::HostBSD::Host]
 INFO hosts: Host class: VagrantPlugins::HostWindows::Host
 INFO runner: Running action: #<Vagrant::Action::Builder:0x2f0e638>
 INFO cli: CLI: [] "up" []
DEBUG cli: Invoking command class: VagrantPlugins::CommandUp::Command []
DEBUG command: 'Up' each target VM...
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command:  -- names: []
DEBUG command:  -- options: {:provider=>nil}
DEBUG command: Loading all machines...
 INFO environment: Getting machine: default (virtualbox)
 INFO environment: Uncached load of machine.
 INFO loader: Set :vm_default = []
 INFO loader: Loading configuration in order: [:default, :home, :root, :vm_default]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
 INFO environment: Provider-supported box formats: [:virtualbox]
 INFO box_collection: Searching for box: precise64 (virtualbox) in C:/Users/Ben LeTibetain/.vagrant.d/boxes/precise64/virtualbox/met
adata.json
 INFO box_collection: Box found: precise64 (virtualbox)
 INFO environment: Box found with format: virtualbox
 INFO environment: Box exists with Vagrantfile. Reloading machine config.
 INFO loader: Set :box_precise64_virtualbox = #<Pathname:C:/Users/Ben LeTibetain/.vagrant.d/boxes/precise64/virtualbox/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:C:/Users/Ben LeTibetain/.vagrant.d/boxes/precise64/virtualbox/Vagrantfile>
DEBUG loader: Load procs for pathname: C:/Users/Ben LeTibetain/.vagrant.d/boxes/precise64/virtualbox/Vagrantfile
 INFO loader: Loading configuration in order: [:default, :box_precise64_virtualbox, :home, :root, :vm_default]
DEBUG loader: Loading from: default (cache)
DEBUG loader: Loading from: box_precise64_virtualbox (evaluating)
DEBUG loader: Upgrading config from version 1 to 2
DEBUG loader: Upgrading config to version 2
DEBUG loader: Upgraded to version 2 with 0 warnings and 0 errors
DEBUG loader: Loading from: root (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
 INFO machine: Initializing machine: default
 INFO machine:   - Provider: VagrantPlugins::ProviderVirtualBox::Provider
 INFO machine:   - Box: #<Vagrant::Box:0x2a1eac8>
 INFO machine:   - Data dir: C:/WEB-DEV/Ruby/.vagrant/machines/default/virtualbox
DEBUG virtualbox: Instantiating the driver for machine ID: nil
DEBUG base: Windows. Trying VBOX_INSTALL_PATH for VBoxManage
DEBUG base: VBOX_INSTALL_PATH value: C:\Program Files\Oracle\VirtualBox\
 INFO base: VBoxManage path: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
 INFO subprocess: Starting process: ["C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe", "--version"]


*****************************************************************
===> Stucked here, so I killed the vboxmanage process
*****************************************************************


DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
 INFO environment: Running hook: environment_unload
 INFO runner: Running action: #<Vagrant::Action::Builder:0x349c368>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::VBoxManageError: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr: >
ERROR vagrant: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr:
ERROR vagrant: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/driver/base.rb:316:in `execute'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/driver/meta.rb:123:in `read_version'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/driver/meta.rb:34:in `initialize'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/provider.rb:34:in `new'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/provider.rb:34:in `machine_id_changed'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/providers/virtualbox/provider.rb:14:in `initialize'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/machine.rb:116:in `new'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/machine.rb:116:in `initialize'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:417:in `new'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:417:in `machine'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/plugin/v2/command.rb:131:in `block in with_target_vms'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/plugin/v2/command.rb:164:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/plugin/v2/command.rb:164:in `block in with_target_vms'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/plugin/v2/command.rb:163:in `map'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/plugin/v2/command.rb:163:in `with_target_vms'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/up/command.rb:42:in `block in execute'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:206:in `block (2 levels) in batch'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:204:in `tap'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:204:in `block in batch'
<internal:prelude>:10:in `synchronize'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:203:in `batch'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/plugins/commands/up/command.rb:41:in `execute'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/cli.rb:46:in `execute'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/environment.rb:467:in `cli'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.2.2/bin/vagrant:84:in `<top (required)>'
C:/HashiCorp/Vagrant/bin//../embedded/../embedded/gems/bin/vagrant:23:in `load'
C:/HashiCorp/Vagrant/bin//../embedded/../embedded/gems/bin/vagrant:23:in `<main>'
 INFO interface: error: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr:
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["--version"]

Stderr:

@bluefoxicy

This comment has been minimized.

Show comment
Hide comment
@bluefoxicy

bluefoxicy May 2, 2013

Bringing machine 'wcm_devagrant' up with 'virtualbox' provider...
[wcm_devagrant] Setting the name of the VM...
[wcm_devagrant] 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.

Manually:

C:\>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list vms
"Ubuntu" {19edf8cb-0496-4df0-a4f5-378d8487ff71}
"ReactOS" {917fa7f9-417f-486a-965e-12fa488a3e12}
"ubuntu_puppet" {6c6743a9-6302-4810-a411-0cf1d12a4b62}
"wcm-dev_1367510859" {be165b34-21af-4185-8a2c-d2fd42698a21}

This occurred in the middle of using vagrant on a system where it had been working, when I upgraded the base box and modified the Vagrantfile. I didn't upgrade VirtualBox (4.2.6) or Vagrant (1.2.1). I destroyed that box and tried switching back, but no luck; seems to have permanently disabled Vagrant.

After some hammering, it seems that Windows is not granting Vagrant administrative access when it runs VBoxManage anymore.

Bringing machine 'wcm_devagrant' up with 'virtualbox' provider...
[wcm_devagrant] Setting the name of the VM...
[wcm_devagrant] 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.

Manually:

C:\>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list vms
"Ubuntu" {19edf8cb-0496-4df0-a4f5-378d8487ff71}
"ReactOS" {917fa7f9-417f-486a-965e-12fa488a3e12}
"ubuntu_puppet" {6c6743a9-6302-4810-a411-0cf1d12a4b62}
"wcm-dev_1367510859" {be165b34-21af-4185-8a2c-d2fd42698a21}

This occurred in the middle of using vagrant on a system where it had been working, when I upgraded the base box and modified the Vagrantfile. I didn't upgrade VirtualBox (4.2.6) or Vagrant (1.2.1). I destroyed that box and tried switching back, but no luck; seems to have permanently disabled Vagrant.

After some hammering, it seems that Windows is not granting Vagrant administrative access when it runs VBoxManage anymore.

@mitchellh

This comment has been minimized.

Show comment
Hide comment
@mitchellh

mitchellh May 2, 2013

Member

Unfortunately this is an issue with VirtualBox. The next version Vagrant (will be 1.2.3) contains better error detection for this, but it revolves around some weird fact that if you have VirtualBox GUI open, it will fail to start the COM server. Or if you started it under a different user, it can't talk to it.

For best results, quit all VirtualBox UIs, halt all VirtualBox VMs, and only use Vagrant + VirtualBox from a single user.

Member

mitchellh commented May 2, 2013

Unfortunately this is an issue with VirtualBox. The next version Vagrant (will be 1.2.3) contains better error detection for this, but it revolves around some weird fact that if you have VirtualBox GUI open, it will fail to start the COM server. Or if you started it under a different user, it can't talk to it.

For best results, quit all VirtualBox UIs, halt all VirtualBox VMs, and only use Vagrant + VirtualBox from a single user.

@davidagraf

This comment has been minimized.

Show comment
Hide comment
@davidagraf

davidagraf May 22, 2013

Might be important:
I had the same issue after upgrading virtual box and vagrant to the latest versions on my Windows 7 machine. Afterwards, I downgraded Virtual Box to 4.2.10. And still had the same issue. Fortunately, it disappeared after removing the following port mapping which I had in my Vagrantfile by accident (I spend several hours re-installing everything several times till I figured this out :-( ):

config.vm.network :forwarded_port, guest: 8080, host: 8080

No clue why. But if I put the mapping back, if fails again with the same error message. I didn't test it with Virtual Box 4.2.12 ...

But I still have sometimes the following error when shutting down the box:
$ vagrant halt
[default] Attempting graceful shutdown of VM...
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["showvminfo", "e3a35b03-12ad-4495-b92a-03ad94fa9849", "--machinereadable"]

Stderr: VBoxManage.exe: error: The object is not ready
VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component Console, interface IConsole, callee IUnknown
VBoxManage.exe: error: Context: "COMGETTER(RemoteUSBDevices)(ComSafeArrayAsOutParam(coll))" at lin 1840 of file VBoxManageInfo.cpp

Luckily, the box can still be started afterwards without errors.

Might be important:
I had the same issue after upgrading virtual box and vagrant to the latest versions on my Windows 7 machine. Afterwards, I downgraded Virtual Box to 4.2.10. And still had the same issue. Fortunately, it disappeared after removing the following port mapping which I had in my Vagrantfile by accident (I spend several hours re-installing everything several times till I figured this out :-( ):

config.vm.network :forwarded_port, guest: 8080, host: 8080

No clue why. But if I put the mapping back, if fails again with the same error message. I didn't test it with Virtual Box 4.2.12 ...

But I still have sometimes the following error when shutting down the box:
$ vagrant halt
[default] Attempting graceful shutdown of VM...
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["showvminfo", "e3a35b03-12ad-4495-b92a-03ad94fa9849", "--machinereadable"]

Stderr: VBoxManage.exe: error: The object is not ready
VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component Console, interface IConsole, callee IUnknown
VBoxManage.exe: error: Context: "COMGETTER(RemoteUSBDevices)(ComSafeArrayAsOutParam(coll))" at lin 1840 of file VBoxManageInfo.cpp

Luckily, the box can still be started afterwards without errors.

@nathanpalmer

This comment has been minimized.

Show comment
Hide comment
@nathanpalmer

nathanpalmer Jun 19, 2013

I was running into this issue as well when attempting to start up a new box. I also tested it by just listing out the VMS directly through VBoxManage.exe

& 'C:\Program Files\Oracle\VirtualBox\VBoxManage.exe' list vms

That failed with the same error message

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.

It came down to the fact that I was running from an elevated prompt (Administrator.)

I was running into this issue as well when attempting to start up a new box. I also tested it by just listing out the VMS directly through VBoxManage.exe

& 'C:\Program Files\Oracle\VirtualBox\VBoxManage.exe' list vms

That failed with the same error message

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.

It came down to the fact that I was running from an elevated prompt (Administrator.)

@Enalmada

This comment has been minimized.

Show comment
Hide comment
@Enalmada

Enalmada Jun 29, 2013

I just got hit with the "CO_E_SERVER_EXEC_FAILURE" error when trying to run vagrant up in a windows administrator console. I usually run in an elevated prompt (Administrator) to avoid the popups. Running in regular prompt helped. Thanks to @nathanpalmer for the hint.

I just got hit with the "CO_E_SERVER_EXEC_FAILURE" error when trying to run vagrant up in a windows administrator console. I usually run in an elevated prompt (Administrator) to avoid the popups. Running in regular prompt helped. Thanks to @nathanpalmer for the hint.

@wxl3000

This comment has been minimized.

Show comment
Hide comment
@wxl3000

wxl3000 Jul 7, 2013

To see if you set the virtualbox path to your Windows Environment Path, if not, set it, that should be working...

wxl3000 commented Jul 7, 2013

To see if you set the virtualbox path to your Windows Environment Path, if not, set it, that should be working...

@bwalsh

This comment has been minimized.

Show comment
Hide comment
@bwalsh

bwalsh Jul 13, 2013

This happens intermittently to me (running vagrant 1.2.2 on windows 7 pro ) For what it's worth, if I go into virtualbox, start the machine, power it off in virtual box, return to the command prompt and start vagrant it works.... your mileage may vary

bwalsh commented Jul 13, 2013

This happens intermittently to me (running vagrant 1.2.2 on windows 7 pro ) For what it's worth, if I go into virtualbox, start the machine, power it off in virtual box, return to the command prompt and start vagrant it works.... your mileage may vary

@sohoffice

This comment has been minimized.

Show comment
Hide comment
@sohoffice

sohoffice Aug 17, 2013

I think @davidagraf is right about port mapping.
I just removed some ports (in my case they are 5000 and 5432) and it works right away.
I'm using vagrant 1.2.2 + virtualbox 4.2.10.
ps. I've tried to restore the port mapping and upgrade to vagrant 1.2.7, unfortunately it doesn't help.

I think @davidagraf is right about port mapping.
I just removed some ports (in my case they are 5000 and 5432) and it works right away.
I'm using vagrant 1.2.2 + virtualbox 4.2.10.
ps. I've tried to restore the port mapping and upgrade to vagrant 1.2.7, unfortunately it doesn't help.

@bstetler

This comment has been minimized.

Show comment
Hide comment
@bstetler

bstetler Aug 21, 2013

This seemed to be broke. I installed the newest version of vagrant and it does not work out of the box... Windows7 64bit, Vagrant 1.2.7, Virtual Box 4.2.16

C:\VMs>vagrant up
Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.

Vagrant uses the VBoxManage binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
VBoxManage binary and add it to the PATH environmental variable.

I went back to the top of this issue and read that using an elevated prompt caused the issue. I ran a prompt as my user and it seems to be working... So I guess running a cmd prompt as administrator causes the issue...

This seemed to be broke. I installed the newest version of vagrant and it does not work out of the box... Windows7 64bit, Vagrant 1.2.7, Virtual Box 4.2.16

C:\VMs>vagrant up
Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.

Vagrant uses the VBoxManage binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
VBoxManage binary and add it to the PATH environmental variable.

I went back to the top of this issue and read that using an elevated prompt caused the issue. I ran a prompt as my user and it seems to be working... So I guess running a cmd prompt as administrator causes the issue...

@sean-zou

This comment has been minimized.

Show comment
Hide comment
@sean-zou

sean-zou Sep 10, 2013

Was having the same issue, and it turns out that I have to put the the forwarding ports in ascending order.

Was having the same issue, and it turns out that I have to put the the forwarding ports in ascending order.

@jhabdas

This comment has been minimized.

Show comment
Hide comment
@jhabdas

jhabdas Sep 15, 2013

Same here using Windows 8. The error started occurring after I added my 4th port forward to the Vagrantfile. After removing one of the other forwarded ports, the error went away.

Port forwards before the issue started occurring

config.vm.network :forwarded_port, guest: 80, host: 8080
config.vm.network :forwarded_port, guest: 4567, host: 4567
config.vm.network :forwarded_port, guest: 3333, host: 3333

Port forwards in config when error was occurring

config.vm.network :forwarded_port, guest: 80, host: 8080
config.vm.network :forwarded_port, guest: 4567, host: 4567
config.vm.network :forwarded_port, guest: 3333, host: 3333
config.vm.network :forwarded_port, guest: 4000, host: 4000

Resolved by removing a forwarded port, like

config.vm.network :forwarded_port, guest: 80, host: 8080
config.vm.network :forwarded_port, guest: 4567, host: 4567
config.vm.network :forwarded_port, guest: 4000, host: 4000

I also tried reordering, as suggested by @seanzoucn, but that had no effect for me.

jhabdas commented Sep 15, 2013

Same here using Windows 8. The error started occurring after I added my 4th port forward to the Vagrantfile. After removing one of the other forwarded ports, the error went away.

Port forwards before the issue started occurring

config.vm.network :forwarded_port, guest: 80, host: 8080
config.vm.network :forwarded_port, guest: 4567, host: 4567
config.vm.network :forwarded_port, guest: 3333, host: 3333

Port forwards in config when error was occurring

config.vm.network :forwarded_port, guest: 80, host: 8080
config.vm.network :forwarded_port, guest: 4567, host: 4567
config.vm.network :forwarded_port, guest: 3333, host: 3333
config.vm.network :forwarded_port, guest: 4000, host: 4000

Resolved by removing a forwarded port, like

config.vm.network :forwarded_port, guest: 80, host: 8080
config.vm.network :forwarded_port, guest: 4567, host: 4567
config.vm.network :forwarded_port, guest: 4000, host: 4000

I also tried reordering, as suggested by @seanzoucn, but that had no effect for me.

@dilignt

This comment has been minimized.

Show comment
Hide comment
@dilignt

dilignt Oct 7, 2013

Same here using Windows 8. After reading @jhabdas post above I've found that removing my 4th port forward also fixed the problem. How do I get more than 3 ports to forward from the vm?

dilignt commented Oct 7, 2013

Same here using Windows 8. After reading @jhabdas post above I've found that removing my 4th port forward also fixed the problem. How do I get more than 3 ports to forward from the vm?

@brugnara

This comment has been minimized.

Show comment
Hide comment
@brugnara

brugnara Oct 9, 2013

starting as a non admin user, solved for me, many thanks.

brugnara commented Oct 9, 2013

starting as a non admin user, solved for me, many thanks.

@dilignt

This comment has been minimized.

Show comment
Hide comment
@dilignt

dilignt Oct 11, 2013

@djhell it doesn't make any different whether I run as administrator or not - running VBoxManage.exe works in either administrator or non-admin consoles. There seems no way of having more than 3 forwarded ports for me.

dilignt commented Oct 11, 2013

@djhell it doesn't make any different whether I run as administrator or not - running VBoxManage.exe works in either administrator or non-admin consoles. There seems no way of having more than 3 forwarded ports for me.

@Tomdarkness

This comment has been minimized.

Show comment
Hide comment
@Tomdarkness

Tomdarkness Oct 11, 2013

Contributor

Also got the same problem with more than 3 forwarded ports. How do you know this is an issue with VirtualBox? If I look at the commands vagrant executes upon running vagrant up then execute them in a .bat like so:

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" --version
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a3
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" --version
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list hostonlyifs 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" --version 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list hostonlyifs 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list systemproperties 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list vms 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list vms 

Then every single command executes fine. Only when Vagrant executes them does the final list vms fail.

Contributor

Tomdarkness commented Oct 11, 2013

Also got the same problem with more than 3 forwarded ports. How do you know this is an issue with VirtualBox? If I look at the commands vagrant executes upon running vagrant up then execute them in a .bat like so:

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" --version
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a3
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" --version
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list hostonlyifs 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" --version 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list hostonlyifs 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list systemproperties 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list vms 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo 4f076722-a388-4d23-ab83-5933cd2361c9 --machinereadable 
"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list vms 

Then every single command executes fine. Only when Vagrant executes them does the final list vms fail.

@Tomdarkness

This comment has been minimized.

Show comment
Hide comment
@Tomdarkness

Tomdarkness Oct 11, 2013

Contributor

Been playing around a bit and it appears to be the result of a race condition. Basically, the VBoxSVC.exe COM server will exit after a short while if you don't issue a command to it, don't have the GUI open or are not running a VM.

If there is a delay that is just the right amount of time between issuing commands then the COM server will be shutting down just as you execute the command and won't startup again for the command you just issued.

HandleForwardPortCollisions on my machine just happens to take the correct amount of time to enable this to happen when you are using 4 port forwards. 1 less or 1 more port forward means it does not take the correct amount of time and this never happens. You can also see this by adding a sleep of about 3-8 seconds to plugins\providers\virtualbox\driver\base.rb#raw so that the timing is sufficiently altered on command executions to avoid this issue.

All Vagrant needs to do to work around this is just retry the command after a short delay of something like 1 or 2 seconds and it will work fine.

Contributor

Tomdarkness commented Oct 11, 2013

Been playing around a bit and it appears to be the result of a race condition. Basically, the VBoxSVC.exe COM server will exit after a short while if you don't issue a command to it, don't have the GUI open or are not running a VM.

If there is a delay that is just the right amount of time between issuing commands then the COM server will be shutting down just as you execute the command and won't startup again for the command you just issued.

HandleForwardPortCollisions on my machine just happens to take the correct amount of time to enable this to happen when you are using 4 port forwards. 1 less or 1 more port forward means it does not take the correct amount of time and this never happens. You can also see this by adding a sleep of about 3-8 seconds to plugins\providers\virtualbox\driver\base.rb#raw so that the timing is sufficiently altered on command executions to avoid this issue.

All Vagrant needs to do to work around this is just retry the command after a short delay of something like 1 or 2 seconds and it will work fine.

@Tomdarkness

This comment has been minimized.

Show comment
Hide comment
@Tomdarkness

Tomdarkness Oct 11, 2013

Contributor

Okay, Vagrant should actually be trying the command after a delay of 1s anyway but there appears to be a bug stopping it from retrying the command. My PR #2365 should fix the underlying issue which should also make this issue go away as well.

Contributor

Tomdarkness commented Oct 11, 2013

Okay, Vagrant should actually be trying the command after a delay of 1s anyway but there appears to be a bug stopping it from retrying the command. My PR #2365 should fix the underlying issue which should also make this issue go away as well.

@schlamar

This comment has been minimized.

Show comment
Hide comment
@schlamar

schlamar Oct 17, 2013

Contributor

I was able to solve various issues with vagrant and DCOM (e.g. running vagrant in a Jenkins job failed with error message above) by disabling DCOM authentication:

  1. Open Command Prompt (select Run from the Start menu, and enter "cmd").
  2. Enter DCOMCNFG and press Enter. Component Services MMC app opens.
  3. Expand Component Services -> Computers -> My Computer -> DCOM Config -> VirtualBox Application.
  4. Right-click VirtualBox Application and select Properties.
  5. Set Authentication Level to None

Update: Afterwards you should re-create your VirtualBox config by moving/deleting the ~/.VirtualBox folder. I had some issues with the GUI which were solved by that.

Update2: Still issues after reboot. I guess another setting was still active.

What does help for my concrete use case is changing the identity of the DCOM object as described here (+ the identity of the Jenkins service). However, this has the drawback that started VMs from the GUI have no window.

Contributor

schlamar commented Oct 17, 2013

I was able to solve various issues with vagrant and DCOM (e.g. running vagrant in a Jenkins job failed with error message above) by disabling DCOM authentication:

  1. Open Command Prompt (select Run from the Start menu, and enter "cmd").
  2. Enter DCOMCNFG and press Enter. Component Services MMC app opens.
  3. Expand Component Services -> Computers -> My Computer -> DCOM Config -> VirtualBox Application.
  4. Right-click VirtualBox Application and select Properties.
  5. Set Authentication Level to None

Update: Afterwards you should re-create your VirtualBox config by moving/deleting the ~/.VirtualBox folder. I had some issues with the GUI which were solved by that.

Update2: Still issues after reboot. I guess another setting was still active.

What does help for my concrete use case is changing the identity of the DCOM object as described here (+ the identity of the Jenkins service). However, this has the drawback that started VMs from the GUI have no window.

@kaoz70

This comment has been minimized.

Show comment
Hide comment
@kaoz70

kaoz70 Oct 30, 2013

I got the error by only using:

config.vm.network :forwarded_port, guest: 80, host: 8080

If I use:

config.vm.network :forwarded_port, guest: 80, host: 4567

I have no errors.

Running Windows 8 x64

kaoz70 commented Oct 30, 2013

I got the error by only using:

config.vm.network :forwarded_port, guest: 80, host: 8080

If I use:

config.vm.network :forwarded_port, guest: 80, host: 4567

I have no errors.

Running Windows 8 x64

@mark-casey

This comment has been minimized.

Show comment
Hide comment
@mark-casey

mark-casey Feb 24, 2014

This more recent ticket (for which a fix will supposedly one day arrive) pretty well mirrors what I'm seeing on my machine and what I'm reading here about vboxsvc.exe not running at certain inopportune moments. Looks like it will be a while but, fingers crossed.

https://www.virtualbox.org/ticket/12509

I never tried the dcom workaround since, so far, I hit this issue very rarely.

This more recent ticket (for which a fix will supposedly one day arrive) pretty well mirrors what I'm seeing on my machine and what I'm reading here about vboxsvc.exe not running at certain inopportune moments. Looks like it will be a while but, fingers crossed.

https://www.virtualbox.org/ticket/12509

I never tried the dcom workaround since, so far, I hit this issue very rarely.

@relipse

This comment has been minimized.

Show comment
Hide comment
@relipse

relipse Feb 28, 2014

I too experienced this right after upgrading to vagrant 1.4.3
I just did "vagrant up" a 2nd time and it worked.

relipse commented Feb 28, 2014

I too experienced this right after upgrading to vagrant 1.4.3
I just did "vagrant up" a 2nd time and it worked.

@Gerarudo Gerarudo referenced this issue in ptwobrussell/Mining-the-Social-Web-2nd-Edition May 25, 2014

Closed

"Vagrant could not detect VirtualBox!" #192

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment