Dear Alvaro, I ran the vbguest plugin and it did update my guest additions from 4.X.X to 5.X.X.
However, this did not fix the issue. I still get exactly the same errors as before. Arne On Wednesday, August 5, 2015 at 4:30:05 PM UTC-6, Arne Wolframm wrote: > > Dear Alvaro, > > I am not upgrading the OS. I am using config.vm.box = "ubuntu/vivid64" from > Atlas box repository. > > Should I still check out the link for vbguest? > > Regards, > > Arne > > > On Wednesday, August 5, 2015 at 4:23:02 PM UTC-6, Alvaro Miranda Aguilera > wrote: >> >> Are you updating the OS? >> >> If you upgrade the OS and Kernel, this probably is the cause. >> >> You need to recompile the modules, or use a plugin that will do this for >> you. >> >> If this is the problem, this plugin will help: >> >> https://github.com/dotless-de/vagrant-vbguest >> >> vagrant plugin install vagrant-vbguest >> >> On Thu, Aug 6, 2015 at 10:20 AM, Arne Wolframm <[email protected]> >> wrote: >> > 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. >> > -- 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/82c5edf3-2ec6-471b-a9dd-b55e6dcb9728%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
