Locating the shared folder

74 views
Skip to first unread message

Patrick Bass

unread,
Jul 23, 2015, 11:19:58 AM7/23/15
to Vagrant
Hi,

I'm using Vagrant for the first time and I had to read many tutorials before I can be able to set up Vagrant in VirtualBox of my Windows 7 OS. Now, after trying to run the command "mv main/ /vagrant" so that I can have a look to /main folder I previously retrieved from cloning a repository via git, this error message is being returned: "permission denied, cannot move 'main/' to '/vagrant'". I tried to run ''ls -ld /vagrant", it returned: "ls: cannot access /vagrant: No such file or directory". Could it be that the shared folder between windows and Vagrant isn't /Vagrant? If so, how can I locate that folder? Any suggestions, please? 

Thanks

Alvaro Miranda Aguilera

unread,
Jul 23, 2015, 5:19:48 PM7/23/15
to vagra...@googlegroups.com
hello,

seems your guest is on linux

Assuming your Vagrantfile hasn't disabled this folder, then you can
check the mount point like:

mount
or
df

If the /vagrant mountpoint has stalled.. a vagrant reload should fix it.
> --
> 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 vagrant-up+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/4d5c9650-9ae8-4cc1-b375-2b41d48c1a55%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Patrick Bass

unread,
Jul 27, 2015, 2:52:27 PM7/27/15
to Vagrant, comput...@gmail.com
Thanks Alvaro for taking time to answer. Actually I'm a newbie both on Linux and Vagrant, so could you please clarify your answer? Do you mean that I should run those that seem to me as commands, if so please provide the entire commands if you don't mind. Thanks in advance. 

Alvaro Miranda Aguilera

unread,
Jul 27, 2015, 6:15:38 PM7/27/15
to vagra...@googlegroups.com, comput...@gmail.com
Hello,

Can you paste here your Vagrantfile?


The commands you need to run that I did suggest were:

vagrant ssh
sudo df -h
sudo mount

you can paste that result here too

Thanks
> --
> 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 vagrant-up+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/92e954e1-a766-4ef0-a357-6d265aa3f8b1%40googlegroups.com.

Patrick Bass

unread,
Jul 29, 2015, 1:50:33 PM7/29/15
to Vagrant, comput...@gmail.com
Thanks, Alvaro, for your answer, and sorry for delay. Please find below the ouputs from the commands you asked me to run and other informations:


Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-55-generic x86_64)


55 packages can be updated.
30 updates are security updates.


vagrant@vagrant-ubuntu-trusty-64:~$ vagrant ssh

The program 'vagrant' is currently not installed. To run 'vagrant' please ask your administrator to install the package 'vagrant'
vagrant@vagrant-ubuntu-trusty-64:~$ sudo df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        40G  2.0G   36G   6% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
udev            240M   12K  240M   1% /dev
tmpfs            49M  344K   49M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            245M     0  245M   0% /run/shm
none            100M     0  100M   0% /run/user

vagrant@vagrant-ubuntu-trusty-64:~$ sudo mount

/dev/sda1 on / type ext4 (rw)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)


Le jeudi 23 juillet 2015 16:19:58 UTC+1, Patrick Bass a écrit :

Alvaro Miranda Aguilera

unread,
Jul 29, 2015, 7:41:35 PM7/29/15
to vagra...@googlegroups.com, Patrick Bass
On Thu, Jul 30, 2015 at 5:50 AM, Patrick Bass <comput...@gmail.com> wrote:
> 14.04.2 LTS

Hello,

Thanks for the info

Well, the /vagrant is not mounted, this can be by several reasons. One
of them is in some new kenels are some issues, with vmware tools, and
a long etc.

So, can you test this box:

mkdir precise64
cd precise64
vagrant init -m hashicorp/precise64
vagrant up

Can you share the outlog log in a gist (gist.github.com) and repeat
the same commands?

If the commands works as I expect, my recommendation will be test
other ubuntu box, or create your very own with packer (packer.io)

Thanks
Alvaro.

dragon788

unread,
Aug 4, 2015, 2:15:38 PM8/4/15
to Vagrant, comput...@gmail.com
You can also use 'lsmod | grep vm' and if it doesn't return the vmhgfs module with a count higher than 0 (or it doesn't show up) then Alvaro is correct and it hasn't loaded the driver/module correctly. This is frequently an issue if you are using newer than 3.13.0-37 of the Linux kernel, they made some minor changes there that broke the VMware Tools installs horribly.
Reply all
Reply to author
Forward
0 new messages