Open gmaubach opened 2 months ago
Some problem with VirtualBox:
VBoxManage unregistervm "db-sqlite3" --delete VBoxManage: error: Cannot unregister the machine 'db-sqlite3' while it is locked VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports VBoxManage: error: Context: "Unregister(fDeleteAll ? CleanupMode_DetachAllReturnHardDisksAndVMRemovable :CleanupMode_DetachAllReturnHardDisksOnly, ComSafeArrayAsOutParam(aMedia))" at line 233 of file VBoxManageMisc.cpp
vagrant halt ==> db-sqlite3: Attempting graceful shutdown of VM... db-sqlite3: Guest communication could not be established! This is usually because db-sqlite3: SSH is not running, the authentication information was changed, db-sqlite3: or some other networking issue. Vagrant will force halt, if db-sqlite3: capable. ==> db-sqlite3: Forcing shutdown of VM...
Issue solved.
Error encountered
Virtual machine does not boot due to an error with guest communications.
Debug output
https://gist.github.com/gmaubach/2938628918668a05ca06b8c9b1ca274a
Expected behavior
Machine should boot normally.
Actual behavior
Boot process is interrupted.
Reproduction information
Vagrant version
Vagrant 2.3.4
Host operating system
Operating System: Debian GNU/Linux 12 (bookworm) Debian Version: 12.5 Kernel: Linux 6.1.0-20-amd64
Guest operating system
Vagrantbox: debian/bookworm64
Steps to reproduce
Just run "vagrant up --provision --debug"
Vagrantfile
I do not know which part causes the error. Thus complete Vagrantfile is provided.
Note: This bug report is filed upon request of Vagrant reporting when running "vagrant up --provision".