Seems to be related to https://github.com/mitchellh/vagrant/issues/1198. So, yeah. I have this issue as well.

clebio on 8 Jun 2013

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.

mitchellh on 9 Jun 2013

👎16 👍5

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

clebio on 9 Jun 2013

👍67 🎉8 😄8

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.

mitchellh on 9 Jun 2013

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

clebio on 9 Jun 2013

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

mitchellh on 9 Jun 2013

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

clebio on 9 Jun 2013

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

starrychloe on 17 Jun 2013

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

ktacheny on 20 Jun 2013

👍9

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

reinink on 18 Sep 2013

👍8

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

mitchellh on 18 Sep 2013

@mitchellh You rock!

reinink on 18 Sep 2013

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'

tshafer on 21 Sep 2013

Same here as tshafer.
Mac OS X 10.8.5

sergmetelin on 24 Sep 2013

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

adin-ttc on 26 Sep 2013

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.

jperry on 27 Sep 2013

Same problem here, solved by downgrading to 1.3.2

jcalonso on 1 Oct 2013

👍1

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

borantula on 1 Oct 2013

👍9 ❤3 🎉1

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.

parth-j-gandhi on 2 Oct 2013

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.

marlev on 5 Oct 2013

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

leogono on 12 Oct 2013

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

shunwen on 17 Oct 2013

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

shanimal on 19 Oct 2013

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

kanduvisla on 23 Oct 2013

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

nlisgo on 23 Oct 2013

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

yiclwh on 23 Oct 2013

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

iboargun on 23 Oct 2013

Thanks @marlev! Solution worked on OSX Mavericks! :+1:

hugoduraes on 23 Oct 2013

@marlev your tip works great for me but I need to run each time I restart. Is this your experience?

nlisgo on 25 Oct 2013

@marlev also just noticed that I need to run each time I restart. :/

hugoduraes on 25 Oct 2013

@nlisgo @hugoduraes That's seems to be the case for me as well, I had not restarted since i upgraded to Maverick so I wasn't aware.

marlev on 25 Oct 2013

for windows users try running the command as admin
http://www.howtogeek.com/howto/windows-vista/run-a-command-as-administrator-from-the-windows-vista-run-box/

chriscalip on 31 Oct 2013

👍1

sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist

This fixes the problem on MAC Maverricks completeley. Have fun.

Cy4n1d on 4 Nov 2013

👍3

I don't have the "org.virtualbox.startup.plist" file on my Mac

launchctl: Couldn't stat("/Library/LaunchDaemons/org.virtualbox.startup.plist"): No such file or directory
nothing found to load

marlev on 4 Nov 2013

Try to uninstall and reinstall VirtualBox to see if it creates that file.

hugoduraes on 4 Nov 2013

@marlev It seems Virtualbox 4.2 creates /Library/StartupItems/VirtualBox/VirtualBox while 4.3 creates /Library/LaunchDaemons/org.virtualbox.startup.plist

dserodio on 5 Nov 2013

Thanks heaps @marlev your solution worked for me on OSX Mavericks 10.9

majilesh on 5 Nov 2013

@dserodio oes that mean that the command:

sudo launchctl load /Library/StartupItems/VirtualBox/VirtualBox

can be used instead of:

sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist

?

nlisgo on 11 Nov 2013

@nlisgo no, it should be sudo /Library/StartupItems/VirtualBox/VirtualBox restart

dserodio on 11 Nov 2013

@dserodio I'm doing that already but I have to run it each time I restart my machine. I am looking for a way to avoid this. :)

nlisgo on 12 Nov 2013

@ktacheny changing the directory in preferences works for me. Ran into this issue with VirtualBox 4.3.10 and also after downgrading to 4.3.8.

jopann on 29 Apr 2014

I had to reinstall Virtual Box and everything is back to normal. I was screwing around with StartupItems and this may have had something to do with it.

sethen on 1 Jun 2014

Installed V1.6.3 and now all my VMs that previously work with Vagrant up - all fail with the --name error
running Windows 7 64 bit host
Vagrant 1.6.3
VirtualBox V4.3.12r93733 (although it was all working fine until the vagrant upgrade)

Also, when I upgraded, i had to install twice - coz bsdtar did not get installed properly

I am going to re-install vagrant as administrator this time, will let you know if that makes any difference

michaeljquinn on 15 Jun 2014

