blocks|key|2459151|text|看起来最新的版本在VPS上不起作用。我不得不选择旧版本的软件来在这个ubuntu+VPS上运行它们，我选择的版本是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2459152|VirtualBox+>=+4.3.12|code-block|syntax|javascript|2459153|和|2459154|Vagrant+>=+1.5.3|2459155|这是可行的，但您必须配置ssh|2459156|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Seems like the latest versions are not working on a VPS.
I had to choose the older versions of the softwares to run them on this ubuntu VPS
The versions i chose was

<pre><code>VirtualBox &gt;= 4.3.12
</code></pre>

AND

<pre><code>Vagrant &gt;= 1.5.3
</code></pre>

This works but you will have to configure ssh

blocks|key|2459186|text|当我尝试在亚马逊EC2+Ubuntu16.04实例上使用虚拟化(virtualbox+%2B+vagrant)时，我遇到了这个问题。显然，这似乎是不可能的，因为亚马逊决定阻止该选项-+virtualbox安装将失败/您将得到标题中的消息时，尝试‘流浪’。正如这篇文章中所说的(有点陈旧，但说服了我)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2459187|http://cloudstacking.com.s3-website-us-east-1.amazonaws.com/posts/running-hyper-v-vmware-or-xen-on-an-aws-ec2-instance.html|offset|length|2459188|可以在这里找到一个更复杂的解决方案-但我没有尝试过它是否有效：|2459189|HVX:+Virtual+infrastructure+for+the+cloud|2459190|entityMap|0|LINK|mutability|MUTABLE|url|1|https://www.ravellosystems.com/technology/hvx^0|0|0|3F|0|0|0|0|15|1|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@$D|U|E|V|1|W]]|A|$]]|$1|F|3|G|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|J|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|C]]|Q|$5|M|N|O|A|$P|R]]]]

I came across this issue when trying use virtualisation (virtualbox + vagrant) on an AWS EC2 Ubuntu 16.04 instance. Apparently, it seems it's not possible because Amazon decided to block that option - virtualbox installation will fail / you will get the message in the title when trying 'vagrant up'. As said in this article (a bit old, but convinced me):

<a href="http://cloudstacking.com.s3-website-us-east-1.amazonaws.com/posts/running-hyper-v-vmware-or-xen-on-an-aws-ec2-instance.html" rel="nofollow noreferrer">http://cloudstacking.com.s3-website-us-east-1.amazonaws.com/posts/running-hyper-v-vmware-or-xen-on-an-aws-ec2-instance.html</a>

A more complex solution can be found here - but I didn't try it to see if it works:

<a href="https://www.ravellosystems.com/technology/hvx" rel="nofollow noreferrer">HVX: Virtual infrastructure for the cloud</a>

blocks|key|2459227|text|我也遇到了这个问题，我通过打开"Oracle+Virtual+Box+Manager“GUI修复了这个问题。转到“设置”->“网络”并选择“适配器1”，然后单击箭头展开该选项，并确保选中了“已连接电缆”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2459228|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this issue also and I fixed it by opening up the &quot;Oracle Virtual Box Manager&quot; GUI. Go to &quot;Settings&quot; -&gt; &quot;Network&quot; and choose &quot;Adapter 1&quot; then expand the option by clicking on the arrow and make sure that &quot;Cable Connected&quot; is checked.

blocks|key|1846307|text|我的版本是virtualbox(5.1.20)，vagrant(1.9.3)。我通过删除以下内容来解决此错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1846308|v.customize+["modifyvm",+:id,+"--natdnshostresolver1",+"on"]|offset|length|style|CODE|1846309|我是新手，希望这能帮上忙。|1846310|entityMap^0|0|0|1O|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

My version virtualbox(5.1.20), vagrant(1.9.3). I solve this error by deleting

<code>v.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]</code>

I´m newbie, hope this help.

