Answers: <p>Try to start with a clean sheet by removing the .vagrant.d folder or start to remove the corrupted zip. When the file or folder has been removed, one could run <code>vagrant up</code> again and check whether it works.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-09-22T22:44:34.093Z
Answers: 2017-09-22T22:44:34.093Z
Answers: 030
Body: <p>I'm Provisioning Vagrant Box with Virtual-box on Fedora 26. </p>
  
  <pre><code>$ vagrant -v
  Vagrant 1.9.1
  $ virtualbox -v
  virtualbox 5.1
  </code></pre>
  
  <p>Below is the error;</p>
  
  <pre><code>muhammadtaqi@localhost etc]$ vagrant up
  Bringing machine 'default' up with 'virtualbox' provider...
  ==&gt; default: Importing base box 'ubuntu/trusty64'...
  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/muhammadtaqi/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-trusty64/20170918.0.1/virtualbox/box.ovf", "--vsys", "0", "--vmname", "ubuntu-cloudimg-trusty-vagrant-amd64_1506105327930_50139", "--vsys", "0", "--unit", "6", "--disk", "/home/muhammadtaqi/VirtualBox VMs/ubuntu-cloudimg-trusty-vagrant-amd64_1506105327930_50139/box-disk1.vmdk"]
  
  Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
  Interpreting /home/muhammadtaqi/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-trusty64/20170918.0.1/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/muhammadtaqi/VirtualBox VMs/ubuntu-cloudimg-trusty-vagrant-amd64_1506105327930_50139/box-disk1.vmdk'.
  VBoxManage: error: VMDK: Compressed image is corrupted '/home/muhammadtaqi/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-trusty64/20170918.0.1/virtualbox/box-disk1.vmdk' (VERR_ZIP_CORRUPTED)
  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
  </code></pre>
  
Comments: CC BY-SA 3.0
Comments: 2017-09-22T19:19:16.617Z
Comments: Did you download this vmdk, or did you create it yourself with virtualbox? Most of the guidance out there states that you have a corrupt vmdk. Others suggest maybe the VMDK was intended for different virtualization software.
Comments: James Shewey
Comments: CC BY-SA 3.0
Comments: 2017-09-22T20:01:12.633Z
Comments: I just installed vagrant, virtualbox, then `vagrant init ubuntu/trusty64; vagrant up` and got the above error.
Comments: Muhammad Taqi
Comments: CC BY-SA 3.0
Comments: 2017-09-22T20:10:53.437Z
Comments: So what's providing the vmdk file? Perhaps that is your issue - are you referencing a file that doesn't exist? Does `ls -alh /home/muhammadtaqi/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-trusty64/20170918.0.1/virtualbox/box-disk1.vmdk` show the file?
Comments: James Shewey
Comments: CC BY-SA 3.0
Comments: 2017-09-22T20:21:12.170Z
Comments: `No such file or directory`
Comments: Muhammad Taqi
Comments: CC BY-SA 3.0
Comments: 2017-09-22T20:41:02.643Z
Comments: Based on that, it sounds like that's the issue: There is no image file for virtualbox to start up. You'll need to get or build one.
Comments: James Shewey
Comments: CC BY-SA 3.0
Comments: 2017-09-22T20:51:09.517Z
Comments: How, I do this before on Ubuntu it works well with just `vagrant init ubuntu/trusty64; vagrant up`, but now on fedora 26 gets error.
Comments: Muhammad Taqi
Tags: <ansible><vagrant><virtualization>
Title: Error Vagrant Provisioning with Virtual Box on Fedora
UserDisplayName: Muhammad Taqi
ThreadText: # Error Vagrant Provisioning with Virtual Box on Fedora
  
  (Asked by: username_0 on 2017-09-22)
  
  I'm Provisioning Vagrant Box with Virtual-box on Fedora 26.
  
  ```
  $ vagrant -v
  Vagrant 1.9.1
  $ virtualbox -v
  virtualbox 5.1
  
  ```
  
  Below is the error;
  
  ```
  username_0@localhost etc]$ vagrant up
  Bringing machine 'default' up with 'virtualbox' provider...
  ==> default: Importing base box 'ubuntu/trusty64'...
  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/username_0/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-trusty64/20170918.0.1/virtualbox/box.ovf", "--vsys", "0", "--vmname", "ubuntu-cloudimg-trusty-vagrant-amd64_1506105327930_50139", "--vsys", "0", "--unit", "6", "--disk", "/home/username_0/VirtualBox VMs/ubuntu-cloudimg-trusty-vagrant-amd64_1506105327930_50139/box-disk1.vmdk"]
  
  Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
  Interpreting /home/username_0/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-trusty64/20170918.0.1/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/username_0/VirtualBox VMs/ubuntu-cloudimg-trusty-vagrant-amd64_1506105327930_50139/box-disk1.vmdk'.
  VBoxManage: error: VMDK: Compressed image is corrupted '/home/username_0/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-trusty64/20170918.0.1/virtualbox/box-disk1.vmdk' (VERR_ZIP_CORRUPTED)
  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
  
  ```
  
  **Tags:** ansible, vagrant, virtualization
  
  > **Comments:**
  > **username_1**: Did you download this vmdk, or did you create it yourself with virtualbox? Most of the guidance out there states that you have a corrupt vmdk. Others suggest maybe the VMDK was intended for different virtualization software.  
  > **username_0**: I just installed vagrant, virtualbox, then `vagrant init ubuntu/trusty64; vagrant up` and got the above error.  
  > **username_1**: So what's providing the vmdk file? Perhaps that is your issue - are you referencing a file that doesn't exist? Does `ls -alh /home/username_0/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-trusty64/20170918.0.1/virtualbox/box-disk1.vmdk` show the file?  
  > **username_0**: `No such file or directory`  
  > **username_1**: Based on that, it sounds like that's the issue: There is no image file for virtualbox to start up. You'll need to get or build one.  
  > **username_0**: How, I do this before on Ubuntu it works well with just `vagrant init ubuntu/trusty64; vagrant up`, but now on fedora 26 gets error.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2017-09-22. Score: 1
  
  Try to start with a clean sheet by removing the .vagrant.d folder or start to remove the corrupted zip. When the file or folder has been removed, one could run `vagrant up` again and check whether it works.
  
  
  ---
  
  