Vagrant can't use the requested machine because it is locked

laravel vagrant virtual-machine homestead
Marco picture Marco · Apr 16, 2016 · Viewed 9.6k times · Source

I have tried to access my projects sites that I have set up on homestead, they were working all fine before, and I haven't been working on them for few weeks, but today when I have tried to access them I couldn't open the sites. I have tried to run vagrant ssh but I get this error:

  VM must be running to open SSH connection. Run `vagrant up`
  to start the virtual machine.

And when I try to do vagrant up, I get:

  Vagrant can't use the requested machine because it is locked! This
  means that another Vagrant process is currently reading or modifying
  the machine. Please wait for that Vagrant process to end and try
  again. Details about the machine are shown below:

  Name: default
  Provider: virtualbox

When I do:

 vagrant status 'idOfTheMachine'

I get:

vagrant status 'idOfTheMachine'
/Users/myName/Homestead/Vagrantfile:4: warning: already initialized constant VAGRANTFILE_API_VERSION
/Users/myName/Homestead/Vagrantfile:4: warning: previous definition of VAGRANTFILE_API_VERSION was here
Current machine states:

default                   poweroff (virtualbox)

The VM is powered off. To restart the VM, simply run `vagrant up`

When I have opened virtualbox, and tried to see the shared folders, I could see the shared folders in the terminal but not the projects inside of them. I have googled around about this issue, but can't find any solution to it. Should I destroy the homestead machine on the virtual box and make a new one, and if so, how to make that properly, so that I have the same projects on the new machine?

Answer

Tyler H picture Tyler H · Apr 27, 2016

I have this problem as well, and while I don't understand how/why it happens, I did find that running

vagrant reload {boxid}

will usually bring up the box and allow me to connect to it.

You're probably like me and 'vagrant halt' your box when you're done coding to free up resources and expect to just be able to turn it back on effortlessly with 'vagrant up', but it would seem that's not the case. Hopefully this gets you back on your feet and someone else who knows whats happening can explain why this happens.

Related questions

Using Laravel Homestead: 'no input file specified'

I am new to using Laravel, and Homestead, and would appreciate any help or a point in the right direction. I have successfully been able to get to the "You have arrived" screen when I run "php artisan serve" but …

Read More
error: OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054

While running the command vagrant box add laravel/homestead, I am getting this error: An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again. OpenSSL SSL_read: …

Read More
Laravel homestead IP address not working

I’m using Laravel Homestead 2.0 for my VM and am trying to serve my sites on the default IP address in the YAML file 192.168.10.10 My /etc/hosts file looks like this: My Homestead.yaml file looks like this: --- ip: "192.168.10.10" …

Read More