blocks|key|4570500|text|在一些晦涩难懂的论坛上找到了以下解决方案，它的工作原理是将它添加到您的Vagrantfile底部，就在写着end的行前|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4570501|++++config.vm.provider+"virtualbox"+do+%7Cvb%7C
++++++++vb.customize+["modifyvm",+:id,+"--cableconnected1",+"on"]
++++end|code-block|syntax|javascript|4570502|与手动更改VirtualBox+AFAIK中的设置相同，但我个人更喜欢基础架构作为代码解决方案。这样一来，同事就不必在某处处理同样的问题了。|4570503|entityMap^0|Z|B|1H|3|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Found the following solution on some arcane forum, it works by adding it to the bottom of your <code>Vagrantfile</code> just before the line that says <code>end</code>:

<pre><code> config.vm.provider "virtualbox" do |vb|
 vb.customize ["modifyvm", :id, "--cableconnected1", "on"]
 end
</code></pre>

Does the same as manually changing the setting in VirtualBox AFAIK, but I personally prefer infrastructure as code solutions. That way a colleague doesn't have to deal with the same problem somewhere down the line.

blocks|key|5987313|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5987314|📷|atomic|offset|length|5987315|5987316|我发现我的WSL在我的Windows+10上启用了，所以使用以下命令禁用了它|5987317|bcdedit+/set+hypervisorlaunchtype+off|code-block|syntax|javascript|5987318|但它对我没有帮助，所以我浏览了Windows的功能，发现虚拟机平台是打开的，所以我查了查，它链接到了WSL，所以我把它关闭了，我的ssh密钥问题就解决了。|5987319|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6f85f1aa6df58ed38fb73a2a58161b51.png|imageAlt^0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@$E|11|F|12|1|13]]|A|$]]|$1|G|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|16|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X|Y|-4]]]]

<a href="https://i.stack.imgur.com/5DsoX.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/5DsoX.png" alt="enter image description here"></a>

I found that my WSL enabled on my Windows 10 so disabled it by using this command 

<pre><code>bcdedit /set hypervisorlaunchtype off
</code></pre>

but it didn't helped me so i went through Windows features and found that Virtual Machine Platform was turned ON so i look it up and it was linked to WSL so i turned it OFF and my ssh key problem solved.

blocks|key|2459316|text|在花了几周的时间阅读和测试我找到的所有答案，甚至是那些没有标记为正确的答案后，我不记得在哪里，有人提到了一些关于Guest+Additions的事情……我找到了这个插件并安装了它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2459317|++++vagrant+plugin+install+vagrant-vbguest|code-block|syntax|javascript|2459318|它就像一种护身符。问题解决了。|2459319|堆栈:+Virtualbox+6.0、Vagrant+2.2.7、OS+Fedora+31|2459320|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

After spending weeks reading and testing all the answers I found, even the answers that were not marked as correct, I don't remember where, someone mentioned something about Guest Additions... I found the plugin and installed it:

<pre><code> vagrant plugin install vagrant-vbguest
</code></pre>

It works like a charm. Problem solved.

Stack: Virtualbox 6.0, Vagrant 2.2.7, OS Fedora 31

blocks|key|5987362|text|在我的例子中，我已经进入了一种无效的状态。在vagrant+up之前运行这个命令就可以了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5987363|注意:请谨慎使用，因为这将清除流浪实例上的所有数据。|5987364|vagrant+destroy+--force|code-block|syntax|javascript|5987365|entityMap^0|M|A|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

In my case, I had gotten into a sort of an invalid state. Running this command before <code>vagrant up</code> did the trick.
Note: Use with caution, as this will clear all data on the vagrant instance.
<pre><code>vagrant destroy --force
</code></pre>

blocks|key|1846408|text|我也被困在Windows的同一个SSH+auth+method:+Private+key+(试图通过SSH连接到Ubuntu机器)，然后几分钟后我就超时了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1846409|注意，如果您正在运行多个+SSH代理(可能是非自愿的)。例如，在Windows中，您可以同时拥有Pageant和OpenSSH身份验证代理(可以在Windows+Services下找到的梯子)。在我的例子中，私钥是在Pageant下添加的，但OpenSSH身份验证代理似乎在操作系统重新启动后获得了优先级。|BOLD|1846410|最终禁用了后者，重新启动操作系统，在Pageant中再次加载密钥，然后vagrant+ssh工作。|1846411|entityMap^0|G|S|0|A|2|0|Z|B|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|L|$]]

