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.
On Friday, December 8, 2017 at 4:45:30 AM UTC-5, Alvaro Miranda Aguilera wrote: > > 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 <javascript:>> > 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+...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/c8c54605-241e-4d98-b430-644447837da4%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/c8c54605-241e-4d98-b430-644447837da4%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Alvaro > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/88301b79-aed3-4a8c-a400-92b9fc61ed20%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
