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 tested on clean install of Ubuntu 12.04 same boxes and everything was same except that Saucy has no errors. But when I ssh in to it mounted vagrant directory was unreadable. When I replace guest additions with 4.3.0 everything works. Tested with VB 4.3.0 and vagrant 1.3.5. This might tell as that guest additions must be right version but they are not on Precise and Raring and they work from the box (really from .box). From debug.logs you can see that vagrant can not establish ssh connection with booted VM. On newest vagrant version there is big delay (2-3sec) on establishing ssh connection so I think that they work in that direction. -- 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 fails in 13.10 vagrant cloud image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1239417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