I was getting stuck in Windows too at the same <code>SSH auth method: Private key</code> (trying to SSH to an Ubuntu box), and then I get a timeout after a few minutes.
Beware if you are running multiple SSH agents (maybe involuntary). For example, in Windows, you could have both Pageant and OpenSSH Authentication Agent (the ladder you can find under Windows Services). In my case, the private key was added under Pageant but OpenSSH Authentication Agent seems to have taken priority after an OS restart.
Ended up disabling the latter, restarting the OS, loading the key again in Pageant, and then <code>vagrant ssh</code> worked.

blocks|key|4570676|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4570677|我也有这个问题，我通过打开"Oracle+Virtual+Box+Manager“图形用户界面并转到”设置“->”网络“并选择”适配器1“，然后通过单击箭头展开选项并确保选中了”电缆连接“来修复它。|blockquote|4570678|4570679|4570680|我尝试了这个答案，发现默认情况下已经启用了。我尝试禁用并重新启用，这首先给出了下面的消息Warning:+Connection+aborted.+Retrying...，之后vagrant继续启动并成功启动|offset|length|style|CODE|4570681|entityMap^0|0|0|0|0|18|14|0^^$0|@$1|2|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|O|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|P|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|R|7|@$H|S|I|T|J|K]]|8|@]|9|$]]|$1|L|3|-4|4|5|6|U|7|@]|8|@]|9|$]]]|M|$]]

<blockquote>
I had this issue also and I fixed it by opening up the &quot;Oracle Virtual Box Manager&quot; GUI and go to &quot;Settings&quot; -&gt; &quot;Network&quot; and choose &quot;Adapter 1&quot; then expand the option by clicking on the arrow and make sure that &quot;Cable Connected&quot; is checked.
</blockquote>
I tried this answer and found that this was already enabled by default. I Tried disabling and re-enabling and this first gave me the following message <code>Warning: Connection aborted. Retrying...</code> after which vagrant continued the startup and did so successfully

blocks|key|2459465|text|2021年5月更新:所以我发现这是Vagrant中的一个实际bug。解决方案直接来自Hashicorps'+GitHub。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2459466|主要是打开vagrantfile并在config.vm.provider+:virtualbox+do+%7Cv%7C下和end之前添加以下代码行|style|CODE|2459467|v.customize+["modifyvm",+:id,+"--uart1",+"0x3F8",+"4"]
v.customize+["modifyvm",+:id,+"--uartmode1",+"file",+File::NULL]|code-block|syntax|javascript|2459468|如果该行为config.vm.provider+:virtualbox+do+%7Cvb%7C，则代码将为：|2459469|vb.customize+["modifyvm",+:id,+"--uart1",+"0x3F8",+"4"]
vb.customize+["modifyvm",+:id,+"--uartmode1",+"file",+File::NULL]|2459470|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/hashicorp/vagrant/issues/11777^0|16|I|0|0|5|B|I|11|1L|3|0|0|5|12|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@$A|13|B|14|F|G]|$A|15|B|16|F|G]|$A|17|B|18|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|19|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1A|8|@$A|1B|B|1C|F|G]]|9|@]|C|$]]|$1|O|3|P|5|J|7|1D|8|@]|9|@]|C|$K|L]]|$1|Q|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

