hashicorp/vagrant · error · Vagrant::Errors::MachineLocked
Vagrant can't use the requested machine because it is locked
Error message
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: %{name}
Provider: %{provider} What it means
Error "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: %{name} Provider: %{provider}" thrown in hashicorp/vagrant.
Source
Thrown at lib/vagrant/machine_index.rb:138
# @return [MachineIndex::Entry]
def get(uuid)
entry = nil
@lock.synchronize do
with_index_lock do
# Reload the data
unlocked_reload
data = find_by_prefix(uuid)
return nil if !data
uuid = data["id"]
entry = Entry.new(uuid, data)
# Lock this machine
lock_file = lock_machine(uuid)
if !lock_file
raise Errors::MachineLocked,
name: entry.name,
provider: entry.provider
end
@machine_locks[uuid] = lock_file
end
end
entry
end
# Tests if the index has the given UUID.
#
# @param [String] uuid
# @return [Boolean]
def include?(uuid)
@lock.synchronize do
with_index_lock doView on GitHub (pinned to 35f3160f4a)
When it happens
Trigger: Thrown at lib/vagrant/machine_index.rb:138 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of hashicorp/vagrant@35f3160f4a (2026-08-21).
Data as JSON: /api/errors/0522a3c8189d6f25.
Report an issue: GitHub.