search

g7 / sailfishx-patcher-f5321

Patcher script that applies the f5321 (Xperia X Compact) compatibility layer on top of official Sailfish X f5121 images
29 stars 5 forks source link

Error after command "vagrant up" #6

Closed Kabouik closed 5 years ago

Kabouik commented 5 years ago

I am following the how-to and everything seemed to go well until this:

mathieu@solus-desktop ~/.config/sailfishx-patcher-f5321 $ vagrant up
[...]
sailfish_image_patcher: Progress: 99% (Rate: 1347k/s, Estimated time remaini    sailfish_image_patcher: Progress: 99% (Rate: 1258k/s, Estimated time remaini==> sailfish_image_patcher: Successfully added box 'debian/stretch64' (v9.6.0) for 'virtualbox'!
==> sailfish_image_patcher: Importing base box 'debian/stretch64'...
Progress: 90%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/mathieu/.vagrant.d/boxes/debian-VAGRANTSLASH-stretch64/9.6.0/virtualbox/box.ovf", "--vsys", "0", "--vmname", "stretch_1542457752922_21024", "--vsys", "0", "--unit", "6", "--disk", "/run/media/mathieu/INT 4TB/JEUX STEAM/stretch_1542457752922_21024/stretch.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/mathieu/.vagrant.d/boxes/debian-VAGRANTSLASH-stretch64/9.6.0/virtualbox/box.ovf...
OK.
0%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Could not create the directory '/run/media/mathieu/INT 4TB/JEUX STEAM/stretch_1542457752922_21024' (VERR_ACCESS_DENIED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 886 of file VBoxManageAppliance.cpp

Should I worry about this? The paths seem totally unrelated and I'm not even sure why they are being processed.

Kabouik commented 5 years ago

I just unmounted the corresponding hard drive and the issue seems to be gone!

g7 commented 5 years ago

That's strange indeed. I guess that's an issue with VBoxManage feeding a wrong target path to vagrant, don't have a clue why.

Anyway, great that you resolved :) Closing this.