UPDATE AS OF MAY 2021: So I found that this was an actual bug in Vagrant. The solution comes directly from <a href="https://github.com/hashicorp/vagrant/issues/11777" rel="nofollow noreferrer">Hashicorps' GitHub</a>.
Basically open the <code>vagrantfile</code> and add these lines under <code>config.vm.provider :virtualbox do |v|</code> and before <code>end</code>:
<pre><code>v.customize [&quot;modifyvm&quot;, :id, &quot;--uart1&quot;, &quot;0x3F8&quot;, &quot;4&quot;]
v.customize [&quot;modifyvm&quot;, :id, &quot;--uartmode1&quot;, &quot;file&quot;, File::NULL]
</code></pre>
If the line is <code>config.vm.provider :virtualbox do |vb|</code> then the code will be:
<pre><code>vb.customize [&quot;modifyvm&quot;, :id, &quot;--uart1&quot;, &quot;0x3F8&quot;, &quot;4&quot;]
vb.customize [&quot;modifyvm&quot;, :id, &quot;--uartmode1&quot;, &quot;file&quot;, File::NULL]
</code></pre>

blocks|key|2459523|text|嗯，我遇到了类似的问题，并在下面的线程中得到了解决方案:Hyper这是因为我在Windows10上运行docker桌面，它使用windows+SubsystemLinux并使用https://forums.virtualbox.org/viewtopic.php?f=6&t=97578+-v来启动虚拟环境。这不允许或使Virtual+box在响应ssh超时时变得太慢，并且还会导致文件系统错误。你应该特别关注“乌龟”图标，这意味着Virtualbox太慢，如果一切正常，你会在virtualbox控制台上看到"V“图标。按照说明停止hyper-v，重新启动机器，它将正常工作。要完全关闭Hyper-V，请执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2459524|2459525|关闭了所有程序。您必须重新启动主机。|ordered-list-item|2459526|2459527|2459528|请注意，我有64位主机，但无法安装64位来宾。本教程在步骤2中还有几个要查找的内容。请确保所有这些内容都已关闭。|2459529|2459530|click+it+>找到命令提示符图标，右键单击该图标，然后选择[以Administrator.身份运行][|2459531|2459532|2459533|2459534|输入以下命令:+bcdedit+/set虚拟机管理程序启动类型关闭|2459535|2459536|2459537|输入以下命令:+shutdown+-s+-t+2|2459538|2459539|2459540|当电脑关机时，拔掉它的电源20秒钟。然后再插上电源，启动Windows10。|2459541|2459542|entityMap|0|LINK|mutability|MUTABLE|url|https://forums.virtualbox.org/viewtopic.php?f=6&t=97578^0|2G|1J|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|D|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1F|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]|$1|J|3|K|5|G|7|1I|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1J|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1K|8|@]|9|@]|C|$]]|$1|O|3|-4|5|G|7|1L|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1N|8|@]|9|@]|C|$]]|$1|R|3|S|5|G|7|1O|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|V|3|W|5|G|7|1R|8|@]|9|@]|C|$]]|$1|X|3|-4|5|6|7|1S|8|@]|9|@]|C|$]]|$1|Y|3|-4|5|6|7|1T|8|@]|9|@]|C|$]]|$1|Z|3|10|5|G|7|1U|8|@]|9|@]|C|$]]|$1|11|3|-4|5|6|7|1V|8|@]|9|@]|C|$]]|$1|12|3|-4|5|6|7|1W|8|@]|9|@]|C|$]]]|13|$14|$5|15|16|17|C|$18|19]]]]

Well, i faced similar issue and got the resolution in the below thread:
<a href="https://forums.virtualbox.org/viewtopic.php?f=6&amp;t=97578" rel="nofollow noreferrer">https://forums.virtualbox.org/viewtopic.php?f=6&amp;t=97578</a>
This was caused by me running docker desktop on windows 10, which uses windows SubsystemLinux and utilized Hyper-v to launch the Virtual env. This does not allow or makes Virtual box too slow to respond that the ssh times out and also results in File system errors.
you should specially focus on the &quot;turtle&quot; icon which means Virtualbox too slow and i if everything is fine then you will see the &quot;V&quot; icon on virtualbox console. follow the instruction to stop hyper-v reboot the machine and it will work.
To turn Hyper-V off completely, do this:
<ol>
<li>Shut down all programs. You will have to reboot your host.
</li>
<li>See I have a 64bit host, but can't install 64bit guests. This tutorial has a couple more things to look for in step 2. Be sure these are all turned off.
</li>
<li>Find the Command Prompt icon, right click it and choose Run As Administrator.
</li>
<li>Enter this command:
bcdedit /set hypervisorlaunchtype off
</li>
<li>Enter this command:
shutdown -s -t 2
</li>
<li>When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.
</li>
</ol>

