is the box public? can you share a link? on the win10 box can you run this
vagrant halt set VAGRANT_LOG=debug vagrant up and share all the generated log over a gist? from inside that vm then do uname -a lsmod | grep -i vbox mount df -Ph Thanks! Alvaro. On Wed, Mar 30, 2016 at 3:20 PM, Isaiah Banks <[email protected]> wrote: > Hello everyone, > > I created my own base box following the Vagrant and other tutorials. The > base box looks as if it was successfully created. However, I'm finding that > on different versions of Windows (host machine), the Vagrant / VirtualBox > setup is responding differently. > > I'm using Vagrant 1.8.1 and VirtualBox 5.0.16. The base box is Ubuntu > 14.04 LTS. > > On Windows 7 Professional, everything works just fine. The box is loaded > and added to the Vagrant environment. I can ssh into it and I see the > vagrant shared folder that holds the repository files in the guest machine. > > However, on Windows 10, after the box is added to the environment, I get > connection issues (authentication failed) with Vagrant but somehow it's > still able to ssh into the machine after the authentication attempts time > out. Then when I list the root directory, there is no vagrant shared folder. > > I've already tried to manually mount the folder through Linux by running > the command as well as editing the /etc/fstab file. Also on the VirtualBox > machine, when I select Device -> Shared Folders, and look at the name and > path of the shared folder it's the same as the one on the WIndows 7 machine > that works. This very odd. Not to mention on my Windows 8.1 laptop, the > base box won't load at all. All 3 environments are running the same version > of VirtualBox and Vagrant. Also, there are no missing Microsoft C++ > redistributable files on either system. I've already verified that. > > Also, one more thing I've tried is to reload guest additions on the Ubuntu > machine itself and that didn't work. > > Hopefully someone is able to help. Thanks! > > -- > 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/fadbb6f7-e01f-4ea1-8048-1ec80082cdcf%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/fadbb6f7-e01f-4ea1-8048-1ec80082cdcf%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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/CAHqq0eyGz7r0aX6Cxx1Sev%2BVj00u3Vuaq7yHGeiYqbSsf%2BZyfg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
