network configuration (Ubuntu 14.04.x)

[till]

I configured an IP (static) in my Vagrantfile which seems to work fine with the virtualbox provider:

  config.vm.network :private_network, ip: '33.33.33.160'

When I start the box with App Catalyst, it assigns itself another IP:

==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 192.168.38.141:22
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!

The IP seems to be from my LAN's DHCP pool.

In contrast, the log with virtualbox would show a tunnel via 127.0.0.1:2222, which I think Vagrant is unable to setup because the IP address defined in the Vagrantfile does not match the expected value of 33.33.33.160.

This also seems to lead to shared folders not being mounted:

Unattended code received 500: VIX Error: There was an error mounting the Shared Folders file system inside the guest operating system, code: 20050, operation: vm.EnableSharedFolders

Any thoughts what I can do to debug this?

[till]

I was kind of too fast when I opened this.

I have to add that when I remove the network configuration, shared folders still do not work. So this issue is unrelated. But if anyone had any thoughts, I would appreciate pointers as well.

Thanks!

[till]

RE: networks shares: I had previously used the open-vm-tools (from the official Ubuntu repo) before and since I updated those to 9.9.3.47419 (build-2759765), my shares work fine. Maybe the provider could check if the tools are installed and at a version that works with AppCatalyst?

---

The IP related issue is still present.

[frapposelli]

@till the open-vm-tools package from the Ubuntu repo may or may not contain shared folders support compiled in, hence the error, the situation is now changing with VMware Tools 10 but if you're running a Linux distro that is not bleeding edge my advice is to stick to the VMware Tools package we provide with our products.

Private networks are not currently supported by the plugin, I'm working on a new improved version that will support private networks and will be released before the end of the year.

[till]

@frapposelli I couldn't find 10 for trusty (LTS), but it seems to work with 9.9.3.etc.pp. It seemed like the repository offered by VMware does not contain trusty anymore?

Probably not the scope of this "provider", but is there a command that shows capabilities of the VM? E.g. shared folders, private networking, etc.?

Thanks for the heads up on the private networking.

[Xe]

What Ubuntu vagrant box were you using?

[till]

@Xe I rolled my own: https://atlas.hashicorp.com/ies/boxes/vagrant-ubuntu_14.04.3-chef_11.10.4

My packer templates are here: https://github.com/easybiblabs/packer-templates

[Xe]

==> gantry-test-2: Adding box 'ies/vagrant-ubuntu_14.04.3-chef_11.10.4' (v2.0.9) for provider: vmware_desktop   
==> gantry-test-2: Importing base box 'ies/vagrant-ubuntu_14.04.3-chef_11.10.4'...                              
    gantry-test-2: Cloning VM, this might take a while...                                                       
==> gantry-test-2: Checking if box 'ies/vagrant-ubuntu_14.04.3-chef_11.10.4' is up to date...                   
==> gantry-test-1: Checking if box 'ies/vagrant-ubuntu_14.04.3-chef_11.10.4' is up to date...                   
==> gantry-test-2: An error occurred. The error will be shown after all tasks complete.                         
==> gantry-test-1: An error occurred. The error will be shown after all tasks complete.                         
An error occurred while executing multiple actions in parallel.                                                 
Any errors that occurred are shown below.                                                                       

An error occurred while executing the action on the 'gantry-test-1'                                             
machine. Please handle this error then try again:                                                               

Power on was canceled, make sure the VM you're trying to power on does not violate AppCatalyst constraints.     

An error occurred while executing the action on the 'gantry-test-2'                                             
machine. Please handle this error then try again:                                                               

Power on was canceled, make sure the VM you're trying to power on does not violate AppCatalyst constraints.

My Vagrantfile:

# Set our default provider for this Vagrantfile to 'vmware_appcatalyst'
ENV['VAGRANT_DEFAULT_PROVIDER'] = 'vmware_appcatalyst'

nodes = [
    { hostname: 'gantry-test-1', box: 'hashicorp/precise64' },
    { hostname: 'gantry-test-2', box: 'hashicorp/precise64',  }
]

Vagrant.configure('2') do |config|

    # Configure our boxes with 1 CPU and 384MB of RAM
    config.vm.provider 'vmware_appcatalyst' do |v|
        v.cpus = '1'
        v.memory = '512'
    end

    # Go through nodes and configure each of them.j
    nodes.each do |node|
        config.vm.define node[:hostname] do |node_config|
            node_config.vm.box = node[:box]
            node_config.vm.hostname = node[:hostname]
            node_config.vm.network :private_network, ip: '33.33.33.160'
            node_config.vm.synced_folder('/Users/xena/Code', '/home/xena/code')
        end
    end
end

_  vagrant ssh gantry-test-1                                                  
Welcome to Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-virtual x86_64)             

 * Documentation:  https://help.ubuntu.com/                                   
Last login: Thu Jan 31 13:48:53 2013                                          
vagrant@gantry-test-1:~$ ifconfig                                             
eth0      Link encap:Ethernet  HWaddr 00:0c:29:35:3f:18                       
          inet addr:172.16.143.133  Bcast:172.16.143.255  Mask:255.255.255.0  
          inet6 addr: fe80::20c:29ff:fe35:3f18/64 Scope:Link                  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1                  
          RX packets:758 errors:0 dropped:0 overruns:0 frame:0                
          TX packets:470 errors:0 dropped:0 overruns:0 carrier:0              
          collisions:0 txqueuelen:1000                                        
          RX bytes:88326 (88.3 KB)  TX bytes:71766 (71.7 KB)                  

lo        Link encap:Local Loopback                                           
          inet addr:127.0.0.1  Mask:255.0.0.0                                 
          inet6 addr: ::1/128 Scope:Host                                      
          UP LOOPBACK RUNNING  MTU:16436  Metric:1                            
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0                  
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0                
          collisions:0 txqueuelen:0                                           
          RX bytes:680 (680.0 B)  TX bytes:680 (680.0 B)                      

vagrant@gantry-test-1:~$ logout                                               
Connection to 172.16.143.133 closed.                                          

I'm not seeing the IP address being on my home network (I run a 10../8), but I am seeing the behavior that the configured IP address is not being set.

I think this issue name may need to be changed to "Private networking doesn't work" or some similar thing to that.

[khromov]

@frapposelli Any news on private_network support for AppCatalyst in Vagrant?