No, there's not much you can do/diagnose using CLI or Ssh at this stage, because the VM fails to initialize properly and is not in a "working" state.
You should follow the advice contained in the error message.
Destroy your current VM:
vagrant destroy
then open VirtualBox GUI, and restart the Vagrant setup with :
vagrant up
You can then watch in the VM Console/Window (from Virtualbox GUI) what fails and prevents the setup from running.
An alternative way to start the VM with a console GUI would be to modify your Vagrantfile
:
# You will find this line in the Vagrantfile Vagrant.configure("2") do |config| #Add this directive config.vm.provider "virtualbox" do |v| v.gui = true end end
(destroy your existing and failing VM with vagrant destroy
and then run vagrant up
)
If the remote machine (where VirtualBox runs) is a Unix box accessed using SSH, you may be able to export the GUI to your local machine using the -X
option when SSHing to it. See this answer for more details about ssh -X