Installing Vagrant as admin made no difference to the problem - it fails on the rename when running the VBoxManage command
Could not rename the directory 'E:VirtualBoxVMSplay1_play_1402794868406_41496' to 'E:VirtualBoxVMSplay.example.com' to save the settings file (VERR_ALREADY_EXISTS) because it looks like the play.example.com directory is created by vagrant and then when the rename of the tmp VM is attempted, it fails

A customization command failed:

["modifyvm", :id, "--name", "play.example.com"]

The following error was experienced:

VBoxManage, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "ae41da5a-0967-46e8-a828-832156788b44", "--name", "play.example.com"]

Stderr: VBoxManage.exe: error: Could not rename the directory 'E:VirtualBoxVMSplay1_play_1402794868406_41496' to 'E:VirtualBoxVMSplay.example.com' to save the settings file (VERR_ALREADY_EXISTS)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "SaveSettings()" at line 2716 of file VBoxManageModifyVM.cpp

Please fix this customization and try again.

michaeljquinn on 15 Jun 2014

made no diff at all, the puzzling thing is that it all worked fine until i upgraded to Vagrant 1.6.3

A customization command failed:

["modifyvm", :id, "--name", "play.example.com"]

The following error was experienced:

VBoxManage, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "0243fbb5-2100-4fda-b91d-2ce42d957d84", "--name", "play.example.com"]

Stderr: VBoxManage.exe: error: Could not rename the directory 'E:VirtualBoxVMSplay1_play_1402795391184_12112' to 'E:VirtualBoxVMSplay.example.com' to save the settings file (VERR_ALREADY_EXISTS)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "SaveSettings()" at line 2716 of file VBoxManageModifyVM.cpp

Please fix this customization and try again.

michaeljquinn on 15 Jun 2014

Every time I restart my computer I have new issues with Vagrant up.

I get this every time I vagrant up. I am on Mac.

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

