Problemas con vBox

[Matías]

==> homestead: Setting the name of the VM: homestead
The name of your virtual machine couldn’t be set because VirtualBox
is reporting another VM with that name already exists. Most of the
time, this is because of an error with VirtualBox not cleaning up
properly. To fix this, verify that no VMs with that name do exist
(by opening the VirtualBox GUI). If they don’t, then look at the
folder in the error message from VirtualBox below and remove it
if there isn’t any information you need in there.

VirtualBox error:

VBoxManage.exe: error: Could not rename the directory ‘C:\Users\Matute\VirtualBox VMs\ubuntu-18.04-amd64_1574023164989_16012’ to ‘C:\Users\Matute\VirtualBox VMs\homestead’ 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 3206 of file VBoxManageModifyVM.cpp

Tienen idea de por que el error? Agradezco por la ayuda!

[joseherrero]

$ vagrant box add laravel/homestead

The box ‘laravel/homestead’ could not be found or

could not be accessed in the remote catalog. If this is a private

box on HashiCorp’s Vagrant Cloud, please verify you’re logged in via

vagrant login. Also, please double-check the name. The expanded

URL and error message are shown below:

 

URL: [“https://vagrantcloud.com/laravel/homestead”%5D

Error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) – La funci�n de revocaci�n no puede comprobar la revocaci�n para el certificado.

 

[joseherrero]

¿Alguien tiene idea de cómo solucionar este error? Muchas gracias.

[Autor]

Entradas