This is outrageous, the official tutorial leads directly into this trap! 
How can that  possibly be? Just 
did https://www.vagrantup.com/docs/getting-started/synced_folders.html and 
run into same issue, was not able to solve until found this post.
>after "vagrant up", I hit "pwd" and got "/home/vagrant" and assumed that 
was the "/vagrant" mentioned in the docs. My mistake.
Not your, it is their mistake.

воскресенье, 15 декабря 2013 г., 6:46:10 UTC+7 пользователь Jeff Widman 
написал:
>
> Nope--I figured it out. 
>
> I didn't realize I should be looking at "/vagrant" rather than 
> "/home/vagrant"
>
> after "vagrant up", I hit "pwd" and got "/home/vagrant" and assumed that 
> was the "/vagrant" mentioned in the docs. My mistake.
>
>
>
>
> On Sat, Dec 14, 2013 at 2:42 PM, Teemu Matilainen <[email protected] 
> <javascript:>> wrote:
>
>> Jeff,
>>
>> I don't see anything strange in that log. One thing that you could try is 
>> to restart the VM with `vagrant reload` (same as `vagrant halt; vagrant 
>> up`). Maybe the new drivers didn't kick in correctly (in which case it's a 
>> vagrant-vbguest issue as it should have restarted the VM).
>>
>> -- 
>> Teemu
>>
>>
>>
>> On Sat, Dec 14, 2013 at 7:06 PM, Jeff Widman <[email protected] 
>> <javascript:>> wrote:
>>
>>> Just updated guest additions to match the host virtualbox version, but 
>>> the problem persists--/vagrant on guest and /[project] on host are not 
>>> syncing.
>>>
>>> The guest additions were updated by installing the vagrant-vbguest 
>>> plugin (thanks for pointing me toward that Teemu).
>>>
>>> Here's an updated gist with the new log output using the "debug" option: 
>>> https://gist.github.com/jeffwidman/3549a6f07ec8768dac15
>>>
>>>
>>> On Sat, Dec 14, 2013 at 12:52 PM, Jeff Widman <[email protected] 
>>> <javascript:>> wrote:
>>>
>>>> Here you go Teemu:
>>>>
>>>> https://gist.github.com/jeffwidman/c9e145a70bae2dd5c8ba
>>>>
>>>> As I mentioned, I suspect it's an issue with latest Virtualbox being 
>>>> 4.3.4 and guest additions packaged in the precise32 box being Vbox 4.2.0
>>>>
>>>>
>>>>
>>>> On Saturday, December 14, 2013 12:35:32 PM UTC-8, Teemu Matilainen 
>>>> wrote:
>>>>
>>>>> Hi Jeff,
>>>>>
>>>>> Please gist 
>>>>> <https://www.google.com/url?q=https%3A%2F%2Fgist.github.com&sa=D&sntz=1&usg=AFQjCNGbQPJUwexo1pHRYrizhfMG1_9Z_A>
>>>>>  
>>>>> your Vagrantfile and debug output 
>>>>> <http://docs.vagrantup.com/v2/other/debugging> of vagrant up.
>>>>>
>>>>> -- 
>>>>> Teemu
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Dec 14, 2013 at 4:46 PM, Jeff Widman <[email protected]> 
>>>>> wrote:
>>>>>
>>>>>> New to Vagrant and having an issue, as I walk through the Getting 
>>>>>> Started guide. 
>>>>>>
>>>>>> The sync'd folders aren't working by default:
>>>>>>
>>>>>> vagrant up
>>>>>> vagrant ssh
>>>>>>
>>>>>> "pwd" says /vagrant
>>>>>> touch foo
>>>>>> exit 
>>>>>>
>>>>>>  
>>>>>> Back on host machine, the project directory where the vagrant file 
>>>>>> resides shows no sign of foo. searching the rest of my computer also 
>>>>>> shows 
>>>>>> no sign of foo.
>>>>>>
>>>>>> I've reinstalled VirtualBox and Vagrant, and neither one fixed the 
>>>>>> issue. I'm on OSX Mountain Lion. The only change I made from the Getting 
>>>>>> Started guide was I used the precise64 box instead of the precise32.
>>>>>>
>>>>>> Any suggestions for how to better pinpoint the underlying issue and 
>>>>>> fix it? 
>>>>>>
>>>>>> Cheers,
>>>>>> Jeff
>>>>>>
>>>>>> -- 
>>>>>> 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].
>>>>>>
>>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>>
>>>>>
>>>>> -- 
>>>> 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/topic/vagrant-up/cSqm9qHtBDM/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to 
>>>> [email protected] <javascript:>.
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>
>>>
>>>
>>> -- 
>>> Jeff Widman
>>>
>>> 740-WIDMAN-J (943-6265)
>>> http://www.jeffwidman.com/
>>> <><
>>>
>>> -- 
>>> 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] <javascript:>.
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>> -- 
>> 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/topic/vagrant-up/cSqm9qHtBDM/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> -- 
> Jeff Widman
>
> 740-WIDMAN-J (943-6265)
> http://www.jeffwidman.com/
> <><
>

-- 
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/9ea5281c-a72a-49ee-acc0-694a6b35ba03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to