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