vagrant up import issue

Created on 13 Oct 2012  ยท  29Comments  ยท  Source: hashicorp/vagrant

On "vagrant up" an import error occurs, details below thanks.

System: OS X 10.7
Vagrant: 1.0.5
VirtualBox: 4.2.1 r80871

INFO global: Vagrant version: 1.0.5
INFO vagrant: vagrant invoked: ["up"]
INFO environment: Environment initialized (#Vagrant::Environment:0x0000010116b078)
INFO environment: - cwd: /Users/kurtcampher/Projects/vagrant/lucid_box
INFO environment: Home path: /Users/kurtcampher/.vagrant.d
INFO plugin: Searching and loading any available plugins...
INFO plugin: Loaded 0 plugins.
INFO environment: Loading configuration...
INFO cli: CLI: [] "up" []
INFO datastore: Created: /Users/kurtcampher/Projects/vagrant/lucid_box/.vagrant
INFO virtualbox_base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["VBoxManage", "--version"]
INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
INFO virtualbox_base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["VBoxManage", "showvminfo", "1c838864-3bba-4ca9-a4d9-a45c0327686d"]
INFO virtualbox_base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["VBoxManage", "--version"]
INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
INFO virtualbox_base: VBoxManage path: VBoxManage
INFO vm: Loading guest: linux
INFO up: Creating: default
INFO hosts: Host class: Vagrant::Hosts::BSD
INFO runner: Running action: up
INFO warden: Calling action: #Vagrant::Action::General::CheckVirtualbox:0x000001010a7088
INFO subprocess: Starting process: ["VBoxManage", "list", "hostonlyifs"]
INFO warden: Calling action: #Vagrant::Action::General::Validate:0x000001010a7060
INFO warden: Calling action: #Vagrant::Action::VM::CheckAccessible:0x000001010a7010
INFO warden: Calling action: #Vagrant::Action::VM::CheckBox:0x000001010a6fe8
INFO warden: Calling action: #Vagrant::Action::VM::Import:0x000001010a6fc0
INFO interface: info: Importing base box 'lucid_guest_adds'...
[default] Importing base box 'lucid_guest_adds'...
INFO subprocess: Starting process: ["VBoxManage", "import", "/Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf"]
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
INFO warden: Calling recover: #Vagrant::Action::VM::Import:0x000001010a6fc0
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #

["import", "/Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.>
ERROR vagrant: There was an error executing the following command with VBoxManage:

["import", "/Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR vagrant: /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/driver/virtualbox_base.rb:278:in block in execute' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/util/retryable.rb:14:inretryable'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/driver/virtualbox_base.rb:268:in execute' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/driver/virtualbox_4_2.rb:183:inimport'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/vm/import.rb:14:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/warden.rb:33:incall'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/vm/check_box.rb:28:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/warden.rb:33:incall'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/vm/check_accessible.rb:18:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/warden.rb:33:incall'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/general/validate.rb:13:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/warden.rb:33:incall'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/general/check_virtualbox.rb:23:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/warden.rb:33:incall'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/builder.rb:92:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/runner.rb:49:inblock in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/util/busy.rb:19:in busy' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/action/runner.rb:49:inrun'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/vm.rb:192:in run_action' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/vm.rb:145:inup'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/command/up.rb:31:in block in execute' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/command/base.rb:116:inblock in with_target_vms'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/command/base.rb:111:in each' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/command/base.rb:111:inwith_target_vms'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/command/up.rb:24:in execute' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/cli.rb:42:inexecute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/lib/vagrant/environment.rb:167:in cli' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.5/bin/vagrant:43:in /Applications/Vagrant/bin/../embedded/gems/bin/vagrant:19:in load' /Applications/Vagrant/bin/../embedded/gems/bin/vagrant:19:in

'
INFO interface: error: There was an error executing the following command with VBoxManage:

["import", "/Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
There was an error executing the following command with VBoxManage:

["import", "/Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.

All 29 comments

Can you try this command directly and see what happens:

VBoxManage import /Users/kurtcampher/.vagrant.d/boxes/lucid_guest_adds/box.ovf

hey, thanks for the response.

Tried your suggestion and got this:

0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance read failed
VBoxManage: error: Could not read OVF file 'box.ovf' (VERR_ACCESS_DENIED)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Appliance, interface IAppliance
VBoxManage: error: Context: "int handleImportAppliance(HandlerArg*)" at line 306 of file VBoxManageAppliance.cpp

hi everyone,
i am getting the same error when i am trying to use bills-kitchen which uses vagrant

There was an error executing the following command with VBoxManage:
["import", "W:/home/.vagrant.d/boxes/ubuntu-12.04-server-amd64-bare-os/box.ovf"]

W:\repo\my-chef-repo>VBoxManage import W:/home/.vagrant.d/boxes/ubuntu-12.04-server-amd64-bare-os/box.ovf
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

Interpreting W:\home.vagrant.d\boxes\ubuntu-12.04-server-amd64-bare-os\box.ovf...
OK.
Disks: vmdisk1 10632560640 -1 http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized box-disk1.vmdk -1 -1
Virtual system 0:
..........................................
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage.exe: error: Could not create the clone medium 'W:\home\VirtualBox VMs\ubuntu-12.04-server-amd64\box-disk1.vmdk'.
VBoxManage.exe: error: VMDK: Compressed image is corrupted 'W:\home.vagrant.d\boxes\ubuntu-12.04-server-amd64-bare-os\box-disk1.vmdk' (VERR_ZIP_CORRUPTED)
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Appliance, interface IAppliance, callee
Context: "ImportAppliance" at line 793 of file VBoxManageAppliance.cpp

I'm getting the same error as @campherkurt

I'm having the same error as @campherkurt as well, details below;

OS: Mac OS X 10.8.2 (12C3006)
VirtualBox Version: 4.2.6
Vagrant version: 1.0.6

Vagrantfile:

Vagrant::Config.run do |config|

        ## The Box
        config.vm.box = "precise64"
        config.vm.box_url = "http://files.vagrantup.com/precise64.box"

end

ran sudo vagrant up

[default] Box precise64 was not found. Fetching box from specified URL...
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
[default] Importing base box 'precise64'...
[default] The guest additions on this VM do not match the install version of
VirtualBox! This may cause things such as forwarded ports, shared
folders, and more to not work properly. If any of those things fail on
this machine, please update the guest additions and repackage the
box.

Guest Additions Version: 4.2.0
VirtualBox Version: 4.2.6
[default] Matching MAC address for NAT networking...
[default] Clearing any previously set forwarded ports...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Mounting shared folders...
[default] -- v-root: /vagrant

ran vagrant status

Current VM states:

default not created

The environment has not yet been created. Run vagrant up to
create the environment.

ran VAGRANT_LOG=INFO vagrant up

INFO global: Vagrant version: 1.0.6
INFO vagrant: vagrant invoked: ["up"]
INFO environment: Environment initialized (#Vagrant::Environment:0x000001021101b8)
INFO environment: - cwd: /Users/sjugge/Workspace/Vagrantboxes/precise64naked
INFO environment: Home path: /Users/sjugge/.vagrant.d
INFO plugin: Searching and loading any available plugins...
INFO plugin: Loaded 0 plugins.
INFO environment: Loading configuration...
INFO cli: CLI: [] "up" []
INFO datastore: Created: /Users/sjugge/Workspace/Vagrantboxes/precise64naked/.vagrant
INFO virtualbox_base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["VBoxManage", "--version"]
INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
INFO virtualbox_base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["VBoxManage", "showvminfo", "bc50834a-631e-4654-95c1-5dc7eb9327a4"]
INFO virtualbox_base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["VBoxManage", "--version"]
INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
INFO virtualbox_base: VBoxManage path: VBoxManage
INFO vm: Loading guest: linux
INFO up: Creating: default
INFO hosts: Host class: Vagrant::Hosts::BSD
INFO runner: Running action: up
INFO warden: Calling action: #Vagrant::Action::General::CheckVirtualbox:0x00000102014778
INFO subprocess: Starting process: ["VBoxManage", "list", "hostonlyifs"]
INFO warden: Calling action: #Vagrant::Action::General::Validate:0x00000102014750
INFO warden: Calling action: #Vagrant::Action::VM::CheckAccessible:0x00000102014728
INFO warden: Calling action: #Vagrant::Action::VM::CheckBox:0x00000102014700
INFO warden: Calling action: #Vagrant::Action::VM::Import:0x000001020146d8
INFO interface: info: Importing base box 'precise64'...
[default] Importing base box 'precise64'...
INFO subprocess: Starting process: ["VBoxManage", "import", "/Users/sjugge/.vagrant.d/boxes/precise64/box.ovf"]
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/Users/sjugge/.vagrant.d/boxes/precise64/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
INFO warden: Calling recover: #Vagrant::Action::VM::Import:0x000001020146d8
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/Users/sjugge/.vagrant.d/boxes/precise64/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/Users/sjugge/.vagrant.d/boxes/precise64/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/Users/sjugge/.vagrant.d/boxes/precise64/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/Users/sjugge/.vagrant.d/boxes/precise64/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #

["import", "/Users/sjugge/.vagrant.d/boxes/precise64/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.>
ERROR vagrant: There was an error executing the following command with VBoxManage:

["import", "/Users/sjugge/.vagrant.d/boxes/precise64/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR vagrant: /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/driver/virtualbox_base.rb:278:in block in execute' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/util/retryable.rb:14:inretryable'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/driver/virtualbox_base.rb:268:in execute' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/driver/virtualbox_4_2.rb:183:inimport'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/vm/import.rb:14:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:incall'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/vm/check_box.rb:28:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:incall'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/vm/check_accessible.rb:18:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:incall'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/general/validate.rb:13:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:incall'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:incall'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in call' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:inblock in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in busy' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:inrun'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/vm.rb:192:in run_action' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/vm.rb:145:inup'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/command/up.rb:31:in block in execute' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/command/base.rb:116:inblock in with_target_vms'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/command/base.rb:111:in each' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/command/base.rb:111:inwith_target_vms'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/command/up.rb:24:in execute' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:inexecute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in cli' /Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/bin/vagrant:43:in /Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in load' /Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in

'
INFO interface: error: There was an error executing the following command with VBoxManage:

["import", "/Users/sjugge/.vagrant.d/boxes/precise64/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
There was an error executing the following command with VBoxManage:

["import", "/Users/sjugge/.vagrant.d/boxes/precise64/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.

I had a similar issue but the problem was that I downloaded the box as root. 'chown' ing it to my user fixed the problem.

@gmanricks you may be on to something. I used to sudo vagrant up a lot so to avoid the sudo rights prompt for the NFS...

In the meanwhile I have re-installed my Mac since there was some software installed for client work that I didn't trust too much, have been using vagrant up like a good lad and haven't had any issues as described above.

I am also seeing the same error as @campherkurt and the others. Using Vagrant via Cygwin/Mintty on Windows 7 64-bit.

In my case, I had a previous VM already running in Virtualbox. I then started my Vagrant box. After I ran vagrant halt then vagrant destroy, I noticed the precise64 base box was still listed in Virtualbox. I right-clicked and removed it, but not the underlying files. That's when I started seeing the error. I checked the permissions on the .vagrant.d/boxes folder and it's descendents after finding this issue. Unlike @gmanricks, I didn't notice anything abnormal. I halted the original VM and closed the Virtualbox GUI, then tried vagrant up again. Now it's working again -- go figure.

Getting the same issue on Ubuntu 12.10 32-bit, VirtualBox 4.2.6, Vagrant 1.0.6. Both with a box I packaged myself (which works on my work machine, as well as a co-worker's OS X machine), and with the fresh "precise64" box from Vagrant itself.

Ah, the issue is the sudo which sets up incorrect permissions on the folders that Vagrant uses to add boxes. I'm going to add checks in for this to prevent this from happening.

@mitchellh Hm, when I just run VBoxManage import ~/path/to/box.ovf I get the following:

https://gist.github.com/9b9875845c002a1f0dac

What should permissions _be_? I own the folders and all subfolders, and permissions on the ~/VirtualBox VMs/precise64_1358961920/ are 700

@mattdeboard That error looks like your box was corrupted or invalid. VirtualBox doesn't understand the format.

Hm I even get this error on fresh boxes, e.g. vagrant box add precise64 http://files.vagrantup.com/precise64.box... wonder if I'm having a network issue. Do you have the checksums for the boxes you host?

Yeah, I definitely need to add checksumming into the boxes. :)

I've got the same issue.

$ VAGRANT_LOG=INFO vagrant up
INFO global: Vagrant version: 1.0.6
INFO vagrant: vagrant invoked: ["up"]
INFO environment: Environment initialized (#Vagrant::Environment:0x7f523147a358)
INFO environment: - cwd: /home/xuser/vagrant/farfadev
INFO environment: Home path: /home/xuser/.vagrant.d
INFO plugin: Searching and loading any available plugins...
INFO plugin: Loaded 0 plugins.
INFO environment: Loading configuration...
INFO cli: CLI: [] "up" []
INFO datastore: Created: /home/xuser/vagrant/farfadev/.vagrant
INFO virtualbox_base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["VBoxManage", "--version"]
INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_1
INFO virtualbox_base: VBoxManage path: VBoxManage
INFO vm: Loading guest: linux
INFO up: Creating: default
INFO hosts: Host class: Vagrant::Hosts::Linux
INFO runner: Running action: up
INFO warden: Calling action: #Vagrant::Action::General::CheckVirtualbox:0x7f5232e3d0d8
INFO subprocess: Starting process: ["VBoxManage", "list", "hostonlyifs"]
INFO warden: Calling action: #Vagrant::Action::General::Validate:0x7f5232e3d088
INFO warden: Calling action: #Vagrant::Action::VM::CheckAccessible:0x7f5232e3d038
INFO warden: Calling action: #Vagrant::Action::VM::CheckBox:0x7f5232e3cfe8
INFO warden: Calling action: #Vagrant::Action::VM::Import:0x7f5232e3cf98
INFO interface: info: Importing base box 'ubuntu-cloud'...
[default] Importing base box 'ubuntu-cloud'...
INFO subprocess: Starting process: ["VBoxManage", "import", "/home/xuser/.vagrant.d/boxes/ubuntu-cloud/box.ovf"]
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/home/xuser/.vagrant.d/boxes/ubuntu-cloud/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
INFO warden: Calling recover: #Vagrant::Action::VM::Import:0x7f5232e3cf98
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/home/xuser/.vagrant.d/boxes/ubuntu-cloud/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/home/xuser/.vagrant.d/boxes/ubuntu-cloud/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/home/xuser/.vagrant.d/boxes/ubuntu-cloud/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR warden: Error occurred: There was an error executing the following command with VBoxManage:

["import", "/home/xuser/.vagrant.d/boxes/ubuntu-cloud/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #

["import", "/home/xuser/.vagrant.d/boxes/ubuntu-cloud/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.>
ERROR vagrant: There was an error executing the following command with VBoxManage:

["import", "/home/xuser/.vagrant.d/boxes/ubuntu-cloud/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
ERROR vagrant: /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/driver/virtualbox_base.rb:278:in execute' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/util/retryable.rb:14:inretryable'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/driver/virtualbox_base.rb:268:in execute' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/driver/virtualbox_4_1.rb:160:inimport'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/vm/import.rb:14:in call' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:incall'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/vm/check_box.rb:28:in call' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:incall'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/vm/check_accessible.rb:18:in call' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:incall'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/general/validate.rb:13:in call' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:incall'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in call' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:incall'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in call' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:inrun'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in busy' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:inrun'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/vm.rb:192:in run_action' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/vm.rb:145:inup'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/command/up.rb:31:in execute' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/command/base.rb:116:inwith_target_vms'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/command/base.rb:111:in each' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/command/base.rb:111:inwith_target_vms'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/command/up.rb:24:in execute' /var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:inexecute'
/var/lib/gems/1.8/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in cli' /var/lib/gems/1.8/gems/vagrant-1.0.6/bin/vagrant:43 /usr/local/bin/vagrant:23:inload'
/usr/local/bin/vagrant:23
INFO interface: error: There was an error executing the following command with VBoxManage:

["import", "/home/xuser/.vagrant.d/boxes/ubuntu-cloud/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.
There was an error executing the following command with VBoxManage:

["import", "/home/xuser/.vagrant.d/boxes/ubuntu-cloud/box.ovf"]

For more information on the failure, enable detailed logging with
VAGRANT_LOG.

@sychedelix For me the issue was a corrupted download.

Finally got it working. It was the sudo issue!!!!!!

thanks @sjugge

thanks @mitchellh helped me.

@mattdeboard For me it was because of a XFS file system problem...

For me it was simply that my disk was full!

doing sudo vagrant up was working but the vm didn't work right.

For me, I had installed VirtualBox with one user on the system, then switched to another user (long story). So it was trying to create the VM in /Users/cameron/VirtualBox VMs instead of /Users/camd/VirtualBox VMs where it should.

The fix was to launch VirtualBox in the OS X ui. Go to preferences then the general tab and change Default Machine Folder to /Users/camd/VirtualBox VMs

run through the same issue, the cause is there wasn't enough disk space left.
Vagrant version 1.0.6 - VirtualBox version: 4.2.12 - Linux Fedora 18 - 3.8.7-201.fc18.x86_64

There is a separate issue for checksumming and in a recently release I added VBoxManage error output when an error occurs which makes it much nicer to know what went wrong. Because of these changes, I'm going to close this issue.

I started having this issue recently, in VirtualBox 4.3.6 on OS/X. Docker had a file read error in the the middle of download and the VM corrupted. I could not use boot2docker to delete the VM, getting the above error. I ended up manually deleting all VM files and restarting.

I have solved the issue! sudo chmod 777 !!

Sorry to bother you guys again, but I'm having this problem now. And I really don't know if its a vagrant problem or virtualbox problem. I was having an access denied problem, but a chmod 777 in the .vagrant.d directory solved the problem. Now I'm having the corrupted file problem.
Could not create the clone medium '/home/eduardo/VirtualBoxVMs/settler_default_1400246833526_15327/box-disk1.vmdk'.
and
VMDK: Compressed image is corrupted '/home/eduardo/.vagrant.d/boxes/laravel-VAGRANTSLASH-homestead/0.1.6/virtualbox/box-disk1.vmdk' (VERR_ZIP_CORRUPTED).
I don't know what it can be, I just downloaded vbox and vagrant direct from the respectives sites. Really odd to see a corrupt file there. Im trying to install homestead to use in laravel projects. It happens when I try to run vagrant up or when I try to do it manually importing the appliance on Virtual Box. It runs the box.ovf file with no problems, but it fails when it try to access the box-disk1.vmdk file.

@camd had same issue, thank you!!

For anyone who finds this thread on google, and is using windows, I found that if I set the "Default Machine Folder" in VirtualBox to another drive, it would return VERR_PATH_NOT_FOUND. The solution was to create a directory in the drive and point to that.

Note: this is when running Vagrant in-elevated.

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.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Cbeck527 picture Cbeck527  ยท  3Comments

hesco picture hesco  ยท  3Comments

rhencke picture rhencke  ยท  3Comments

luispabon picture luispabon  ยท  3Comments

DreadPirateShawn picture DreadPirateShawn  ยท  3Comments