Closed smaction closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the issue template and include your OS/Vagrant/VVV versions! Don't forget you can get support in the VVV slack at https://varyingvagrantvagrants.org/docs/en-US/slack/
VVV
Join the VVV Slack Workspace
Windows 10 and Vagrant 2.30
It should be enough to move the folder and start again vagrant.
I am not sure anyway where vagrant will place the VM image for caching and also virtualbox.
You can use any folder for VVV but as Daniele says VVV doesn’t determine the location of the VM itself, you’ll need to configure VirtualBox itself to use your D drive which is not something we can help you with
On Sun, 4 Sep 2022 at 11:10, Daniele Scasciafratte @.***> wrote:
It should be enough to move the folder and start again vagrant.
I am not sure anyway where vagrant will place the VM image for caching and also virtualbox.
— Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/2629#issuecomment-1236303706, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAOLZ7GTMACRU5FFTDDPMDV4RYQNANCNFSM6AAAAAAQEBLJX4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>
The same would be true of Hyper-V if you’re using that as a provider instead of VirtualBox
Thank you to both of you.
My C; drive on a Windows machine is full. I need to install VVV on my D: drive. Is this possible?
Thanks,
Scott