Command: ["import", "/Users/pmdg3/.vagrant.d/boxes/puphpet-VAGRANTSLASH-ubuntu1204-x64/1.0/virtualbox/box.ovf", "--vsys", "0", "--vmname", "packer-virtualbox-iso_1403652849870_95571", "--vsys", "0", "--unit", "7", "--disk", "/Users/pmdg3/VirtualBox VMs/packer-virtualbox-iso_1403652849870_95571/packer-virtualbox-iso-disk1.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/pmdg3/.vagrant.d/boxes/puphpet-VAGRANTSLASH-ubuntu1204-x64/1.0/virtualbox/box.ovf...
OK.
0%...10%...20%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Could not create the clone medium '/Users/pmdg3/VirtualBox VMs/packer-virtualbox-iso_1403652849870_95571/packer-virtualbox-iso-disk1.vmdk'.
VBoxManage: error: VMDK: cannot write allocated data block in '/Users/pmdg3/VirtualBox VMs/packer-virtualbox-iso_1403652849870_95571/packer-virtualbox-iso-disk1.vmdk' (VERR_DISK_FULL)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Appliance, interface IAppliance
VBoxManage: error: Context: "int handleImportAppliance(HandlerArg*)" at line 779 of file VBoxManageAppliance.cpp

behnampmdg3 on 25 Jun 2014

@behnampmdg3 Your disk is full: VERR_DISK_FULL

davidkarlsen on 25 Jun 2014

I have 1 gig free. How much does Vagrant need each time?

behnampmdg3 on 26 Jun 2014

@behnampmdg3 that's not a lot... vboxmanage needs enough space to copy the vmdk (which is usually about ~400MB or so, depending on the box) to your VirtualBox VMs folder, and then once the box starts up and everything it can grow larger (for me they tend to get to like ~1.5GB).

drpebcak on 26 Jun 2014

For Mac OS X 10.9.3 and Vagrant 1.6.3 and VirtualBox 4.3.6 this problem was fixed with restarting the VirtualBox
sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart

pazhyn on 1 Jul 2014

👍1

Going back to the original post - on windows at least - I solved the same issue for myself by renaming Virtualbox VM's to VirtaulBoxVMs - it seems that vagrant doesn't like filenames with spaces in them.

EndemolUK on 4 Jul 2014

@EndemolUK Same thing for me trying to boot it up on Win7. Into VirtualBox's preferences and change the default value for the VM folder name.

robpodosek on 14 Aug 2014

Hi all,

I had same issue on Windows 7, Vagrant 1.5.
Solved it by restarting VirtualBox service in service manager.

elzix88 on 23 Sep 2014

I get this issue on Windows 7 with the latest version of vagrant. I fix it by going into the directory where VB stores machines and deleting the folders.

uchagani on 14 Oct 2014

@uchagani is right. If Vagrant cannot rename the box there is a chance that in c:Users[USER]VirtualBox VMs to exist an directory with that name. Just delete it.

If by any change you have deleted all, check and remove that VM from VirtualBox also.

ialbescu on 12 Nov 2014

I have this same issue on Ubuntu.
The only way I've found to be able to access the VM without having to destroy it was to do the following:

in my vagrant file, I was using the following

config.vm.provider :virtualbox do |v|
v.customize ["modifyvm", :id, "--name", "nameofmyvm"]
end

Commenting the v.customize ["modifyvm", :id, "--name", "nameofmyvm"] is what allowed me to boot the machine.

This is in no way a fix however, just a band-aid.

ladydascalie on 9 Apr 2015

Had the same error. I fixed it by resetting the default VM location in Virtual Box. (which I had changed in the past)

Just open the Virtual Box GUI and go to settings.

basepack on 20 May 2015

hi all, I ran into this error when trying to 'vagrant up' a win2012 box that I built on VBox.

Running vagrant 1.7.2 (latest as of 6/25/2015) running on ubuntu 14.04

Bringing machine 'default' up with 'virtualbox' provider...
==> 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: ["modifyvm", "47a2582f-a1e2-49b7-bff8-ebd0a71d9149", "--nic2", "none", "--nic3", "none", "--nic4", "none", "--nic5", "none", "--nic6", "none", "--nic7", "none", "--nic8", "none"]

Stderr: VBoxManage: error: Runtime error opening '/home/mreider/VirtualBox VMs/win2012_default_1435261495327_14037/win2012_default_1435261495327_14037.vbox-tmp' for reading: -102(File not found.).
VBoxManage: error: /build/buildd/virtualbox-4.3.10-dfsg/src/VBox/Main/src-server/MachineImpl.cpp10362
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "SaveSettings()" at line 2716 of file VBoxManageModifyVM.cpp

My resolution was to delete the .box file, rerunning "vagrant package --base xxx --output xxxx.box" and "vagrant box add"

perfecto25 on 25 Jun 2015

my option is restart the vm ,don't kown the reason why ,but it works.
when I stop vagrant use vagrant halt and later run vagrant up ,the error occured!
I sove this problem by:

1.start from virtualbox  , and shutdown it when loged in.
2.vagrant up

nilyang on 26 Jun 2015

👍3

+1 for powering off with VBox. This fixed it for me.

XedinUnknown on 19 Oct 2015

I had a similar issue with a namend instance. Removing the name fixed it for me.

   vb.customize ["modifyvm", :id,
            "--name", "oracle",
            "--memory", "512",
            "--natdnshostresolver1", "on"]

Change to

   vb.customize ["modifyvm", :id,
            "--memory", "512",
            "--natdnshostresolver1", "on"]

OS: Windows 7 64bit
VBox: Version 5.0.8 r103449
Vagrant: Installed Version: 1.7.4
Vagrantfile: https://github.com/hilverd/vagrant-ubuntu-oracle-xe

bahrmichael on 11 Dec 2015

I had this issue and couldn't see the ghost VM until I typed "virtualbox restart" in the CLI, this made it visible in the VirtualBox app so I could delete it. Running on Mac Mountain Lion 10.8.5

Souliloquy on 31 Mar 2016

Had this issue on windows after choosing to ignore all warnings that a VB process is still running. Uninstalling and reinstalling fixed the issue without any more problems.

bertpareyn on 23 May 2016

Solved this issue just upgrading virtualbox from 4 to 5.

andreipaz on 28 May 2016

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'scotch/box' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
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", "dc937c6c-6b0c-45f1-98bc-5d7b0cbfef84", "--type", "headless "]

Stderr: VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU modes (V ERR_VMX_MSR_ALL_VMX_DISABLED)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

I am having this issue with vagrant up on windows 7
Vagrant 1.8.1
VirtualBox-5.0.20-106931-Win

Please , I need help. I am a newbie

St33lMagnolia on 6 Jun 2016

@St33lMagnolia, in your case this is not Vagrant issue. VirtualBox reports that in your hardware disabled VT-x. More about how check availability and possibly enable VT-x you can see here.

rrzaripov on 8 Jun 2016

👍1

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: Setting the name of the VM: homestead-7
==> 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: ["modifyvm", "3edf52a7-f514-4d17-a014-d07afa80047f", "--nic2", "none", "--nic3", "none", "--nic4", "none", "--nic5", "none", "--nic6", "none", "--nic7", "none", "--nic8", "none", "--nic9", "none", "--nic10", "none", "--nic11", "none", "--nic12", "none", "--nic13", "none", "--nic14", "none", "--nic15", "none", "--nic16", "none", "--nic17", "none", "--nic18", "none", "--nic19", "none", "--nic20", "none", "--nic21", "none", "--nic22", "none", "--nic23", "none", "--nic24", "none", "--nic25", "none", "--nic26", "none", "--nic27", "none", "--nic28", "none", "--nic29", "none", "--nic30", "none", "--nic31", "none", "--nic32", "none", "--nic33", "none", "--nic34", "none", "--nic35", "none", "--nic36", "none"]

Stderr: VBoxManage.exe: error: Invalid NIC number 9
VBoxManage.exe: error: Invalid NIC number 10
VBoxManage.exe: error: Invalid NIC number 11
VBoxManage.exe: error: Invalid NIC number 12
VBoxManage.exe: error: Invalid NIC number 13
VBoxManage.exe: error: Invalid NIC number 14
VBoxManage.exe: error: Invalid NIC number 15
VBoxManage.exe: error: Invalid NIC number 16
VBoxManage.exe: error: Invalid NIC number 17
VBoxManage.exe: error: Invalid NIC number 18
VBoxManage.exe: error: Invalid NIC number 19
VBoxManage.exe: error: Invalid NIC number 20
VBoxManage.exe: error: Invalid NIC number 21
VBoxManage.exe: error: Invalid NIC number 22
VBoxManage.exe: error: Invalid NIC number 23
VBoxManage.exe: error: Invalid NIC number 24
VBoxManage.exe: error: Invalid NIC number 25
VBoxManage.exe: error: Invalid NIC number 26
VBoxManage.exe: error: Invalid NIC number 27
VBoxManage.exe: error: Invalid NIC number 28
VBoxManage.exe: error: Invalid NIC number 29
VBoxManage.exe: error: Invalid NIC number 30
VBoxManage.exe: error: Invalid NIC number 31
VBoxManage.exe: error: Invalid NIC number 32
VBoxManage.exe: error: Invalid NIC number 33
VBoxManage.exe: error: Invalid NIC number 34
VBoxManage.exe: error: Invalid NIC number 35
VBoxManage.exe: error: Invalid NIC number 36

How to fix vagrant up problem?
I'm using
*windows 10 64bit
*virtualbox 5.0.21.7994-win
*vagrant 1.8.3
Please, I need help. I'm a newbie.

tusar-nill on 11 Jun 2016

@tusar-nill you can look at this workaround.

yethee on 12 Jun 2016

I was only able to fix this by getting the list of vms, then deleting each one using the following commands:

sudo VBoxManage list vms
sudo VBoxManage unregistervm <vmname> --delete

larskendall on 13 Jun 2016

👍1

@larskendall
Hey, I'm using windows 10 OS. So, Does sudo command works for windows?

tusar-nill on 14 Jun 2016

@tusar-nill sudo won't work on Windows since it's a Unix command (Windows uses DOS). I think in Windows you can right click on the CMD executable and run it as administrator. Then you can run those commands without the sudo bit and they should hopefully work. If that doesn't work, then maybe runas would help. Here's a thread about that particular issue that might help:

http://superuser.com/questions/42537/is-there-any-sudo-command-for-windows

larskendall on 14 Jun 2016

I found a hot fix in my case. I just change the Virtual Box VMs path in the configuration. It was somehow setup to my old username but after I've changed its working nicely.
See pics.
vb vm error

s2925534 on 16 Jun 2016

🎉3

Was getting that error but vagrant reload seems to fix it. I'm on mac El Capitan, Vagrant 1.8.4 and VB 5.0.24

magedmakled on 25 Jul 2016

Thanks s2925534, that solved my problem. Was pulling my hair out for a few minutes there. :)

