Question

我最近更新了我的windows10并尝试运行虚拟机，但它让我保持同样的错误次数'等待机器启动时超时'，我已经尝试了所有可能的方法，启用gui，增加超时值，甚至更新了流浪者和虚拟框

C:\Users\tmsfi\fullstack-nanodegree-vm\vagrant>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/ubuntu-16.04-i386' is up to date...
==> default: There was a problem while downloading the metadata for your box
==> default: to check for updates. This is not an error, since it is usually 
due
==> default: to temporary network problems. This is just a warning. The 
problem
==> default: encountered was:
==> default:
==> default: Could not resolve host: vagrantcloud.com
==> default:
==> default: If you want to check for box updates, verify your network 
connection
==> default: is valid and try again.
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 8000 (guest) => 8000 (host) (adapter 1)
default: 8080 (guest) => 8080 (host) (adapter 1)
default: 5000 (guest) => 5000 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: 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.

C:\Users\tmsfi\fullstack-nanodegree-vm\vagrant>vagrant ssh
ssh_exchange_identification: read: Connection reset by peer

请帮我解决这个问题，提前谢谢你 Meghana

Answer 1

我已经弄明白了，我们将面临这个问题，因为我们的系统已禁用虚拟化。要检查它是启用还是禁用，请转到

Taskmanager-->Performance

检查虚拟化是启用还是禁用，如果禁用则启用它当我们的Windows更新到最新版本时我们需要在BIOS设置中启用虚拟化，这样做会发生

setting-->Update&Security-->Recovery-->Advance startup-->click(restart now)

重新启动后，它提供了很少的选项，然后点击

Troubleshoot-->Advanced options-->Select UEFI Firmware Settings-->Click 
Restart.

您的系统将重新启动并带您进入BIOS。现在启用您的Intel Virtual技术并保存并重新启动系统。

请参阅此How to change BIOS settings in windows

Answer 2

我启用了虚拟化并重新安装，然后再次遇到此问题

E：\ vagrant>无所事事使用“ virtualbox”提供程序启动计算机“默认” ... ==>默认值：检查'chrislentz / trusty64-lamp'版本'3.0.0'是否是最新的... ==>默认值：计算机已配置。运行vagrant provision或使用--provision ==>默认值：强制置备标志。标记为始终运行的预配器仍将运行。

在Windows 10中等待机器启动时超时'超时'

2 个答案: