Vagrant up: There was an error while executing VBoxManage, a CLI used by Vagrant

[starrychloe]

$ /cygdrive/c/Program\ Files/Oracle/VirtualBox/VBoxManage.exe list vms
"AIDC_1367972500" {16d4bcdc-a907-42eb-962f-faef2c68f13c}
"Ubuntu Box" {83f7549d-0ef3-453c-a014-77732d7ba775}


$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Setting the name of the VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "16d4bcdc-a907-42eb-962f-faef2c68f13c", "--name", "AIDC_1370628358"]

Stderr: VBoxManage.exe: error: Could not rename the directory 'C:\Users\Chloe\VirtualBox VMs\AIDC_1367972500' to 'C:\Users\Chloe\VirtualBox VMs\AIDC_1370628358' to save the settings file (VERR_ACCESS_DENIED)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "SaveSettings()" at line 2527 of file VBoxManageModifyVM.cpp

However, I am able to start the VM directly from Oracle VirtualBox manager GUI, and I am able to log in with root/vagrant.

[clebio]

Seems to be related to #1198. So, yeah. I have this issue as well.

[mitchellh]

Dup of #1198.

At its root this appears to be an issue with what permissions Vagrant is run with. I'd love for Vagrant to better detect when this error might appear. But at the moment I'm unsure what exactly causes it, mostly because of my ignorance about Windows permissions/ACL.

As the error message says, the problem is that VirtualBox can't rename the directory due to an access denied. I would check permissions on the VirtualBox VMs directory.

[clebio]

@mitchellh I'm not sure why you would consider this closed. It's clearly verified by multiple users. VirtualBox can't rename the directory... ok... why is it trying to? Does VirtualBox, under normal operation, rename directories? Not understanding the cause isn't really a fair reason to ignore the issue. This has made Vagrant very unreliable for me -- I never know when I go to bring up the Vagrant box whether I'll be able to start on my work right away, or will have to spend a few hours debugging a known issue.

[mitchellh]

I'm sorry. I need a clear reproduction case that I can mirror. Until then, I can't fix the bug. Unfortunately this is one of the pros and cons of open source. For platforms that I'd like to support, but don't use on a daily basis, I depend on the community to debug and fix issues for these.

I admit this is a bug, and I'd be happy to fix it, but I require a clear reproduction case that I can do. If I can't get that, I'd love for a patch or pull request to fix it for you.

[clebio]

@mitchellh I did my best! Hope that is enough to get started. I absolutely understand your point about FOSS. Vagrant is a great tool, so I very much want to help it along.

[mitchellh]

@clebio It looks fantastic. I'm going to give it a shot with my Windows machine shortly. Thanks so much.

[clebio]

Just glad to help. Let me know if you need more details, etc. Thanks!

[starrychloe]

I agree with @clebio . Why does Vagrant need to keep renaming the virtual box to a random name like AIDC_1367972500 every time?

[ktacheny]

I was able to get around this error by going into virtual box preferences and changing the vm directory to c:\1\vagrant\vm

[reinink]

I'm running Vagrant on OSX Mountain Lion and keep getting this error as well. Typically a vagrant reload solves it.

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

Command: ["guestproperty", "get", "2bdb0360-5d44-40c8-9869-749d396b0caf", "/VirtualBox/GuestAdd/Version"]

Stderr: dyld: Symbol not found: _iconv
  Referenced from: /usr/lib/libcups.2.dylib
  Expected in: /Applications/Vagrant/bin/../embedded/lib/libiconv.dylib in /usr/lib/libcups.2.dylib

[mitchellh]

@reinink This was hot-fixed in 1.3.2 last night. Please redownload 1.3.2 and try again.

[reinink]

@mitchellh You rock!

[tshafer]

I am getting this error as well

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

Command: ["hostonlyif", "ipconfig", "dyld: DYLD_ environment variables being ignored because main executable (/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdp", "--ip", "192.168.3.1", "--netmask", "255.255.255.0"]