mrreubenjones on 4 Aug 2016

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

Command: ["startvm", "0bc57779-876b-4756-8253-5990e9447e38", "--type", "headless"]

Stderr: VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

I am using windows 10 and I was enable virtualization but it's not work.
help me please :sob:

aprilpur on 9 Aug 2016

@borantula fix worked for me on OpenSuse Tumbleweed, Thanks.

Mohamed-Saleem on 18 Aug 2016

In my case, this is how I encountered the problem:-

I was using hyper-V with Visual Studio and then forgot to turn it off before starting the vagrant up command. This showed a BSOD (blue screen...) and restarted the computer. I turned off hyper-V and tried to run vagrant up in the same folder as before... Got an error that the index had been corrupted. I went on to delete the index file (pointed to by the error message).

I did vagrant up again and got the dreaded

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

Command: ["showvminfo", "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"]

Stderr:

Then I went ahead and deleted the .vagrant directory in the same folder and that, folks, fixed it for me!!

Oh, and kudos to this comment by @borantula

I hope someone benefits!!

shrmrf on 31 Aug 2016

👍35 🎉9 ❤8

Dear all,
I am a newer in vagrant and virtual box. As i run vagrant up, i got a problem as below:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:Usersa1639371>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
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", "e17b2f74-98c6-45f0-8441-f2fdd326978a", "--type", "headless
"]

