Skip to content
This repository has been archived by the owner on Jul 25, 2023. It is now read-only.

Failed to connect to VM! #1

Open
hemanth opened this issue Jun 18, 2012 · 4 comments
Open

Failed to connect to VM! #1

hemanth opened this issue Jun 18, 2012 · 4 comments

Comments

@hemanth
Copy link

hemanth commented Jun 18, 2012

[default] Waiting for VM to boot. This can take a few minutes.
[default] Failed to connect to VM!
Failed to connect to VM via SSH. Please verify the VM successfully booted
by looking at the VirtualBox GUI.

In the GUI : Changing the VM state from 'RESUMING' to 'RUNNING' It running fine there.

$ /opt/vagrant/bin/vagrant ssh
ssh_exchange_identification: Connection closed by remote host
$ uname -a
generic #65-Ubuntu SMP Tue Jan 24 13:48:14 UTC 2012 i686 GNU/Linux


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 10.10
Release:    10.10
Codename:   maverick

Could it be due to :

Guest Additions Version: 4.1.8
VirtualBox Version: 4.1.10
@rhelmer
Copy link
Owner

rhelmer commented Jun 18, 2012

Try uncommenting this line in Vagrantfile:

config.vm.boot_mode = :gui

Then kill the Virtualbox processes and "vagrant up again". Frequently virtualbox does not report problems in headless mode.

@hemanth
Copy link
Author

hemanth commented Jun 19, 2012

It prints the below and the prompt returns. What next?

[default] VM already created. Booting if it's not already running...

@rhelmer
Copy link
Owner

rhelmer commented Apr 3, 2013

@hemanth make sure that virtualbox is not running in the background - this is a problem with virtualbox, and you can't easily diagnose in the default (headless) mode.

@hemanth
Copy link
Author

hemanth commented Apr 3, 2013

Okies, will try that!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants