Bumping this, I guess. I'm still having nothing but problems. I've "solved" the SSH issue by upgrading to Vagrant 1.6.3, but now I get the "Failed to mount folders in Linux guest error. There's a LOT of chatter about this one around the Google-sphere, but none of it is getting me anywhere.
I'm running Windows 8 (now), Vagrant 1.6.3 and Virtualbox 4.3.12. The guest is Ubuntu 12.04. Neither my Windows username nor my password contain anything but letters & numbers. I'm also running the vb-guest plugin which _should_, if I understand it correctly, get me the correct guest additions, but that seems to be failing as well: "An error occurred during installation of VirtualBox Guest Additions 4.3.12. Some functionality may not work as intended" Some posted solutions require me to SSH into the vagrant machine and create a symlink, but a) every time I bring it up from nothing? and, b) The Samba issue seems to power off the box so I couldn't SSH even if I wanted to do so. Any ideas? I'm running out of patience for this thing and have no idea what to try next. Vagrant works wonderfully on *nix, but if I can't get it functional (and performant) on Windows, I can't adopt it across my entire team. Thanks. On Friday, May 16, 2014 2:08:54 PM UTC-4, Rob Wilkerson wrote: > > I'm trying to configure Windows access to a Vagrant environment via Samba. > If I launch the Command Prompt as an Administrator, Vagrant can't connect > via SSH and a VM shutdown is forced. I've tried tweaking the ownership of > ~/.vagrant.d/insecure_private_key, but no luck with "Administrator" as the > owner. I'm not a Windows user, myself, so I could really use a hand with > this one. What am I missing? I know that, in order to use SMB for syncing, > I have to vagrant up as an Administrator, but I'm not sure what else I need > to do to get past this step. > > Win7, Vagrant 1.5.4. > > Thanks. > -- 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.
