VERR_ALREADY_EXISTS

Virtualbox is failing to use the custom name because there is either a VM
with that name or a directory already exists.

I suggest review C:\Users\Eduardo's PC\VirtualBox VMs\

and the Virtualbox Gui for bradphp.puphpet

Alvaro

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virusvrij.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Oct 29, 2017 at 2:11 AM, Eduardo Herrera <[email protected]> wrote:

> *Windows 10 - Virtual Box 5.1.30 - Vagrant 2.0*
>
> *Error after 'vagrant up' command*
>
>
> A customization command failed:
>
> ["modifyvm", :id, "--name", "bradphp.puphpet"]
>
> The following error was experienced:
>
> #<Vagrant::Errors::VBoxManageError: There was an error while executing
> `VBoxManage`, a CLI used by Vagrant
> for controlling VirtualBox. The command and stderr is shown below.
>
> Command: ["modifyvm", "14767214-2d71-425b-8edf-0fe762582391", "--name",
> "bradphp.puphpet"]
>
> Stderr: VBoxManage.exe: error: Could not rename the directory
> 'C:\Users\Eduardo's PC\VirtualBox VMs\local-sites_bradphp_1509232196757_11807'
> to 'C:\Users\Eduardo's PC\VirtualBox VMs\bradphp.puphpet' to save the
> settings file (VERR_ALREADY_EXISTS)
> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component
> SessionMachine, interface IMachine, callee IUnknown
> VBoxManage.exe: error: Context: "SaveSettings()" at line 3060 of file
> VBoxManageModifyVM.cpp
> >
>
> Please fix this customization and try again.
>
> --
> 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/868d2d00-ad3f-4ed1-8448-dc23a205cbee%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/868d2d00-ad3f-4ed1-8448-dc23a205cbee%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
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/CAHqq0ewoH_V4Uo0tU8dn8gGwuDUH%2B33TS%2BeWzb9o6UWO_bG7qw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to