Vagrant Gurumeditation Curse...when vagrant up in ubuntu
Hello everyone I have installed virtual box & vagrant and tried to vagrant up on a box (joomlatools) but when i did I got an error saying that the status of the virtual box was in Gurumeditation mode… I powered off the box and powered it back on but when i run vagrant up I get the below error… Does anyone know how to fix this?
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["modifyvm", "15b64d8c-f8ab-431c-a1b0-72c2f57833c2", "--natpf1", "delete", "ssh"]
Stderr: VBoxManage: error: The machine 'joomlatools-box' is already locked for a session (or being unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "LockMachine(a->session, LockType_Write)" at line 462 of file VBoxManageModifyVM.cpp
Running
vagrant upwill try to launch the VM which is already powered on. You’ll need to power it off completely first.Hmm, Generally, I create a folder save the init file and vagrant up. When I do that i get the following error
The guest machine entered an invalid state while waiting for it
to boot. Valid states are ‘starting, running’. The machine is in the
'gurumeditation’ state. Please verify everything is configured
properly and try again.
If the provider you’re using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you’re using VirtualBox, run
vagrant upwhile theVirtualBox GUI is open.
If I start fresh and create the init file I can’t poweroff the virtualbox because it hasnt been created so I vagrant up and i get the same error. When I poweroff that specific virtual box and try to vagrant up again i get the same error, this is true for joomlatools, wordpress, laravel.
Also getting this error at the very end
There was an error while executing
VBoxManage, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: [“modifyvm”, “673d6b33-0415-4ed8-8cd6-d93cdbad29c5”, “–natpf1”, “delete”, “ssh”]
Stderr: VBoxManage: error: The machine 'joomlatools-box’ is already locked for a session (or being unlocked)
VBoxManage: error: Details: code VBOXEINVALIDOBJECTSTATE (0x80bb0007), component Machine, interface IMachine, callee nsISupports
VBoxManage: error: Context: “LockMachine(a->session, LockType_Write)” at line 462 of file VBoxManageModifyVM.cpp
bleh :-/
I’m getting this same error. Did you figure it out? I’m following the DigitalOcean instructions exactly.