Stderr: VBoxManage: error: The host network interface with the given name could not be found
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component Host, interface IHost, callee nsISupports
VBoxManage: error: Context: "FindHostNetworkInterfaceByName(name.raw(), hif.asOutParam())" at line 220 of file VBoxManageHostonly.cpp
VBoxManage: error: Could not find interface 'dyld: DYLD_ environment variables being ignored because main executable (/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdp'

[sergmetelin]

Same here as tshafer.
Mac OS X 10.8.5

[adin-ttc]

same issue here v1.3.3 with OSX 10.8.5 not sure if this its OSX though. I downgraded to 1.3.2 and everything seems to be fine

[jperry]

I get the same as well for 10.8.5 using 1.3.3, downgrading to 1.3.2 fixed it for me as well.

[jcalonso]

Same problem here, solved by downgrading to 1.3.2

[borantula]

After getting the error I run the vagrant from VirtualBox itself. On login screen I closed and shut it down.
Then I did a "vagrant up"
It seems to work for me on 1.3.3

[parth-j-gandhi]

I get this error on Windows 7 with vagrant version 1.3.3 when I run "vagrant up" in a multi-machine environment.
Ideal behavior should be to bring up all the boxes but I get this error after the first box is up and vagrant is in the process of bringing the second one up from the same base box.

[marlev]

Got the same error after upgraded to OSX 10.9 Maverick GM.
Tried all above but nothing worked.

The solution was to run $sudo /Library/StartupItems/VirtualBox/VirtualBox restart (as found at http://stackoverflow.com/questions/14404777/vagrant-hostonlyif-create-not-working)
After that vagrant up works.

[leogono]

I followed the workaround provided by @borantula and it works!

[shunwen]

@borantula 's workaround works on OSX 1.8.5, Thanks!

[shanimal]

Not sure if this helps, but I had VirtualBox.app settings open when i shut down and I got this error. I tried to restart and the error repeated. I only closed the settings dialog and it restarted... phew. Thanks to @borantula for pointing me in the right direction. Vagrant version 1.2.3

[kanduvisla]

Thanks, marlevs' solution worked for me on OSX Mavericks 10.9

[nlisgo]

@marlev thanks a lot for the tip. Got me up and running again!

[yiclwh]

Thanks, marlevs' solution worked for me on OSX Mavericks 10.9 too

[iboargun]

Thanks, @marlev! Worked for me on OSX Mavericks too! ;)

[rkarthik63]

I was missing libcurl3 package. Installed libcurl3 and re-installed virtual box to fix the issue

[portal7]

I solved killing process "VBoxHeadless" in Task Manager (Windows 10), running "vagrant up" and works like a charm!!

[mualle]

Check that the VM is not running on VirtualBox Manager.

[helturkey]

@Adongojustice thank u very much, your response solved my problem.

[saidiadegoke]

I had the same issue of "There was an error while executing VBoxManage, a CLI used by Vagrant ..." on my Windows 10 machine. I got that fixed by running the CLI window as an 'administrator' and running vagrant up again.

[lambasahil]

Can anyone help?

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 8080 (guest) => 8001 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "320c29c0-32f1-4134-9f39-1340f5aebaac", "--type", "headless
"]

Stderr: VBoxManage.exe: error: The virtual machine 'Catalogue_default_1506252938
237_96481' has terminated unexpectedly during startup with exit code 1 (0x1).  M
ore details may be available in 'C:\Users\sahil\VirtualBox VMs\Catalogue_default
_1506252938237_96481\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap,
 interface IMachine

[rafaelrozon]

@lambasahil I had the same problem. I fixed it by updating Virtualbox to 5.2.4.

[ito2307]

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