blocks|key|5987547|text|确保在vagrant挂起时查看VirtualBox上的VM终端。对我来说，问题是文件系统损坏。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5987548|我跑了一下：|5987549|fsck+-yf+/dev/mapper/homestead--vg--root|code-block|syntax|javascript|5987550|从VirtualBox终端，问题已得到解决。|5987551|entityMap^0|V|G|0|0|6|0|0|0|M|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

Be sure to look at the VM terminal on VirtualBox while vagrant is hanging.
For me the issue was a broken file system.
I ran:
<pre><code>fsck -yf /dev/mapper/homestead--vg--root
</code></pre>
from the VirtualBox terminal and the issue was resolved.

blocks|key|4570844|text|按照上面用户Kokokoko的建议，我将以下几行添加到了我的vagrnt文件中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4570845|vb.customize+["modifyvm",+:id,+"--uart1",+"0x3F8",+"4"]
vb.customize+["modifyvm",+:id,+"--uartmode1",+"file",+File::NULL]|code-block|syntax|javascript|4570846|安装了最新的virtualbox，确保vm已正确停止，并为我工作。|4570847|结合使用Virtualbox+6.1.32、Vagrant+2.2.10和Ubuntu/Xenial64|4570848|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Following the advice from user Kokokoko above I added the following lines to my vagrnt file.
<pre><code>vb.customize [&quot;modifyvm&quot;, :id, &quot;--uart1&quot;, &quot;0x3F8&quot;, &quot;4&quot;]
vb.customize [&quot;modifyvm&quot;, :id, &quot;--uartmode1&quot;, &quot;file&quot;, File::NULL]
</code></pre>
installed the latest virtualbox, made sure the vm was halted properly and it worked for me.
using Virtualbox 6.1.32 with Vagrant 2.2.10 with Ubuntu/Xenial64

I am running <code>VirtualBox 5.0.24</code> and Vagrant <code>1.8.5</code> on Digital Ocean VPS running on <code>Ubuntu 14.04 LTS Precise</code>
I am using the box <code>ubuntu/precise64</code>
Everything works fine but when i do <code>vagrant up</code> it hangs at the
<pre><code>SSH auth method: Private key
</code></pre>
and the exit out giving time out. Now, i can consider increasing the execution time but it already takes a fare amount of time before giving that error. I don't know what I am doing wrong.
Here is my VAGRANTFILE
<pre class="lang-rb prettyprint-override"><code># -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(&quot;2&quot;) do |config|

 config.vm.box = &quot;ubuntu/precise64&quot;
 
 config.vm.provider :virtualbox do |vb|
 vb.customize ['modifyvm', :'1cf9e703-607e-4338-9162-20abbeca94b0', '--pae', 'on']
 vb.customize ['modifyvm', :'1cf9e703-607e-4338-9162-20abbeca94b0', '--hwvirtex', 'off']
 vb.customize ['modifyvm', :'1cf9e703-607e-4338-9162-20abbeca94b0', '--vtxvpid', 'off']
 end

end
</code></pre>

Vagrant hangs at "SSH auth method: Private key

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在数字海洋VPS上运行VirtualBox 5.0.24和Vagrant 1.8.5，在Ubuntu 14.04 LTS Precise上运行，我使用box ubuntu/precise64一切正常，但当我使用vagrant up时，它挂在SSH auth method: Private key而出口给了我们超时。现...

问Vagrant挂在"SSH auth method: Private key“处
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Vagrant挂在"SSH auth method: Private key“处EN