Искал в интернете по подобной проблеме темы. Проблема распространенная) Но актуальноq была давным-давно. Без особых обдумываний начал качать по старым скриптам виртуалку и проблем огреб по горло)
Посоветуйте, пожалуйста, стоит ли здесь переустанавливать VirtualBox, если да, то по каким скриптам?
Версия Ubuntu 22.04
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: bridged
==> default: Forwarding ports...
default: 80 (guest) => 8000 (host) (adapter 1)
default: 3306 (guest) => 33060 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "55ca9bac-2249-485a-932f-f7d7d2596b50", "--type", "headless"]
Stderr: VBoxManage: error: The machine 'VagrantVM' is already locked by a session (or being locked or unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: "LaunchVMProcess(a->session, sessionType.raw(), ComSafeArrayAsInParam(aBstrEnv), progress.asOutParam())" at line 726 of file VBoxManageMisc.cpp