hello try with a new VM.
mkdir precise64 cd precise64 vagrant init -m hashicorp/precise64 vagrant up The error you are having, its common if you update everything on the guest, including kernel, if this happen a rebuild of virtualbox modules is required. Does this happen even on a new box? Alvaro. On Sun, Mar 12, 2017 at 7:28 PM, Ap Seh <[email protected]> wrote: > Hi, > > I had the misfortune of upgrading my VirtualBox version 5.1.14 to 5.1.16 > and now my folders simply fail to mount. I ran the following command vagrant > plugin install vagrant-vbguest & it did what it did. I checked my guest > additions and they are the same version as my VirtualBox. There are no > other errors that I get except towards the end i get the following message : > . > . > . > default] GuestAdditions 5.1.16 running --- OK. > ==> default: Checking for guest additions in VM... > ==> default: Configuring and enabling network interfaces... > ==> default: Mounting shared folders... > default: /vagrant => D:/test_p32 > > *Vagrant was unable to mount VirtualBox shared folders. This is usually* > *because the filesystem "vboxsf" is not available. This filesystem is* > *made available via the VirtualBox Guest Additions and kernel module.* > *Please verify that these guest additions are properly installed in the* > *guest. This is not a bug in Vagrant and is usually caused by a faulty* > *Vagrant box. For context, the command attempted was:* > > mount -t vboxsf -o dmode=775,fmode=664,uid=1001,gid=33 vagrant /vagrant > > The error output from the command was: > > : No such file or directory > > > How can I get over this error and have my folders synced / shared ! > > Thanks loads. > > > > On Tue, Feb 28, 2017 at 7:09 AM, Ap Seh <[email protected]> wrote: > >> Hi Alvaro, >> >> Yes that's what i meant I guess - an alternate to the linux commands in >> vagrant or what vagrant does to achieve the same effect as the chown and >> chmod commands. >> >> Sure it helps, 😃, >> Thank you very much. >> Ajoo >> >> >> On Tue, Feb 28, 2017 at 3:20 AM, Alvaro Miranda Aguilera < >> [email protected]> wrote: >> >>> hello >>> >>> almost >>> >>> you could think have the same effect, but are not the same commands. >>> >>> chown is to set the owner >>> chmod is to set the permissions >>> >>> think on existing files and folder and you want to change them. >>> >>> >>> the ones you see in vagrant, are actually mount point and user owner of >>> the mount point. >>> >>> it doesn't run any chmod/chown command, but the result "looks the same" >>> >>> by default will be vagrant user and some permissions, and you are >>> overriding that. >>> >>> but may or may not run chown/chmod. >>> >>> hope this helps >>> >>> Alvaro >>> >>> On Mon, Feb 27, 2017 at 8:01 PM, Ap Seh <[email protected]> wrote: >>> >>>> Hi Alvaro, >>>> >>>> I would be grateful if you can confirm that the following commands in >>>> vagrantfile : >>>> >>>> config.vm.synced_folder "complete/path/to/folder/restricted", >>>> "/vagrant/path/upto/restricted", >>>> owner: "vagrant", >>>> group: "www-data", >>>> mount_options: ["dmode=750,fmode=640"] >>>> >>>> actually replace the chown and chmod commands in linux. I mean that >>>> these commands in vagrant do what chown and chmod do in linux. >>>> Thanks loads and sorry if this is the most noob question. I would >>>> rather be sure. >>>> >>>> Thanks load. >>>> Ajoo >>>> >>>> >>>> >>>> On Sun, Feb 26, 2017 at 2:35 AM, Ap Seh <[email protected]> wrote: >>>> >>>>> Hi Alvaro, >>>>> >>>>> Thanks for that great tip. It worked !!! I did have to modify it a bit >>>>> though. Here's the exact code that I used >>>>> >>>>> config.vm.synced_folder "complete/path/to/folder/restricted", >>>>> "/vagrant/path/upto/restricted", >>>>> owner: "vagrant", >>>>> group: "www-data", >>>>> mount_options: ["dmode=750,fmode=640"] >>>>> >>>>> That worked !! >>>>> >>>>> Thanks loads once again ! >>>>> Ajoo. >>>>> >>>>> >>>>> >>>>> On Sun, Feb 26, 2017 at 1:50 AM, Ap Seh <[email protected]> wrote: >>>>> >>>>>> Hi Alvaro, >>>>>> >>>>>> Thanks loads for the reply. I'll check it out and revert in a while. >>>>>> I do have a hunch that this should work. >>>>>> Much obliged. >>>>>> >>>>>> Thanks loads ! >>>>>> Ajoo >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Sat, Feb 25, 2017 at 10:48 PM, Alvaro Miranda Aguilera < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> hello >>>>>>> >>>>>>> vagrant is running commands so if nested folder permissions doesn't >>>>>>> work is not a vagrant issue >>>>>>> >>>>>>> if you were running vboxmanage share + mount on the guest wirthout >>>>>>> vagrant you will probably hit the same issues. >>>>>>> >>>>>>> nested mountpoint are usually troublesome, but this may work >>>>>>> >>>>>>> config.vm.synced_folder ".", "/vagrant", >>>>>>> owner: "vagrant", >>>>>>> group: "www-data", >>>>>>> mount_options: ["dmode=775,fmode=664"] >>>>>>> >>>>>>> config.vm.synced_folder "restricted", "/vagrant/restricted", >>>>>>> owner: "vagrant", >>>>>>> group: "www-data", >>>>>>> mount_options: ["dmode=750,fmode=640"] >>>>>>> >>>>>>> -- >>>>>>> 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 a topic in >>>>>>> the Google Groups "Vagrant" group. >>>>>>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>>>>>> pic/vagrant-up/R2gPXfXxnGQ/unsubscribe. >>>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>>> [email protected]. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyFdoikWY >>>>>>> Gt93w1jgnjZaYrPvQ8GwBrc7jnNK2XuaTXvg%40mail.gmail.com >>>>>>> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyFdoikWYGt93w1jgnjZaYrPvQ8GwBrc7jnNK2XuaTXvg%40mail.gmail.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/ms >>>> gid/vagrant-up/CA%2BnFXPHtPXi9NgW8U2ogPy%2BXurNgLReNhtO%3Ddk >>>> Px5uAOneP5%2Bg%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/vagrant-up/CA%2BnFXPHtPXi9NgW8U2ogPy%2BXurNgLReNhtO%3DdkPx5uAOneP5%2Bg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Alvaro >>> >>> -- >>> 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 a topic in the >>> Google Groups "Vagrant" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>> pic/vagrant-up/R2gPXfXxnGQ/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/vagrant-up/CAHqq0eypekvJBmPf-OnS%2BYXk_U05fYWV4hkHgUAFub >>> am8TLBiw%40mail.gmail.com >>> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0eypekvJBmPf-OnS%2BYXk_U05fYWV4hkHgUAFubam8TLBiw%40mail.gmail.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/CA%2BnFXPGKb-GqitT%2BzuVBQo1nPQEBW5punLZePtvec4DH > 6mb%3DTA%40mail.gmail.com > <https://groups.google.com/d/msgid/vagrant-up/CA%2BnFXPGKb-GqitT%2BzuVBQo1nPQEBW5punLZePtvec4DH6mb%3DTA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Alvaro -- 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/CAHqq0eyj_0anGEsNx9Djy-TvurqXUh_FESJd%2B631gsRwZbTPUA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
