Vagrant “浮动上升间歇错误”；SSH以非零退出状态“响应”；或启动超时错误

大多数时候，每当我运行Wagrant up时，它都会挂断在某个地方，几分钟后，最终会显示以下内容。这是一个全新安装的流浪者，虚拟箱，家园，所以我想知道是什么问题，因为这些都是未修改的

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mv -f '/tmp/vagrant-network-entry-1602866071' '/etc/netplan/50-vagrant.yaml'
chown root:root '/etc/netplan/50-vagrant.yaml'
chmod 0644 '/etc/netplan/50-vagrant.yaml'
netplan apply

Stdout from the command:



Stderr from the command:

Traceback (most recent call last):
  File "/usr/sbin/netplan", line 23, in <module>
    netplan.main()
  File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
    self.run_command()
  File "/usr/share/netplan/netplan/cli/utils.py", line 186, in run_command
    self.func()
  File "/usr/share/netplan/netplan/cli/commands/apply.py", line 46, in run
    self.run_command()
  File "/usr/share/netplan/netplan/cli/utils.py", line 186, in run_command
    self.func()
  File "/usr/share/netplan/netplan/cli/commands/apply.py", line 174, in command_apply
    subprocess.check_call(['udevadm', 'settle'])
  File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['udevadm', 'settle']' returned non-zero exit status 1.
 INFO interface: Machine: error-exit ["Vagrant::Errors::VagrantError", "The following SSH command responded with a non-zero exit status.\nVagrant assumes that this means the command failed!\n\nmv -f '/tmp/vagrant-network-entry-1602866071' '/etc/netplan/50-vagrant.yaml'\nchown root:root '/etc/netplan/50-vagrant.yaml'\nchmod 0644 '/etc/netplan/50-vagrant.yaml'\nnetplan apply\n\nStdout from the command:\n\n\n\nStderr from the command:\n\nTraceback (most recent call last):\n  File \"/usr/sbin/netplan\", line 23, in <module>\n    netplan.main()\n  File \"/usr/share/netplan/netplan/cli/core.py\", line 50, in main\n    self.run_command()\n  File \"/usr/share/netplan/netplan/cli/utils.py\", line 186, in run_command\n    self.func()\n  File \"/usr/share/netplan/netplan/cli/commands/apply.py\", line 46, in run\n    self.run_command()\n  File \"/usr/share/netplan/netplan/cli/utils.py\", line 186, in run_command\n    self.func()\n  File \"/usr/share/netplan/netplan/cli/commands/apply.py\", line 174, in command_apply\n    subprocess.check_call(['udevadm', 'settle'])\n  File \"/usr/lib/python3.6/subprocess.py\", line 311, in check_call\n    raise CalledProcessError(retcode, cmd)\nsubprocess.CalledProcessError: Command '['udevadm', 'settle']' returned non-zero exit status 1.\n"]

此外，有时，当我再次运行Wagrant up时，这将显示：

==> homestead: Waiting for machine to boot. This may take a few minutes...
    homestead: SSH address: 127.0.0.1:2222
    homestead: SSH username: vagrant
    homestead: 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.

---

因此错误不一致。

框中的/var/log/syslog中可能有错误。您可以发布它吗？框中的/var/log/syslog中可能有错误。你能把它寄出去吗？

==> homestead: Waiting for machine to boot. This may take a few minutes...
    homestead: SSH address: 127.0.0.1:2222
    homestead: SSH username: vagrant
    homestead: 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.