Re: [vagrant-up] No prompt in VM after Vagrant up - system just hangs

[Alvaro Miranda Aguilera]

does this happen on a new box?

ie 

mkdir trusty64

cd trusty64

vagrant init -m ubuntu/trusty64

vagrant up

?

does happen with a different box? say hashicorp/precise64

Thanks

Alvaro

On Thu, Dec 7, 2017 at 1:02 PM, Nigel <n.bi...@gmail.com> wrote:

Hi all,

I'm running Vagrant 2.0.1 with VirtualBox 5.2.2 on a Windows 10 host, launching it from within Git Bash (part of Git for Windows 2.15.1.2) Previously, I had no problems spinning up the standard ubuntu/trusty64 image. Without knowingly making any changes, when I now run vagrant ssh, I connect to the VM, but it hangs without showing the command prompt.

I don't encounter this issue on my Linux host (Ubuntu 17.10 running the same versions of Vagrant and VirtualBox) with exactly the same Vagrant bootstrap provisioning files, so this looks like a Windows platform issue, but as I said, it's worked fine before.

I've tried re-installing both Vagrant and VirtualBox, clearing out old config files left behind by both apps (excluding removing the actual box images in the box folder) without success.

I would be very grateful for some advice, as I can't work in the Vagrant-managed VM anymore.

Many thanks.

Nigel

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c8c54605-241e-4d98-b430-644447837da4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Will Jaynes]

I too have this same problem. Same Vagrant 2.0.1 with VirtualBox 5.2.2 on a Windows 10 host, launching it from within Git Bash. Both Laravel Homestead and  the hashicorp/precise64  act the same way. I also, previously had no problems, sorry I don't know what my previous setup was. When I run vagrant ssh I get onto the virtual machine in some kind of bash shell, but there's no prompt, no aliases (so the .bashrc hasn't been read), and the arrow keys and autocomplete doesn't work. It just strange. Not sure what to do.

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c8c54605-241e-4d98-b430-644447837da4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Robert Lilly]

I too am experiencing this, same setup. I am suspecting something with the latest version of Git for Windows. When I use cmd.exe to do 'vagrant up' and then 'vagrant ssh' I get the normal BASH prompt and things look as expected. But when I use Git Bash, after doing 'vagrant ssh' things get wonky. Also, if I launch the VirtualBox GUI and access the VM that way I get a normal BASH prompt.

I will try rolling back to an earlier version of Git for Windows and see how that works. I will report my findings back here.

[thornlord]

Hi all,

I was able to use the `ssh` command from my $PATH as follows.

ssh vag...@127.0.0.1 -p2222 -i C:/users/sdalziel/learn-chef/.vagrant/machines/default/virtualbox/private_key

I feel that this is only a work-around and hope to either post or see the steps to repair soon.

Cheers.
S

[Tara Walker]

I found this solution and it works perfectly with vagrant ssh

Environment: 

Vagrant version : 2.0.1

• Windows 10
• Virtualbox : 5.1.30
• git bash : 2.15.1

Solved using this by putting this line in .bash_profile in c:/users/<yourlogin>
VAGRANT_PREFER_SYSTEM_BIN=1 vagrant ssh

Reference can be found here: https://github.com/hashicorp/vagrant/issues/9143

On Friday, December 8, 2017 at 4:45:30 AM UTC-5, Alvaro Miranda Aguilera wrote:

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c8c54605-241e-4d98-b430-644447837da4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro