{"action":"created","issue":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/6997","repository_url":"https://api.github.com/repos/mitchellh/vagrant","labels_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6997/labels{/name}","comments_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6997/comments","events_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6997/events","html_url":"https://github.com/mitchellh/vagrant/issues/6997","id":132019287,"number":6997,"title":"Can't get eth0 IP address to stick when using Vagrant+VMware Fusion","user":{"login":"wchrisjohnson","id":5418,"avatar_url":"https://avatars.githubusercontent.com/u/5418?v=3","gravatar_id":"","url":"https://api.github.com/users/wchrisjohnson","html_url":"https://github.com/wchrisjohnson","followers_url":"https://api.github.com/users/wchrisjohnson/followers","following_url":"https://api.github.com/users/wchrisjohnson/following{/other_user}","gists_url":"https://api.github.com/users/wchrisjohnson/gists{/gist_id}","starred_url":"https://api.github.com/users/wchrisjohnson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wchrisjohnson/subscriptions","organizations_url":"https://api.github.com/users/wchrisjohnson/orgs","repos_url":"https://api.github.com/users/wchrisjohnson/repos","events_url":"https://api.github.com/users/wchrisjohnson/events{/privacy}","received_events_url":"https://api.github.com/users/wchrisjohnson/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mitchellh/vagrant/labels/bug","name":"bug","color":"e11d21"},{"url":"https://api.github.com/repos/mitchellh/vagrant/labels/provider/vmware","name":"provider/vmware","color":"bfe5bf"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-07T22:03:21Z","updated_at":"2016-02-08T20:08:53Z","closed_at":null,"body":"I have a question about the way that vagrant/fusion works the first time a vm is brought up with \"vagrant up\". eth0 is the internal NIC that vagrant uses for SSH access to the VM. Each time I create a new VM, this IP gets its 4th octet incremented. So, if that nic is using 172.16.255.x, the first time it will come up as 172.16.255.128. If I then destroy the VM and create a new one (\"vagrant up\"), it will get an eth0 IP of 172.16.255.129, the next time x.x.x.130, and so on.\r\n\r\nI'm using Ansible to provision my devstack/openstack work, and I would really like to be able to count on that IP address being the SAME every time I \"vagrant up\". I tried to use this in the Vagrantfile:\r\n\r\n...\r\n  config.vm.network \"private_network\", ip: \"172.16.255.128\",\r\n     auto_config: false\r\n...\r\n\r\nbut no luck.\r\n\r\nIt doesn't appear that vagrant or Fusion is going to allow me to \"stick\" that IP address. If all else fails, I suppose I will have to auto detect and regenerate my Ansible inventory file every time I provision my VM, but I'd really prefer being able to just set it and forget it in my configuration.\r\n\r\nThanks in advance for any background I'm missing here.\r\n\r\nChris"},"comment":{"url":"https://api.github.com/repos/mitchellh/vagrant/issues/comments/181546129","html_url":"https://github.com/mitchellh/vagrant/issues/6997#issuecomment-181546129","issue_url":"https://api.github.com/repos/mitchellh/vagrant/issues/6997","id":181546129,"user":{"login":"phinze","id":37534,"avatar_url":"https://avatars.githubusercontent.com/u/37534?v=3","gravatar_id":"","url":"https://api.github.com/users/phinze","html_url":"https://github.com/phinze","followers_url":"https://api.github.com/users/phinze/followers","following_url":"https://api.github.com/users/phinze/following{/other_user}","gists_url":"https://api.github.com/users/phinze/gists{/gist_id}","starred_url":"https://api.github.com/users/phinze/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/phinze/subscriptions","organizations_url":"https://api.github.com/users/phinze/orgs","repos_url":"https://api.github.com/users/phinze/repos","events_url":"https://api.github.com/users/phinze/events{/privacy}","received_events_url":"https://api.github.com/users/phinze/received_events","type":"User","site_admin":false},"created_at":"2016-02-08T20:08:53Z","updated_at":"2016-02-08T20:08:53Z","body":"Hi @wchrisjohnson - thanks for the report!\r\n\r\nHave you tried leaving `auto_config` off of the private network options?\r\n\r\nThis `Vagrantfile` seems to be working for me in local testing:\r\n\r\n```ruby\r\nVagrant.configure(2) do |config|\r\n  config.vm.box = \"hashicorp/precise64\"\r\n  config.vm.network \"private_network\", ip: \"172.16.255.128\"\r\nend\r\n```\r\n\r\n(Note: I recommend upgrading [to the fresh release I just cut today](https://github.com/hashicorp/vagrant-plugin-changelog/blob/master/vagrant-vmware-changelog.md#407-february-8-2016), which has a fix for a bad option default that was release in 4.0.6.)"}}