Add workaround for shared folders issue

playbooks/archivematica-centos7/README.md

@@ -57,5 +57,12 @@ Deploy](docs/digital-ocean-install-example.rst) document.
 
 6. The ansible playbook `singlenode.yml` specified in the Vagrantfile will provision using the branches of archivematica specfied in the file `vars-singlenode.yml`. Edit this file if need to deploy other branches.  
 
+7. If you get errors regardig the Vagrant shared folders, they are usually due
+to different versions of Virtualbox. One way to fix it, is using a vagrant
+plugin that installs the host's Virtualbox Guest Additions on the guest system :
+  ```
+  $ vagrant plugin install vagrant-vbguest
+  $ vagrant vbguest
+  ```
 
 For more archivematica development information, see: https://wiki.archivematica.org/Getting_started

playbooks/archivematica-xenial/README.md

@@ -54,5 +54,12 @@ machine.
 
 6. The ansible playbook `singlenode.yml` specified in the Vagrantfile will provision using qa branches of archivematica. To provision using the stable 1.5.x/0.8.x branches, replace "vars-singlenode-qa.yml" with "vars-singlenode-1.5.yml" in `singlenode.yml`. You can also modify create a custom vars file and pass it instead (to modify role variables to deploy custom branches, etc.)  
 
+7. If you get errors regardig the Vagrant shared folders, they are usually due
+to different versions of Virtualbox. One way to fix it, is using a vagrant
+plugin that installs the host's Virtualbox Guest Additions on the guest system:
+  ```
+  $ vagrant plugin install vagrant-vbguest
+  $ vagrant vbguest
+  ```
 
 For more archivematica development information, see: https://wiki.archivematica.org/Getting_started

playbooks/archivematica/README.md

@@ -55,5 +55,10 @@ Deploy](docs/digital-ocean-install-example.rst) document.
 
 6. The ansible playbook `singlenode.yml` specified in the Vagrantfile will provision using stable branches of archivematica. To provision using the qa 1.x/0.x branches, replace "vars-singlenode-1.6.yml" with "vars-singlenode-qa.yml" in `singlenode.yml`. You can also modify create a custom vars file and pass it instead (to modify role variables to deploy custom branches, etc.)  
 
+7. If you get errors regardig the Vagrant shared folders, they are usually due to different versions of Virtualbox. One way to fix it, is using a vagrant plugin that installs the host's Virtualbox Guest Additions on the guest system :
+  ```
+  $ vagrant plugin install vagrant-vbguest
+  $ vagrant vbguest
+  ```
 
 For more archivematica development information, see: https://wiki.archivematica.org/Getting_started