1
我试图在我的MacBook Pro上创建一个VirtualBox Ubuntu VM的流浪盒。当我运行命令时,出现一个我不明白的错误。我试过重建虚拟机。我尝试过不同状态的不同虚拟机。我一直打这个砖墙。vagrant包命令失败
它看起来像VBoxManage试图为包过程创建一个临时文件,但该文件由于某种原因不能被写入。这也发生在我的Ubuntu笔记本电脑上。所以这真的很有趣,并且让我怀疑VBoxManage本身是否存在问题,但是,似乎并不是很多人都有这个特定问题(尽管错误代码“代码VBOX_E_FILE_ERROR(0x80bb0004)”比较常见。)
这里是我的命令的输出:
earthmant$ vagrant package --base 64precise6
==> 64precise6: Attempting graceful shutdown of VM...
64precise6: Guest communication could not be established! This is usually because
64precise6: SSH is not running, the authentication information was changed,
64precise6: or some other networking issue. Vagrant will force halt, if
64precise6: capable.
==> 64precise6: Forcing shutdown of VM...
==> 64precise6: Exporting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["export", "64precise6", "--output", "/Users/earthmant/.vagrant.d/tmp/1417878317/box.ovf"]
Stderr: 0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance write failed
VBoxManage: error: File not accessible or erroneous file contents
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Appliance, interface IAppliance
VBoxManage: error: Context: "int handleExportAppliance(HandlerArg*)" at line 1121 of file VBoxManageAppliance.cpp
我遇到了同样的错误(使用VirtualBox 5.0.12和Vagrant 1.7.4)。事实证明,使用qcow2磁盘定义了guest虚拟机,并且使用vmdk磁盘定义的另一个guest虚拟机的打包工作正常。 – 2016-01-13 22:57:39