I am setting up a Ubuntu 15.04 VM on Win7 using Vagrant 1.7.4 and VBox 
5.0.0.


On the first vagrant up I can ssh into the machine using vagrant putty and 
everything is setup correctly and works. When I run vagrant halt, the VM 
shuts down gracefully without error messages.


However, when I try to restart the VM using vagrant up; vagrant putty, the 
machine is in a strange state. For example, the default synced folder 
/vagrant is empty, even though the second vagrant up call prints this 
message:


default: /vagrant => C:/Users/ArneUser/numecs/dev_env


Also, this vagrant up call prints the following message in PowerShell:


The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/initctl emit --no-wait vagrant-mounted MOUNTPOINT=

Stdout from the command:

Stderr from the command:

stdin: is not a tty
bash: line 2: /sbin/initctl: No such file or directory


I am running a really basic setup just to test for this error, so I don't 
think the mistake is in my provisioning script. Some pointers in the right 
direction would be appreciated.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/36ccd6b5-ff99-441f-bdd2-0d43e0b92b46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to