Nope, no nfs. This is the output from a brand new MBP with nothing but Yosemite, VMWare Fusion 6 and Vagrant installed.
I already shoot them an email like a month ago but so far no response. I have been experiencing this ever since I bought the VMWare plugin and ditched VirtualBox, but until now I never needed to create a new vm more than once per project, so the "taking ownership" approach was good enough. Now I'm in a project where I need to create/destroy a vm multiple times per day so this issue started to become really annoying. On Wed, Oct 29, 2014 at 6:27 PM, Alvaro Miranda Aguilera <[email protected]> wrote: > hello, I am sure someone may read this email from Hashicorp, but that > output doesn't look right to me. > > do you use nfs? if yes, can you test without nfs? > > other than that, I will suggest you send an email with that same output to > the support account. You should have gotten an email about that when you > got the license. > > include an output of vagrant plugin list and a vagrant file to repro the > issue so they can have a full picture of your environment. > > Alvaro. > > On Thu, Oct 30, 2014 at 7:25 AM, Hermano Cabral < > [email protected]> wrote: > >> Sure, this is from a brand new install of Yosemite + VMWare Fusion + >> Vagrant: >> >> hermanocabral at Mrs-Jones in ~/projects >> $ id >> uid=501(hermanocabral) gid=20(staff) >> groups=20(staff),401(com.apple.sharepoint.group.1),12(everyone),61(localaccounts),79(_appserverusr),80(admin),81(_appserveradm),98(_lpadmin),33(_appstore),100(_lpoperator),204(_developer),398(com.apple.access_screensharing),399(com.apple.access_ssh) >> hermanocabral at Mrs-Jones in ~/projects >> $ umask >> 0022 >> hermanocabral at Mrs-Jones in ~/projects >> $ ls -alR escluster >> total 32 >> drwxr-xr-x 6 hermanocabral staff 204 Oct 28 22:15 . >> drwxr-xr-x 10 hermanocabral staff 340 Oct 24 22:16 .. >> -rw-r--r--@ 1 hermanocabral staff 8196 Oct 28 21:18 .DS_Store >> drwxr-xr-x 3 root staff 102 Oct 28 21:17 .vagrant >> -rw-r--r--@ 1 hermanocabral staff 2760 Oct 28 22:15 Vagrantfile >> drwxr-xr-x 4 hermanocabral staff 136 Oct 17 18:29 puppet >> >> escluster/.vagrant: >> total 0 >> drwxr-xr-x 3 root staff 102 Oct 28 21:17 . >> drwxr-xr-x 6 hermanocabral staff 204 Oct 28 22:15 .. >> drwxr-xr-x 3 root staff 102 Oct 28 21:17 machines >> >> escluster/.vagrant/machines: >> total 0 >> drwxr-xr-x 3 root staff 102 Oct 28 21:17 . >> drwxr-xr-x 3 root staff 102 Oct 28 21:17 .. >> drwxr-xr-x 3 root staff 102 Oct 28 21:17 default >> >> escluster/.vagrant/machines/default: >> total 0 >> drwxr-xr-x 3 root staff 102 Oct 28 21:17 . >> drwxr-xr-x 3 root staff 102 Oct 28 21:17 .. >> drwxr-xr-x 2 root staff 68 Oct 28 22:36 vmware_fusion >> >> escluster/.vagrant/machines/default/vmware_fusion: >> total 0 >> drwxr-xr-x 2 root staff 68 Oct 28 22:36 . >> drwxr-xr-x 3 root staff 102 Oct 28 21:17 .. >> >> escluster/puppet: >> total 24 >> drwxr-xr-x 4 hermanocabral staff 136 Oct 17 18:29 . >> drwxr-xr-x 6 hermanocabral staff 204 Oct 28 22:15 .. >> -rw-r--r--@ 1 hermanocabral staff 8196 Oct 28 21:15 .DS_Store >> drwxr-xr-x 3 hermanocabral staff 102 Oct 28 22:14 manifests >> >> escluster/puppet/manifests: >> total 8 >> drwxr-xr-x 3 hermanocabral staff 102 Oct 28 22:14 . >> drwxr-xr-x 4 hermanocabral staff 136 Oct 17 18:29 .. >> -rw-r--r-- 1 hermanocabral staff 1687 Oct 28 22:14 default.pp >> >> >> >> On Wednesday, October 29, 2014 1:51:30 AM UTC-3, Alvaro Miranda Aguilera >> wrote: >>> >>> can you paste some output? >>> >>> from command line >>> >>> id >>> umask >>> ls -alR <folder> >>> >>> that will list including .vagrant, so do at the directory level where >>> you Vagrantfile is >>> >>> Alvaro. >>> >>> >>> On Wed, Oct 29, 2014 at 12:15 PM, Hermano Cabral < >>> [email protected]> wrote: >>> >>>> That's actually one of the first things I've tried, It's already inside >>>> my home folder. Still no joy. >>>> >>>> On Tuesday, October 28, 2014 6:03:29 PM UTC-3, Umair Chagani wrote: >>>>> >>>>> You should change where vagrant creates VMs to a place where you have >>>>> full access. Try setting the VAGRANT_VMWARE_CLONE_DIRECTORY env >>>>> variable. See the link below for more details: >>>>> >>>>> https://docs.vagrantup.com/v2/vmware/configuration.html >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, Oct 28, 2014 at 4:59 PM, Hermano Cabral < >>>>> [email protected]> wrote: >>>>> >>>>>> Howdy, >>>>>> >>>>>> I'm constantly having to take ownership of the .vagrant folder before >>>>>> starting up a VM with vmware fusion. If I don't do that, VMWare fusion >>>>>> says >>>>>> it cant open the .vmdk due to insufficient permission. >>>>>> >>>>>> Does anyone know how to fix this? >>>>>> >>>>>> Cheers. >>>>>> >>>>>> PS. reinstalling both vagrant and VMWare fusion didn't help. >>>>>> >>>>>> >>>>>> -- >>>>>> 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. >>>>>> >>>>> >>>>> -- >>>> 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. >>>> >>> >>> -- >> 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. >> > > -- > 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. > -- 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.
