I had a similar problem (I was starting a batch script using the Vagrant file, but the batch script doesn't finish. It is a service, so it stays open, waiting commands. The Command Prompt on my windows VM wasn't appearing either. It was in the Processes List thought I think.)
The way I fixed it was by using my Vagrant file to add the batch script to the Task Scheduler, than running that new scheduled task using the Vagrant file. Here is an example : $start_selenium_grid = <<SCRIPT schtasks /create /XML "C:/selenium-grid-extras/Selenium-Grid-Extras.xml" /TN "Selenium-Grid-Extras" schtasks /run /tn "Selenium-Grid-Extras" SCRIPT config.vm.provision :shell, :inline => $start_selenium_grid I was forced to use /XML instead of just passing in the information, because if I just passed in the information, it wouldn't run from the command line if not plugged in. Create the task manually one time in Task Scheduler, than export it to XML, and use that XML. Inside the XML file you will see the command to run my batch script. I hope this helps! Shawn On Friday, August 8, 2014 2:50:30 AM UTC-7, Clément Sezettre wrote: > > Nop still not working, I think it's because WinRM works in background on > the guest machine. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