Stderr: VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU modes (V
ERR_VMX_MSR_ALL_VMX_DISABLED)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap,
interface IConsole

C:Usersa1639371>

It seems like there is a problem from VBoxManage. Can you please help?

Thank you so much for your time

Regards
Weidong

weidongliangadelaide on 2 Sep 2016

@weidongliangadelaide this is NOT the place to ask this question because it is completely unrelated to this issue. It looks like the issue you are having is that your computer's processor either does not support VT-x, or it is disabled in BIOS. Try googling your actual issue.

PS: If you're running Vagrant on an Adelaide Uni desktop, you should have permissions to BIOS because you're a postgrad student. If you have any problems, just call service desk on 08 8313 3000.

caseyfw on 5 Sep 2016

👍1

I had to set hostname: '' in my puphpet config.yaml to get around this

aphofstede on 5 Sep 2016

What @shrmrf did also worked for me.

GeeWee on 8 Oct 2016

Just removing the .vagrant folder worked for me too, thanks

vmorate on 2 Nov 2016

👍3

reinstalling a newer version of virtualbox fixes it too.

https://www.virtualbox.org/wiki/Downloads

dkw789 on 4 Nov 2016

👍3

I got the same error. Below was the error message:

A customization command failed:

["modifyvm", :id, "--name", "dev.vagrant.local"]

The following error was experienced:

#<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: ["modifyvm", "d1050ee5-6c69-45a9-9842-647c0919db44", "--name", "dev.vagrant.local"]

Stderr: VBoxManage: error: Could not rename the directory '/var/root/VirtualBox VMs/medidatevagrantlocal_medidatevagrantlocal_1485168669703_99607' to '/var/root/VirtualBox VMs/dev.vagrant.local' to save the settings file (VERR_ALREADY_EXISTS)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "SaveSettings()" at line 3052 of file VBoxManageModifyVM.cpp
>

Please fix this customization and try again.

From the error message, it seems kinda clear to me about the error message. I focused on the below line:

Stderr: VBoxManage: error: Could not rename the directory '/var/root/VirtualBox VMs/medidatevagrantlocal_medidatevagrantlocal_1485168669703_99607' to '/var/root/VirtualBox VMs/dev.vagrant.local' to save the settings file (VERR_ALREADY_EXISTS)

It seems like somehow the hostname of my newly created machine got conflicted with one of my old machine's hostname. Thats why it couldn't create the settings file as it already exists from my old machine. Even destroying that existing machine won't solve the problem. So what i did was, gave a new hostname for my new vagrant box and it worked perfectly. :)

williamgomes on 23 Jan 2017

👍1

Stderr: VBoxManage: error: Could not rename the directory '/Users/theo/VirtualBox VMs/airship_machine1_1485426682714_97042' to '/Users/theo/VirtualBox VMs/airship.puphpet' to save the settings file (VERR_ALREADY_EXISTS)

In my case I just deleted the folder /Users/theo/VirtualBox VMs/airship.puphpet. After typing vagrant up vagrant added it back, but this time without the error message.

TheoJL on 26 Jan 2017

👍2

@TheoJL yes thats also helpful. But, as mine got conflicted with an existing one, i had to rename the hostname. :)

williamgomes on 26 Jan 2017

