[Bug 1239417] Re: ls /vagrant fails in 13.10 vagrant cloud image

2013-12-31 Thread Julian Taylor
*** This bug is a duplicate of bug 1252872 *** https://bugs.launchpad.net/bugs/1252872 ** This bug has been marked a duplicate of bug 1252872 saucy vagrant image shared folder 'ls' blocks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1239417] Re: ls /vagrant fails in 13.10 vagrant cloud image

2013-12-20 Thread Lance Rushing
After re-reading the comments, I upgraded to 4.3 and shared folders are working now. Recap: I upgraded virtual box on the host machine to 4.3.6, and installed the 4.3.6 guest additions on the guest. Bug is closed (for me...). Thanks, Lance -- You received this bug notification because you

[Bug 1239417] Re: ls /vagrant fails in 13.10 vagrant cloud image

2013-11-08 Thread Lance Rushing
I've tested this further with pure virtual box (no vagrant) on windows7 Host and ubuntu 13.10 guest. Windows7 - Virtual Box - Version 4.2.18 r88780 I've installed the VBOXADDITIONS_4.2.18_88780 guest additions. Guest machine: $ uname -a Linux sandbox 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9

[Bug 1239417] Re: ls /vagrant fails in 13.10 vagrant cloud image

2013-11-07 Thread lautreamont33
I have same problem so I tested all newest vagrant-cloud-images on clean install of Ubuntu 13.10 on real (old) machine, so I could only testing i386 boxes. Precise and Raring works but Quantal and Saucy did not. Quantal did work after $ vagrant halt -f and $ vagrant up but not Saucy. Then I

[Bug 1239417] Re: ls /vagrant fails in 13.10 vagrant cloud image

2013-11-07 Thread lautreamont33
Forgot to mention, that I am also using vagrant-lxc plugin that has lxc boxes (no guest additions) and have this same error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239417 Title: ls /vagrant

[Bug 1239417] Re: ls /vagrant fails in 13.10 vagrant cloud image

2013-11-02 Thread Jakub Gocławski
This issue is VirtualBox (and kernel 3.11) related. Latest version of VirtualBox 4.3 fixes this error. https://www.virtualbox.org/changeset/48529/vbox Unfortunatelly, the newest version of VirtualBox isn't available in Ubuntu repos. You need to manually download and install it from here:

[Bug 1239417] Re: ls /vagrant fails in 13.10 vagrant cloud image

2013-11-02 Thread Jakub Gocławski
I assumed Ubuntu is used as a host machine, my bad. I now reread the original post and saw that Mac OS X is used. What I mean is that you need VirtualBox 4.3 Guest Additions on the guest Ubuntu 13.10, but official Ubuntu 13.10 box has only VirtualBox 4.2.16. Since the Guest Additions version

[Bug 1239417] Re: ls /vagrant fails in 13.10 vagrant cloud image

2013-11-01 Thread Lance Rushing
Steps to reproduce: # Install Vagrant / Virtual Box first $ vagrant box add saucy64 http://cloud-images.ubuntu.com/vagrant/saucy/current/saucy-server-cloudimg-amd64-vagrant-disk1.box $ vagrant init saucy64 $ vagrant up $ vagrant ssh ## in ssh connection... $ ls /vagrant -- You received this

[Bug 1239417] Re: ls /vagrant fails in 13.10 vagrant cloud image

2013-10-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239417 Title: ls /vagrant