当我在digitalocean服务器(ubuntu)上运行vagrant up
命令时,它会显示以下错误。此命令在本地工作正常但在服务器上不起作用。
$ vagrant up
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["modifyvm", "d2015e22-d634-46d6-9de5-9ca5e9ecea38", "--natpf1", "delete", "ssh", "--natpf1", "delete", "tcp9100", "--natpf1", "delete", "tcp9101", "--natpf1", "delete", "tcp9102", "--natpf1", "delete", "tcp9103", "--natpf1", "delete", "tcp9104", "--natpf1", "delete", "tcp9105"]
Stderr: VBoxManage: error: The machine 'LaunchKit_default_1473257270586_51004' is already locked for a session (or being unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: "LockMachine(a->session, LockType_Write)" at line 493 of file VBoxManageModifyVM.cpp
答案 0 :(得分:0)
VirtualBox认为您的虚拟机仍在运行。
它可能由一个进程持有
运行ps -ef | grep -i "vbox"
并终止与您的VM关联的进程(是任何)
如果您没有找到该过程,请强制VBox停止VM
VBoxManage controlvm LaunchKit_default_1473257270586_51004 poweroff