Re: [vagrant-up] vagrant vboxmanage verr_path_not_found when default machine folder on different drive

[Alvaro Miranda Aguilera]

Hello

can you test with hashicorp/precise64 ?

That will show better where the error is coming from

Thanks

On Sun, Jun 12, 2016 at 9:42 AM, Bill S <bill.st...@gmail.com> wrote:

Windows 10
Vagrant file is located on Drive E:\Vagrant\ubuntu-trusty-vb
Virtualbox machine folder F:


When vagrant up runs the image file directory name is wrong in the .vbox and .vbox-prev files and is  f:\ubuntu-cloudimg-trusty-vagrant-amd64_1465748344502_5020  and the one actually created was F:\ubuntu-trusty-vb_default_1465748361721_37792


Stderr: VBoxManage.exe: error: Could not open the medium 'F:\\ubuntu-cloudimg-trusty-vagrant-amd64_1465748344502_5020\box-disk1.vmdk'.
VBoxManage.exe: error: VD: error VERR_PATH_NOT_FOUND opening image file 'F:\\ubuntu-cloudimg-trusty-vagrant-amd64_1465748344502_5020\box-disk1.vmdk' (VERR_PATH_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MediumWrap, interface IMedium

Is this a bug or is there something I can change in the vagrantfile or configuration?

Thanks

--
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 vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/8c960cc6-c98b-4755-adf4-d1b98e73cb1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.