Here is cmd error, I can't understand where is error and I'm bumping on it again and again, can`t solve it.
$ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Preparing master VM for linked clones... default: This is a one time operation. Once the master VM is prepared, default: it will be used as a base for linked clones, making the creation default: of new VMs take milliseconds on a modern system. ==> default: Importing base box 'hashicorp/bionic64'... There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below. Command: ["import", "\\\\?\\C:\\HashiCorp\\boxes\\hashicorp-VAGRANTSLASH-bionic64\\1.0.282\\virtualbox\\box.ovf", "--vsys", "0", "--vmname", "ubuntu-18.04-amd64_1574870798285_57998", "--vsys", "0", "--unit", "11", "--disk", "C:/Users/\u256C\u044B\u0445\u0443/VirtualBox VMs/ubuntu-18.04-amd64_1574870798285_57998/ubuntu-18.04-amd64-disk001.vmdk"] Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% Interpreting \\?\C:\HashiCorp\boxes\hashicorp-VAGRANTSLASH-bionic64\1.0.282\virtualbox\box.ovf... OK. 0%... Progress state: E_INVALIDARG VBoxManage.exe: error: Appliance import failed VBoxManage.exe: error: Code E_INVALIDARG (0x80070057) - One or more arguments are invalid (extended info not available) VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleImportAppliance(struct HandlerArg *)" at line 957 of file VBoxManageAppliance.cpp
I experienced the same issue and solved it by changing VirtualBox's base VM folder:
File -> Preferences
In my case VirtualBox's Default Machine Folder was still pointing to my external hard drive which was no longer connected. Manually importing the Vagrant downloaded .ovf file in VBox via
File -> Import Virtual Appliance lead me to the above solution. Vagrant does the same thing under the hood.
you can check PATH below,if has blank or special character, change it.
Also, free enough space $VAGRANT_HOME and VirtualBox default Virtual Machine location
I got the same issue and stumbled for several hours. Finally, it worked from the following steps.
User contributions licensed under CC BY-SA 3.0