Perhaps the entry for the plugin v 3.2.2 is related to this. Can you try 
rolling back the plugin version and see if that makes a difference? I see 
you have a bug open on the GitHub for Vagrant as well, keep us updated if 
there is a resolution.3.2.2 (February 12, 2015)
   
   - synced_folders: revert symlink-specific code; recent versions of 
   Fusion and Workstation handle symlinks properly without any additional 
   configuration; incorporating workaround docs for users on older versions of 
   VMWare software that have trouble with symlinks
   - workstation-windows: fix slash mismatch preventing multi-vm port 
   forwarding from working properly


On Wednesday, June 17, 2015 at 5:49:06 PM UTC-5, dragon788 wrote:
>
> Your syntax looks good, but the support of symlinks is somewhat 
> questionable. When you say reboot do you mean 'vagrant reload' or are you 
> using the Linux reboot mechanism?
>
> On Tuesday, June 16, 2015 at 2:55:34 PM UTC-5, Pablo Gosse wrote:
>>
>> Hi all. I'm encountering a problem with Vagrant when trying to create 
>> symlinks on the guest in the folder that is shared with the host (/vagrant) 
>> and I'm hoping someone can help. Here's my environment info:
>>
>> Host OS: Windows 7 Enterprise SP 1
>> Guest OS: CentOS release 6.5 (Final) (using the chef/centos-6.5 box)
>> VMWare Workstation: 11.1.0
>> Vagrant: 1.7.2
>> Vagrant Plugins: vagrant-share (1.1.3, system)
>>                          vagrant-vmware-workstation (3.2.8)
>>
>> I'm trying to create a symlink inside the /vagrant folder such that files 
>> can be added to it from the Windows host.
>>
>> In my Vagrantfile I have the following:
>>
>>   config.vm.provider "vmware_workstation" do |v|
>>     v.vmx["sharedFolder0.followSymlinks"] = "TRUE"
>>   end
>>
>> When I try to create a symlink inside the /vagrant shared folder, this is 
>> the result:
>>
>> [root@drupal-dev-gossep-local ~]# mkdir /var/derp
>> [root@drupal-dev-gossep-local ~]# ln -s /var/derp /vagrant/derplink
>> ln: creating symbolic link `/vagrant/derplink': Operation not supported
>>
>> Debug output from both vagrant up and vagrant reload show the following:
>>
>>  INFO vmx_modify:   - Set: sharedFolder0.followSymlinks = 'TRUE'
>>
>> However when I manually inspect the vmx file after the machine is up, I 
>> see:
>>
>> sharedfolder0.followsymlinks = "FALSE"
>>
>> Even if I change the vmx file to TRUE, when I reboot the machine it is 
>> reset to FALSE.
>>
>> Can anyone provide any advice?
>>
>> Thanks,
>>
>> Pablo
>>
>

-- 
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.

Reply via email to