Hello again, reinstalling Vagrant didnt give me anything new. Still the same error and I also tried with a new windows 10 iso and the error was the same.
What I wanted to do actually is to have a box where I can access via command line and execute test cases on it. I wouldnt be actually using the box via remote desktop, but I also still dont know if this would be supported with vagrant. I will have a look, when time allows, into packer. Thanks for the tip and for the help! Cheers, Rafael On Friday, August 5, 2016 at 8:33:04 AM UTC+2, Alvaro Miranda Aguilera wrote: > > Hi, try reinstalling Vagrant. > > Vagrant will use the tools that came in the installer, this includes curl > to download boxes and tar/zip to compress/uncompress. > > If this still fails, and time permits, have a look at packer, there is a > provider virtualbox-ovf that allows you start from a existing VM. > For the box already exits a packer template without any provisining will > just connect, and poweroff the box, which is what you are after. > > You may need to prepare the box to enable WinRM or ssh what ever is easier > for you. > > There is a packer mailing list in case you want to give it a try and > follow up. :D > > Alvaro. > > On Thu, Aug 4, 2016 at 11:20 PM, Rafael Werner <[email protected] > <javascript:>> wrote: > >> Hi Alvaro, >> >> Thanks for your reply! >> >> I actually tried your suggestion already and it worked! >> >> My windows VM, which I got the error, was tweaked by me, due to the steps >> proposed on the tutorial I mentioned. So I tried to do the same thing to a >> plain windows 10 vm without me doing any changes. But unfortunately I got >> the same error. >> >> also, both VMs, before boxing them with vagrant, worked properly with >> oracle virtual box. >> >> Maybe I have to try and get another windows 10 virtual box.. maybe the >> one I have has some kind of problem. >> >> Cheers, >> Rafael >> >> On Thursday, August 4, 2016 at 10:04:50 PM UTC+2, Alvaro Miranda Aguilera >> wrote: >>> >>> Hello >>> >>> Try with a different box. >>> >>> test >>> >>> mkdir precise64 >>> cd precise64 >>> vagrant init -m hashicorp/precise64 >>> vagrant up >>> >>> if this works, then the box you are using is corrupted. >>> If this also fails, please provide a more verbose log: >>> >>> for windows: >>> set VAGRANT_LOG=debug >>> >>> for bash/linux/osx: >>> export VAGRANT_LOG=debug >>> >>> then: >>> >>> vagrant up >>> >>> and share the verbose output in a gist (gist.github.com) >>> >>> Thanks >>> Alvaro >>> >>> On Thu, Aug 4, 2016 at 5:42 PM, Rafael Werner <[email protected]> >>> wrote: >>> >>>> Hi everybody, >>>> >>>> I am quite new to vagrant and I started this week trying to set up a >>>> vagrant box with windows inside. I found out a good tutorial, which is on >>>> this website (http://huestones.co.uk/node/305). >>>> >>>> I can do all the steps till "vagrant up" where I get the following >>>> error: >>>> >>>> $ vagrant up >>>> Bringing machine 'default' up with 'virtualbox' provider... >>>> ==> default: Importing base box 'PureWindows'... >>>> 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:/Users/erafwer/.vagrant.d/boxes/PureWindows/0/virtualbox/box.ovf", >>>> "--vsys", "0", "--vmname", "WinTest_1_1470324114907_73717", "--vsys", "0", >>>> "--unit", "8", "--disk", "C:\\Users\\erafwer\\VirtualBox >>>> VMs\\WinTest_1_1470324114907_73717\\box-disk1.vmdk"] >>>> >>>> Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% >>>> Interpreting >>>> C:\Users\erafwer\.vagrant.d\boxes\PureWindows\0\virtualbox\box.ovf... >>>> OK. >>>> 0%... >>>> Progress state: VBOX_E_FILE_ERROR >>>> VBoxManage.exe: error: Appliance import failed >>>> VBoxManage.exe: error: Could not create the imported medium >>>> 'C:\Users\erafwer\VirtualBox >>>> VMs\WinTest_1_1470324114907_73717\box-disk1.vmdk'. >>>> VBoxManage.exe: error: VMDK: Compressed image is corrupted >>>> 'C:\Users\erafwer\.vagrant.d\boxes\PureWindows\0\virtualbox\box-disk1.vmdk' >>>> >>>> (VERR_ZIP_CORRUPTED) >>>> VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), >>>> component ApplianceWrap, interface IAppliance >>>> VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl >>>> handleImportAppliance(struct HandlerArg *)" at line 877 of file >>>> VBoxManageAppliance.cpp >>>> >>>> >>>> I saw a few threads on google with suggestions like: >>>> - remove files from .vagrant.d and start over >>>> - downgrade virtualbox version (I cant do that) >>>> - use the latest version of vagrant >>>> - lack of space on the hard drive >>>> >>>> None of them worked for me. I have a free space of 20 GB and still >>>> didn't work. >>>> >>>> Anyone has any ideas or have experience something like this? >>>> >>>> If you need any more infos I can provide, but basically, everything I >>>> used/did is on that website. >>>> >>>> Thank you in advance. >>>> >>>> Cheers, >>>> Rafael >>>> >>>> -- >>>> This mailing list is governed under the HashiCorp Community Guidelines >>>> - https://www.hashicorp.com/community-guidelines.html. Behavior in >>>> violation of those guidelines may result in your removal from this mailing >>>> list. >>>> >>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues >>>> IRC: #vagrant on Freenode >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Vagrant" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/vagrant-up/87259708-6e47-4fc1-ad78-6b932c49134a%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/vagrant-up/87259708-6e47-4fc1-ad78-6b932c49134a%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Alvaro >>> (+31)103400555 >>> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/5a758d37-ea0d-44df-bf70-44882f2e6809%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/5a758d37-ea0d-44df-bf70-44882f2e6809%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Alvaro > (+31)103400555 > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/1f774f03-d242-481d-b888-ad9a6db6eef3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
