hashicorp/vagrant · error · Vagrant::Errors::MachineGuestNotReady
Guest-specific operations were attempted on a machine that i
Error message
Guest-specific operations were attempted on a machine that is not ready for guest communication. This should not happen and a bug should be reported.
What it means
Error "Guest-specific operations were attempted on a machine that is not ready for guest communication. This should not happen and a bug should be reported." thrown in hashicorp/vagrant.
Source
Thrown at lib/vagrant/machine.rb:279
def communicate
if !@communicator
requested = @config.vm.communicator
requested ||= :ssh
klass = Vagrant.plugin("2").manager.communicators[requested]
raise Errors::CommunicatorNotFound, comm: requested.to_s if !klass
@communicator = klass.new(self)
end
@communicator
end
# Returns a guest implementation for this machine. The guest implementation
# knows how to do guest-OS specific tasks, such as configuring networks,
# mounting folders, etc.
#
# @return [Guest]
def guest
raise Errors::MachineGuestNotReady if !communicate.ready?
@guest.detect! if !@guest.ready?
@guest
end
# This sets the unique ID associated with this machine. This will
# persist this ID so that in the future Vagrant will be able to find
# this machine again. The unique ID must be absolutely unique to the
# virtual machine, and can be used by providers for finding the
# actual machine associated with this instance.
#
# **WARNING:** Only providers should ever use this method.
#
# @param [String] value The ID.
def id=(value)
@logger.info("New machine ID: #{value.inspect}")
id_file = nil
if @data_dirView on GitHub (pinned to 35f3160f4a)
When it happens
Trigger: Thrown at lib/vagrant/machine.rb:279 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/56fda2e132425cab.
Report an issue: GitHub.