So Vmware called me actually and told me flat out Vmware 14 does not work 
with vagrant.  They said I should downgrade to 12.

On Friday, November 3, 2017 at 8:27:06 AM UTC-4, Jacob Sherman wrote:
>
> Thanks Alvaro,
> So using the hashicorp/precise64 box vagrant times out on starting 
> VMware.  So I am at a loss except to contact VmWare support but I think 
> they will not help since I am using Vagrant.
>
> On Friday, November 3, 2017 at 6:11:37 AM UTC-4, Alvaro Miranda Aguilera 
> wrote:
>>
>> hello jacob
>>
>> try first a different box to ensure the setup is working properly
>>
>> hashicorp/precise64
>>
>> if this box works then we can assume is the box you are using.
>>
>> The directory that lucas is suggesting is
>>
>> ~/.vagrant.d/boxes
>>
>> being ~ your home directory
>>
>> inside that path you will see a directory for the base boxes (templates) 
>> if you check the box you are having issues you could see the lock file.
>>
>>
>> On Fri, Nov 3, 2017 at 2:23 AM, Jacob Sherman <[email protected]> 
>> wrote:
>>
>>> Lucas,
>>> Thanks for the reply.  I had read your post but first of all I don't see 
>>> a linked_clone line in my Vagrant file.
>>>
>>> I check the directory there is only a subdirectory named vmware_desktop 
>>> which has files only
>>> Very frustrating :(
>>>
>>> my Vagrantfile:
>>>  1  -*- mode: ruby -*-
>>>   2 # vi: set ft=ruby :
>>>   3 
>>>   4 require 'json'
>>>   5 require 'yaml'
>>>   6 
>>>   7 VAGRANTFILE_API_VERSION ||= "2"
>>>   8 confDir = $confDir ||= File.expand_path(File.dirname(__FILE__))
>>>   9 
>>>  10 homesteadYamlPath = confDir + "/Homestead.yaml"
>>>  11 homesteadJsonPath = confDir + "/Homestead.json"
>>>  12 afterScriptPath = confDir + "/after.sh"
>>>  13 aliasesPath = confDir + "/aliases"
>>>  14 
>>>  15 require File.expand_path(File.dirname(__FILE__) + 
>>> '/scripts/homestead.rb')
>>>  16 
>>>  17 Vagrant.require_version '>= 1.9.0'
>>>  18 
>>>  19 Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>>>  20     if File.exist? aliasesPath then
>>>  21         config.vm.provision "file", source: aliasesPath, 
>>> destination: "/tmp/bash_aliases"
>>>  22         config.vm.provision "shell" do |s|
>>>  23             s.inline = "awk '{ sub(\"\r$\", \"\"); print }' 
>>> /tmp/bash_aliases > /home/vagrant/.bash_aliases"
>>>  24         end
>>>  25     end
>>>  26 
>>>  27     if File.exist? homesteadYamlPath then
>>>  28         settings = YAML::load(File.read(homesteadYamlPath))
>>>  29     elsif File.exist? homesteadJsonPath then
>>>  30         settings = JSON.parse(File.read(homesteadJsonPath))
>>>  31     else
>>>  32         abort "Homestead settings file not found in #{confDir}"
>>>  33     end
>>>  34 
>>>  35     Homestead.configure(config, settings)
>>>  36 
>>>  37     if File.exist? afterScriptPath then
>>>  38         config.vm.provision "shell", path: afterScriptPath, 
>>> privileged: false
>>>  39     end
>>>  40 
>>>  41     if defined? VagrantPlugins::HostsUpdater
>>>  42         config.hostsupdater.aliases = settings['sites'].map { |site| 
>>> site['map'] }
>>>  43     end
>>>  44 end
>>>
>>>
>>>
>>> On Thursday, November 2, 2017 at 8:32:55 PM UTC-4, Lucas Rangit 
>>> Magasweran wrote:
>>>>
>>>> Jacob,
>>>>
>>>> This may be the same issue I had recently: 
>>>> https://groups.google.com/d/msg/vagrant-up/bHe04cJJMAE/hm49gqJIAgAJ
>>>>
>>>> Is there a *.vmx.lck directory in 
>>>> /home/devJacob/.vagrant.d/boxes/laravel-VAGRANTSLASH-homestead/4.0.0/ ?
>>>>
>>>> If so, you have to delete it. It should not have been included by the 
>>>> creator of the Vagrant box.
>>>>
>>>> If not, try setting "linked_clone = false" for your provider VM as a 
>>>> workaround so the VM is copied as opposed to linked.
>>>>
>>>> On Thursday, November 2, 2017 at 5:22:28 PM UTC-7, Jacob Sherman wrote:
>>>>>
>>>>> here is a gist of the debug file
>>>>> https://gist.github.com/NYCJacob/e7c8ee74a4b380860e5759001abf9ed8
>>>>>
>>>>> -- 
>>> 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/5b1fecd2-df31-408d-84fe-ff56801fb404%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/vagrant-up/5b1fecd2-df31-408d-84fe-ff56801fb404%40googlegroups.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/3235812e-f787-44db-bda3-ef14db5af643%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to