关于vagrant up的一个终结之谜

https://forums.centos.org/viewtopic.php?t=57223
和我的问题一样
[root@P1WQMSMDW02 /gpmaster/gpseg-1_down/k8s/k8s-node2]#vagrant reload
==> node: Attempting graceful shutdown of VM...
    node: Guest communication could not be established! This is usually because
    node: SSH is not running, the authentication information was changed,
    node: or some other networking issue. Vagrant will force halt, if
    node: capable.
==> node: Forcing shutdown of VM...
==> node: Clearing any previously set forwarded ports...
==> node: Fixed port collision for 22 => 2222. Now on port 2209.
==> node: Clearing any previously set network interfaces...
==> node: Preparing network interfaces based on configuration...
    node: Adapter 1: nat
==> node: Forwarding ports...
    node: 22 (guest) => 2209 (host) (adapter 1)
==> node: Running 'pre-boot' VM customizations...
==> node: Booting VM...
==> node: Waiting for machine to boot. This may take a few minutes...
    node: SSH address: 127.0.0.1:2209
    node: SSH username: vagrant
    node: 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.
[root@P1WQMSMDW02 /gpmaster/gpseg-1_down/k8s/k8s-node2]#
[root@P1WQMSMDW02 /gpmaster/gpseg-1_down/k8s/k8s-node2]#vagrant status
Current machine states:
node                      running (virtualbox)
The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.
[root@P1WQMSMDW02 /gpmaster/gpseg-1_down/k8s/k8s-node2]#vagrant halt
==> node: Attempting graceful shutdown of VM...
    node: Guest communication could not be established! This is usually because
    node: SSH is not running, the authentication information was changed,
    node: or some other networking issue. Vagrant will force halt, if
    node: capable.
==> node: Forcing shutdown of VM...