Command: ["import", "/home/eduardoh/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-xenial64/20180213.2.0/virtualbox/box.ovf", "--vsys", "0", "--vmname", "ubuntu-xenial-16.04-cloudimg-20180213_1518618539483_25179", "--vsys", "0", "--unit", "10", "--disk", "/home/eduardoh/VirtualBox VMs/ubuntu-xenial-16.04-cloudimg-20180213_1518618539483_25179/ubuntu-xenial-16.04-cloudimg.vmdk", "--vsys", "0", "--unit", "11", "--disk", "/home/eduardoh/VirtualBox VMs/ubuntu-xenial-16.04-cloudimg-20180213_1518618539483_25179/ubuntu-xenial-16.04-cloudimg-configdrive.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/eduardoh/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-xenial64/20180213.2.0/virtualbox/box.ovf...
OK.
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Could not create the imported medium '/home/eduardoh/VirtualBox VMs/ubuntu-xenial-16.04-cloudimg-20180213_1518618539483_25179/ubuntu-xenial-16.04-cloudimg.vmdk' (VERR_VD_VMDK_INVALID_FORMAT)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 886 of file VBoxManageAppliance.cpp

i got this error

[tgaertner]

Make sure you have installed the VirtualBox-ExtensionPack
Debian/Ubuntu: sudo apt-get install virtualbox-ext-pack

[eleijonmarck]

Vagrant Reload fixed the issue vagrant reload

[samomar]

This thread is gold, I don't know what exactly worked for me but this thread along side this link helped https://stackoverflow.com/questions/50053255/virtualbox-raw-mode-is-unavailable-courtesy-of-hyper-v-windows-10

[dinbrca]

Had it on Mac after updating to Mac OS Mojave with following error:

==> default: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp

After a couple of minutes I tried loading VirtualBox directly instead of using Vagrant throught the CLI - I got the following message:

turns out I just needed to update the VirtualBox.

[xlcrr]

Restarting laptop worked for me

[osmanskaya]

You have to check if you've the newest version of Virtualbox, because the version might not be compatible with the new Mac OS Mojave. As @dinbrca suggested above, i updated the virtualbox and it worked again!!

[hunken]

Use
vagrant reload

to solve it

[dvetal]

vagrant reload did not work for me. When I updated to mohave i had to basically download the latest vagrant and the latest VirtualBox. Then it worked.

[Xerotherm1c]

I too received this error, but it was not because of permissions like I had presumed. I'm using vagrant box with Laravel and I attempted to create a new symbolic link for storage using the artisan command. But that command failed, and upon Googling I found that you need to have administrative permissions when launching vagrant to be able to create symbolic links. No sweat, so I closed Git CMD and reopened it as an administrator. I then ran vagrant halt followed by vagrant up, but I didn't realize that the halt didn't actually shut down the vagrant box because the elevated instance seems to not be able to talk to the vagrant box that the non-elevated instance spawned? Not entirely sure, but once I halted the box from non-admin and restarted the vagrant box inside the elevated instance, my problem was solved and everything is back to normal. Hopefully this helps someone.

[ne018]

remove saved state on your vbox using:
vagrant halt

then vagrant up again.

[AFKD98]

I am facing the same issue on Ubuntu 16.04. I tried everything above. I am using latest versions.
virtualbox version 6.0.8
vagrant version 2.2.5
I think I need to downgrade my versions ?
Help ??

[jakelacey2012]

I also had this error because "Oracle America, inc", was blocked from installing software on my mac. This can be fixed by following this https://matthewpalmer.net/blog/2017/12/10/install-virtualbox-mac-high-sierra/index.html

[srikanta72]

I found the solution at below link:

1. Grant permission to VirtualBox under System Preferences > Security & Privacy > General (this request is new to macOS High Sierra)
2. Open Terminal and run: sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart
   Like the guy who answered in below link:
   https://stackoverflow.com/questions/18149546/vagrant-up-failed-dev-vboxnetctl-no-such-file-or-directory

[prbhr007]

I was able to get around this error by going into virtual box preferences and changing the vm directory to c:\1\vagrant\vm

same solution works for OSX as well.

[sengfai]

Go to virtualbox and remove and delete it manually, then run "vagrant up again".

[jggj21]

I opened Virtual Box and when I started the machine from there I showed an error that I had virtualization disabled in the BIOS, I enabled the option from the bios and vagrant up it worked again.

[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.