Vagrant + Virtualbox + Windows 7: "vagrant up" command does nothing.

89 views
Skip to first unread message

LeVonne Johnson Jr

unread,
Mar 1, 2018, 12:18:06 AM3/1/18
to Vagrant




I am trying to start a vm with the "vagrant up" command and nothing happens.  I follow all the steps to download and initialize the root folder and that works fine. However when i run the "vagrant up" command, the ".vagrant" file is created but the nothing else and the cursor just blinks. No files are added to the ".vagrant" folder and the vm is not added Virtualbox.


The 3 images show the cursor under the command, the downloaded box file, and the empty ".vagrant" folder


Is there something I am missing? How can I fix this?


Thanks in advance

Alvaro Miranda Aguilera

unread,
Mar 1, 2018, 4:57:40 PM3/1/18
to vagra...@googlegroups.com
not sure can be

try open cmd.exe and try there

add --debug to vagrant up

if you got Anti Virtus try disable it for a test

did you reboot after Vagrant installation ??

--
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/fd6ecc2c-3f82-4870-8cfa-773d0d8b8983%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

LeVonne Johnson Jr

unread,
Mar 1, 2018, 8:26:47 PM3/1/18
to Vagrant
Thanks for the reply Alvaro! I found that I was getting a debug message "DEBUG subprocess: stdout: 2" which meant I needed to update my Windows Powershell. Once I did that I was able to bring up my vm!


On Thursday, March 1, 2018 at 4:57:40 PM UTC-5, Alvaro Miranda Aguilera wrote:
not sure can be

try open cmd.exe and try there

add --debug to vagrant up

if you got Anti Virtus try disable it for a test

did you reboot after Vagrant installation ??
On Wed, Feb 28, 2018 at 9:18 PM, LeVonne Johnson Jr <broad...@gmail.com> wrote:




I am trying to start a vm with the "vagrant up" command and nothing happens.  I follow all the steps to download and initialize the root folder and that works fine. However when i run the "vagrant up" command, the ".vagrant" file is created but the nothing else and the cursor just blinks. No files are added to the ".vagrant" folder and the vm is not added Virtualbox.


The 3 images show the cursor under the command, the downloaded box file, and the empty ".vagrant" folder


Is there something I am missing? How can I fix this?


Thanks in advance

--
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.



--
Alvaro

Reply all
Reply to author
Forward
0 new messages