laravel "vagrant up" 它在 SSH 身份验证方法处停止：私钥
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/43379459/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
"vagrant up" it stops at SSH auth method: private key
提问by Arnau Guadall
I'm trying to install laravel on my computer with homestead environment. I followed all steps on the official documentation. And when I execute my "vagrant up" my console displays the following error.
我正在尝试在具有宅基地环境的计算机上安装 laravel。我遵循了官方文档中的所有步骤。当我执行“vagrant up”时，控制台显示以下错误。
.
.
Stops at SSH auth method. Previously I configured the ssh-keygen with "ssh-keygen -t rsa -b 4096 -C "[email protected]"
在 SSH 身份验证方法处停止。以前我用“ ssh-keygen -t rsa -b 4096 -C “[email protected]”配置了ssh-keygen
I added the host piece at .rb file:
我在 .rb 文件中添加了主机部分：
Even .yaml file. I think I edited properly
甚至 .yaml 文件。我认为我编辑正确
At hosts file I added: "192.168.10.10 administracio.dev" at the bottom of the file.
在主机文件中，我在文件底部添加了：“192.168.10.10 administracio.dev”。
And then when I let this error crash it shows the following error:
然后当我让这个错误崩溃时，它显示以下错误：
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.
Any suggestions?
有什么建议？
回答by halfer
(Posted on behalf of the OP).
（代表 OP 发布）。
Solution: I activated the Hardware acceleration in the BIOS environment.
解决方法：我在BIOS环境中开启了硬件加速。
回答by Gunnar
I had the same issue today and I found that my VirtualBox Settings (Network | Advanced | Cable Connected) were set correctly (that is the checkbox was checked.) I started comparing this VM, which has been stable for months, with some of my other VMs and found the only difference was in the Network Adapters, as Adapter 2 was different than all the rest.
我今天遇到了同样的问题，我发现我的 VirtualBox 设置（网络 | 高级 | 电缆连接）设置正确（即选中了复选框。）我开始比较这个已经稳定了几个月的虚拟机和我的一些其他虚拟机，发现唯一的区别在于网络适配器，因为适配器 2 与其他所有不同。
Adapter 1 was set to the following:
适配器 1 设置如下：
Attached To: NAT
Adapter Type: Intel PRO/1000 MT Desktop ....
while Adapter 2 was set to the following...
而适配器 2 设置为以下...
Attached To: Host-only Adapter
Adapter Type: PCnet-FAST III ...
I have not changed any of these network settings in VirtualBox, ever. Once I set Adapter 2 Adapter Type to the same settings as Adapter 1 as stated above, I then vagrant halt and vagrant up and back to normal.
我从未更改过 VirtualBox 中的任何这些网络设置。一旦我将 Adapter 2 Adapter Type 设置为与上述 Adapter 1 相同的设置，我就会停止 vagrant 和 vagrant up 并恢复正常。
回答by rubo77
The essential line for me when running Ubuntu 20.04 Focal Fossa (focal64) was
运行 Ubuntu 20.04 Focal Fossa (focal64) 时我的基本路线是
If the box appears to be booting properly, you may want to increase the timeout ("config.vm.boot_timeout") value.
如果该框显示正常启动，您可能需要增加超时 ("config.vm.boot_timeout") 值。
I changed my Vagrantfile and added this line:
我改变了我的 Vagrantfile 并添加了这一行：
config.vm.boot_timeout = 600 # wait max 10 minutes
So it seems, like the default (300 seconds) was not enough on my system to get it up running
因此，似乎默认值（300 秒）在我的系统上不足以让它运行
回答by 06userit
Solution works also for me : When setting in the Bios "Intel Virtualization Technology = Enabled", the "SSH auth method: private key " step is not frozen any more and VM starts normally. When setting back in the Bios "Intel Virtualization Technology = Disabled", the "SSH auth method: private key" step is frozen again.
解决方案也适用于我：在 Bios 中设置“Intel Virtualization Technology = Enabled”时，“SSH auth method: private key”步骤不再冻结，VM 正常启动。在 Bios 中设置回“Intel Virtualization Technology = Disabled”时，“SSH 身份验证方法：私钥”步骤再次冻结。
Motherboard : Asus Z170 Pro Gaming (lga1151), Bios menu : Advanced\Cpu Configuration, Virtual Box : 5.1.22, Vagrant : 1.9.5, Windows 10
主板：Asus Z170 Pro Gaming (lga1151)，Bios 菜单：Advanced\Cpu Configuration，Virtual Box：5.1.22，Vagrant：1.9.5，Windows 10
