[SOLVED] Can't remove vagrant machine

HI guys,

Last time, I was installing kali linux from: https://app.vagrantup.com/Sliim/boxe...7.2-mate-amd64. After installation, I was not able to log-in to the machine, and can't delete it.

To reproduce the issue, I try to setup the new machine again. Sadly I was not able to remove this machine. Please check bellow:

MUMs-Mac-Pro:vagrant mum0l$ cat Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :
# boxes URL https://atlas.hashicorp.com/search.
 
Vagrant.configure("2") do |config|
  config.vm.define "kali-2017" do |node|
    node.vm.hostname = 'kali-2017'
    config.vm.boot_timeout = 20
    config.vm.box = "Sliim/kali-2017.2-mate-amd64"
    node.vm.network "private_network",
      ip: "192.168.10.73",
      auto_node: false
  end
  config.vm.define "kali" do |node|
    node.vm.hostname = 'kali'
    config.vm.boot_timeout = 20
    config.vm.box = "Sliim/kali-2017.2-mate-amd64"
    node.vm.network "private_network",
      ip: "192.168.10.74",
      auto_node: false
  end
end
MUMs-Mac-Pro:vagrant mum0l$ vagrant up kali
Bringing machine 'kali' up with 'virtualbox' provider...
==> kali: Importing base box 'Sliim/kali-2017.2-mate-amd64'...
 
==> kali: Matching MAC address for NAT networking...
==> kali: Checking if box 'Sliim/kali-2017.2-mate-amd64' is up to date...
==> kali: Setting the name of the VM: vagrant_kali_1513201592390_79317
==> kali: Clearing any previously set network interfaces...
==> kali: Preparing network interfaces based on configuration...
    kali: Adapter 1: nat
    kali: Adapter 2: hostonly
==> kali: Forwarding ports...
    kali: 22 (guest) => 2222 (host) (adapter 1)
==> kali: Booting VM...
==> kali: Waiting for machine to boot. This may take a few minutes...
    kali: SSH address: 127.0.0.1:2222
    kali: SSH username: vagrant
    kali: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
 
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
 
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
 
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.


MUMs-Mac-Pro:vagrant mum0l$ vagrant destroy kali
    kali: Are you sure you want to destroy the 'kali' VM? [y/N] y
There are errors in the configuration of this machine. Please fix
the following errors and try again:
 
vm:
* A box must be specified.
 
 
MUMs-Mac-Pro:vagrant mum0l$ vagrant box remove --all kali
The box you requested to be removed could not be found. No
boxes named 'kali' could be found.
MUMs-Mac-Pro:vagrant mum0l$ vagrant global-status|head
id       name      provider   state    directory                          
---------------------------------------------------------------------------
eefba63  kali-2017 virtualbox poweroff /Users/mum0l/vagrant                
d636933  kali      virtualbox running  /Users/mum0l/vagrant                
[

The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date. To interact with any of the machines, you can go to
that directory and run Vagrant, or you can use the ID directly
with Vagrant commands from any directory. 


MUMs-Mac-Pro:vagrant mum0l$ vagrant destroy d636933
    kali: Are you sure you want to destroy the 'kali' VM? [y/N] y
There are errors in the configuration of this machine. Please fix
the following errors and try again:
 
vm:
* A box must be specified.
 

MUMs-Mac-Pro:vagrant mum0l$

Maybe this will help.

https://www.vagrantup.com/docs/vagra...lifecycle.html

Not really... how should it help?

Originally Posted by grzeslaw Not really... how should it help?

Read it?

If it was easy, it wouldn't be worth it.

yes I read it, but I don't really get it.. My boxes are up2date, and I do not use any versioning. I was even never logged in into those boxes, because of errors.

MUMs-Mac-Pro:vagrant mum0l$ vagrant up
Bringing machine 'kali-2017' up with 'virtualbox' provider...
Bringing machine 'kali' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* A box must be specified.


MUMs-Mac-Pro:vagrant mum0l$ vagrant status
Current machine states:

kali-2017                 poweroff (virtualbox)
kali                      aborted (virtualbox)

This environment represents multiple VMs. The VMs are all listed
above with their current state. For more information about a specific
VM, run `vagrant status NAME`.
MUMs-Mac-Pro:vagrant mum0l$

Ok, found the root case: config was set incorrectly, I changed "config.vm.boot_timeout = 2" to "node.vm.boot_timeout = 2" and this helps
In directive "do |node|" the main word is "node" not, "config". As I was using multiply VMs, the config variable is accurate to general vm name definition, but not in deeper structure, which was defined by "node".