vagarant will do aport forward 222 to guest 22

so you should be able to do  ssh vagrant@localhost -p 2222

and, you should be able to set gui to true, and use the gui,



On Tue, Mar 11, 2014 at 12:59 PM, Michael Moscardini <moscardin...@gmail.com
> wrote:

> Hoping someone can help me out.  Are these the correct steps?
>
> I just tried creating a new VM on the host machine, set up with just a
> single network interface with NAT and I still can't get SSH to connect
> using 10.9.2 Host, Vagrant 1.4.3, Vagrant Fusion Plugin 2.3.4, and 10.9.2
> Guest.
>
> Are their any guides or directions for setting this stuff up on Mavericks
> host/guest?  Were my above steps correct?
>
> Thanks,
>   Mike
>
> On Monday, February 24, 2014 4:23:33 PM UTC-5, Mike Moscardini wrote:
>>
>> Thanks Mitchell,
>>
>> I tried a few things but still can't get it to work.  Maybe my steps are
>> incorrect.
>>
>> Mac OS 10.9.1 Host
>> Vagrant 1.4.3
>> Vagrant Fusion Plugin 2.3.1
>> Fusion 6.0.2
>> Mac OS 10.9.1 Guest
>>
>> In VMWare fusion, I created two network interfaces for my VM.  The first
>> network configuration is just NAT.  The other network interface is a bridge
>> to ethernet, with a specific mac address.  I booted up the VM and
>> configured the network and confirmed that both network interfaces are
>> working.  I shutdown the VM, and then created a box from this.
>>
>> I installed the box, and my vagrant file now looks like this:
>>
>> Vagrant.configure("2") do |config|
>>   config.vm.box = "mavericks"
>>   config.vm.guest = "darwin"
>>   config.vm.network "public_network", :mac => "<macaddress>"
>>   config.ssh.host = "<dns name>"
>>   config.vm.provider "vmware_fusion" do |v|
>>     v.gui = true
>>   end
>>
>> When the VM boots, neither of my network interfaces are connected and
>> vagrant can't detect that the VM is up.  I also get a prompt in the network
>> preferences to add some new device interfaces.  Were these the corrects
>> steps for creating the network interfaces on the VM?
>>
>>  - Mike
>>
>> On Friday, January 31, 2014 2:45:04 PM UTC-5, Mitchell Hashimoto wrote:
>>>
>>> Michael,
>>>
>>> I'm not sure how your old VM worked but the reason the new one isn't
>>> working is probably because you need to configure the OS too. I apologize
>>> if you know this already, but it is very relevant if you don't: simply
>>> adding a network adapter won't cause the OS to magically configure it
>>> properly.
>>>
>>> In fact, there is a much easier way to do this. Vagrant will
>>> automatically make the first network device a NAT, so you can ignore that.
>>> To make a static IP, you can use the `config.vm.network "public_network"`
>>> option. See here: http://docs.vagrantup.com/v2/networking/public_
>>> network.html
>>>
>>> Best,
>>> Mitchell
>>>
>>>
>>> On Thu, Jan 30, 2014 at 7:41 PM, Michael Moscardini <moscar...@gmail.com
>>> > wrote:
>>>
>>>> Old Environment:
>>>>
>>>> Mac OS 10.8.5 Host
>>>> Vagrant 1.3.1
>>>> Vagrant Fusion Plugin 2.0.4
>>>> Fusion 5.0.3
>>>> Mac OS 10.8.5 Guest
>>>>
>>>> New Environment:
>>>>
>>>> Mac OS 10.9.1 Host
>>>> Vagrant 1.4.3
>>>> Vagrant Fusion Plugin 2.2.8
>>>> Fusion 6.0.2
>>>> Mac OS 10.9.1 Guest
>>>>
>>>> I am trying to create an updated mac vagrant environment.  The VM
>>>> running on the host acts as a build agent for our CI system.  Because of
>>>> this I need the VM to have it's own mac address and IP address to get onto
>>>> our internal network.
>>>>
>>>> The old environment Vagrant file looks like this:
>>>>
>>>> Vagrant.configure("2") do |config|
>>>>   config.vm.box = "macbuld10-8-5"
>>>>   config.vm.guest = "darwin"
>>>>   config.vm.network "public_network"
>>>>   config.ssh.host = "<dns name>"
>>>>   config.vm.provider "vmware_fusion" do |v|
>>>>     v.gui = true
>>>>     v.vmx["ethernet0.connection"] = "nat"
>>>>     v.vmx["ethernet0.linkStatePropagation.enable"] = "TRUE"
>>>>     v.vmx["ethernet1.linkStatePropagation.enable"] = "TRUE"
>>>>     v.vmx["ethernet1.addressType"] = "static"
>>>>     v.vmx["ethernet1.generatedAddress"] = nil
>>>>     v.vmx["ethernet1.generatedAddressOffset"] = nil
>>>>     v.vmx["ethernet1.address"] = "00:50:56:2E:48:47"
>>>>     v.vmx["ethernet1.connectionType"] = "bridged"
>>>>     v.vmx["memsize"] = "3588"
>>>>     v.vmx["numvcpus"] = "2"
>>>>   end
>>>>
>>>> It's been a while since I set this up, and this was my first attempt at
>>>> using vagrant (I am an iOS developer).  I believe the point of this
>>>> configuration was to create a two network interfaces.  Ethernet0 uses nat
>>>> and this is what the Host uses to connect to over ssh.  The second
>>>> interface adds a public IP that the CI server can access.  I did this
>>>> because I didn't feel like trying to get port forwarding to work.
>>>>
>>>> I tried to use this configuration with the new setup and instead I got
>>>> no network at all.  I tried this <https://coderwall.com/p/_meqfg> 
>>>> configuration
>>>> and also got no network.  When I remove all of the vmx stuff, and just try
>>>> to use a private network through config.vm.network, I again get no network
>>>> inside the VM.  I am also unsure why when I modify ethernet0 and ethernet1
>>>> that It would be showing me that my network network interfaces are en2 and
>>>> en3.
>>>>
>>>> Old VM:
>>>>
>>>>
>>>> <https://lh5.googleusercontent.com/-d9foxBqXVec/UuqbZdC9TSI/AAAAAAAAAMk/JHx2aBzUr2I/s1600/oldvm.png>
>>>> New VM:
>>>>
>>>>
>>>> <https://lh5.googleusercontent.com/-H7kw-WFA4MA/UuqbfqTUWXI/AAAAAAAAAMs/67PlkaW_2cU/s1600/newvm.png>
>>>>
>>>> And I missing something?  Is there an easier way to do this?
>>>>
>>>> --
>>>> 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.
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>
>>>  --
> 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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to