Guest machine entered an invalid state while waiting for it to boot.

[Mason]

Hi,
I am using the debian/buster64 image from vagrant cloud to create 3 VM's. Everything works fine. Once I shut down these machines and do a

Code: Select all

vagrant up

The vagrant machine halts at

Code: Select all

node1: SSH auth method: private key

. My only option is to vagrant destroy and recreate all the machine from scratch.

Code: Select all

  N = 3
  (1..N).each do |machine_id|
    config.vm.define "node#{machine_id}" do |machine|
      machine.vm.box = "debian/buster64"
      machine.vm.hostname = "node#{machine_id}"
      machine.vm.network "public_network", bridge: "wlp59s0", ip: "192.168.100.#{200+machine_id}"
      machine.vm.provider "virtualbox" do |vbox|
        vbox.name = "node#{machine_id}"
        vbox.cpus = "1"
        vbox.memory = "512"
        vbox.gui = true
      end
      machine.vm.provision :ansible do |ansible|
        ansible.playbook = "../dev.site.yaml"
      end
    end
  end

This is what I see on the Virtualbox GUI

Code: Select all

error symbol 'grub_calloc' not found
entering rescue mode 
grub rescue >_

I have VT-x/AMD enabled and I can see that in the GUI on the vm general information as well.
Can someone tell me what is going on ?

[scottgus1]

Regrettably we don't grok Vagrant here. They just happen to use Virtualbox, and they have their own forums if you'd like to inquire further.

If you make your own VM directly in Virtualbox and have trouble shown by Virtualbox error messages we might be able to help.

[Mason]

This is what the error says. They are pointing on virtualbox.
Here is the error message that is being spit out by vagrant.


The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'paused' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.


I will try my luck there. I just came here because the error says so.