I'm getting a VBoxManage error VERR_PATH_NOT_FOUND:

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Setting the name of the VM: MagicDB_default_1486432349616_2036
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 80 (guest) => 8080 (host) (adapter 1)
    default: 3306 (guest) => 3306 (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", "cf80d5a9-a152-4e1b-b1bd-7009705e960d", "--type", "headless"]

Stderr: VBoxManage.exe: error: Path not found. (VERR_PATH_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Process finished with exit code 1

Any ideas as to what the issue may be?

captainGeech42 on 7 Feb 2017

Make sure VBoxManage.exe is on your path.

On Mon, Feb 6, 2017 at 8:55 PM, Zander Work notifications@github.com
wrote:

I'm getting a VBoxManage error VERR_PATH_NOT_FOUND:

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Setting the name of the VM: MagicDB_default_1486432349616_2036
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 80 (guest) => 8080 (host) (adapter 1)
default: 3306 (guest) => 3306 (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", "cf80d5a9-a152-4e1b-b1bd-7009705e960d", "--type", "headless"]

Stderr: VBoxManage.exe: error: Path not found. (VERR_PATH_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Process finished with exit code 1

Any ideas as to what the issue may be?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mitchellh/vagrant/issues/1809#issuecomment-277877082,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABATkNaC21tyTG52GLHGjT9qJ4LgaUVJks5rZ877gaJpZM4At8Oz
.

uchagani on 7 Feb 2017

@uchagani It is.

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Zander Work>vboxmanage
Oracle VM VirtualBox Command Line Management Interface Version 5.1.4
(C) 2005-2016 Oracle Corporation
All rights reserved.

Usage:

  VBoxManage [<general option>] <command>


General Options:

  [-v|--version]            print version number and exit
  [-q|--nologo]             suppress the logo
  [--settingspw <pw>]       provide the settings password
  [--settingspwfile <file>] provide a file containing the settings password

...

captainGeech42 on 7 Feb 2017

For windows users, run the git bash or the terminal that you're using with admin rights.

erikseulean on 27 Feb 2017

SOLVED! ON WINDOWS

1.first of all destroy the virtual box with vagrant destroy

navigate to C:\Users\Justice replace justice by username

3.delete the .vagrant.d folder

4.go into VirtualBox VMs folder and delete everything inside it.

5.start it again with vagrant up

it should work fine

Adongojustice on 11 Mar 2017

👍11

had to reinstall virtualbox.

amol-c on 28 Mar 2017

👍1

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

rkarthik63 on 4 Jul 2017

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

portal7 on 22 Jul 2017

❤2

Check that the VM is not running on VirtualBox Manager.

mualle on 3 Oct 2017

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

helturkey on 30 Nov 2017

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.

saidiadegoke on 5 Dec 2017

👎1

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

lambasahil on 26 Dec 2017

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

rafaelrozon on 15 Jan 2018

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

ito2307 on 14 Feb 2018

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

tgaertner on 28 Mar 2018

Vagrant Reload fixed the issue vagrant reload

eleijonmarck on 25 Jun 2018

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

samomar on 12 Sep 2018

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:
screen shot 2018-10-02 at 10 00 01 am

turns out I just needed to update the VirtualBox.

dinbrca on 2 Oct 2018

👍12 ❤2

Restarting laptop worked for me

xlcrr on 17 Oct 2018

👍2 😄1

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!!

Elite40 on 15 Nov 2018

Use
vagrant reload

to solve it

hunken on 18 Nov 2018

👍3 🎉1

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.

dvetal on 6 Dec 2018

👍2

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.

Xerotherm1c on 6 Feb 2019

remove saved state on your vbox using:
vagrant halt

then vagrant up again.

ne018 on 24 Apr 2019

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 ??

AFKD98 on 1 Jul 2019

👍3

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

jakelacey2012 on 8 Oct 2019

👍1

I found the solution at below link:

Grant permission to VirtualBox under System Preferences > Security & Privacy > General (this request is new to macOS High Sierra)
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

srikanta72 on 18 Nov 2019

❤1

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

same solution works for OSX as well.

prbhr007 on 28 Nov 2019

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

sengfai on 16 Jan 2020

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.

jggj21 on 24 Jan 2020

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.

hashibot[bot] on 28 Jan 2020

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

Most helpful comment

All 117 comments

VBoxManage, a CLI used by Vagrant

VBoxManage, a CLI used by Vagrant

Running vagrant 1.7.2 (latest as of 6/25/2015) running on ubuntu 14.04

Related issues