Ubuntu 16.04 在 vagrant up 时冻结

Question

每次运行时vagrant up，ubuntu 16.04 都会冻结，我必须重新启动它。

我不能事件运行vagrant up --debug。

我正在使用widgetbox-php53框。

Answer 1

所以，我在booting VM使用Ubuntu 16.04 LTS 时遇到了同样的问题。

并通过大量硬重置在某些步骤中解决此问题 - 我已更新到Vagrant 2.0.1和VirtualBox 5.2。

检查您有哪些版本：

• vagrant -v （打开 GUI：帮助 --> 关于）
• virtualbox -v

流浪汉

1. 删除旧的index和index.lock在文件夹中的文件/home/USER/.vagrant.d/data/machine-index/
2. 下载 Vagrant 2.0.1 https://www.vagrantup.com/downloads.html
3. 安装包 sudo dpkg -i vagrant_2.0.1_x86_64.deb

虚拟盒子

删除当前的虚拟机

1. 运行sudo apt-get purge virtualbox*以删除所有文件
2. 检查是否有剩余 dpkg -l | grep virtualbox
3. （我不得不）删除 sudo apt-get purge unity-scope-virtualbox

为 Virtualbox 添加存储库（使用apt安装）

• sudo nano /etc/apt/sources.list
• 添加行 deb https://download.virtualbox.org/virtualbox/debian xenial contrib
• 添加密钥 wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -
• sudo apt-get update

安装最新的虚拟机

1. 跑 sudo apt-get install virtualbox-5.2
2. 运行sudo /sbin/vboxconfig以重建设置

我遇到的问题

您可能需要销毁您的盒子并重新构建。

流浪用户问题

The VirtualBox VM was created with a user that doesn't match the
current user running Vagrant. VirtualBox requires that the same user
be used to manage the VM that was created. Please re-run Vagrant with
that user. This is not a Vagrant issue.

删除了 .vagrant 文件夹rm -rf .vagrant来解决这个问题。

重复的虚拟机名称问题

The name of your virtual machine couldn't be set because VirtualBox
is reporting another VM with that name already exists. Most of the
time, this is because of an error with VirtualBox not cleaning up
properly. To fix this, verify that no VMs with that name do exist
(by opening the VirtualBox GUI). If they don't, then look at the
folder in the error message from VirtualBox below and remove it
if there isn't any information you need in there.

由于VBoxManage: error: Could not rename the directory错误无法vagrant up完成，我遇到了重复的 Virtualbox 名称问题。刚刚通过 GUI 删除了我的 Virtualbox VMs 文件夹中的文件夹。

机器索引问题

这就是开始我的冒险并让我从谷歌搜索到这里的原因。

The machine index which stores all required information about
running Vagrant environments has become corrupt. This is usually
caused by external tampering of the Vagrant data folder.

Vagrant cannot manage any Vagrant environments if the index is
corrupt. Please attempt to manually correct it. If you are unable
to manually correct it, then remove the data file at the path below.
This will leave all existing Vagrant environments "orphaned" and
they'll have to be destroyed manually.

Answer 2

一段时间后，将 Vagrant 更新到 2.0.1，将 VirtualBox 更新到 5.2，它为我解决了问题。

我使用的是 Vagrant 1.9.4 和 VirtualBox 5.0。