Hi
If you are in the latest version of vagrant and plugin, and still have this
issue, please email supp...@hashicorp.com
it should be fixed already.
As work around, you can use
config.vm.provider :vmware_fusion do |vmware|
vmware.vmx["ethernet0.pcislotnumber"] = "33"
end
On Wed, Jan 25, 2017 at 9:26 PM, railed mail <railedm...@gmail.com> wrote:
> host is osx. using packer to pack an ubuntu 16.04 box and vagrant up-ing
> on osx
>
>
> On Jan 25, 2017, at 13:59, Alvaro Miranda Aguilera <kiki...@gmail.com>
> wrote:
>
> hello
>
> what os do you use?
>
> The easier way is just make ens32 and ens33 as dhcp
>
> so whatever it gets will just work.
>
> source and destination VM are just vagrant boxes?
>
>
>
> On Wed, Jan 25, 2017 at 7:36 PM, <railedm...@gmail.com> wrote:
>
>> I'm creating a base box. My provider is vmware-iso (fusion).
>>
>> After creating and vagrant up-ing the box I'm noticing how vmware (as
>> expected) is generating a new mac address for the new linked cloned VM.
>>
>> However during packing I have a different mac address (prior to cloning)
>> and therefor the interface name address that gets generated
>> /etc/network/interfaces will be wrong
>>
>> e.g.,
>>
>> during packing
>>
>> ifconfig -a | grep ens
>> ens32
>>
>> during vagrant up
>>
>> ifconfig -a | grep ens
>> ens33
>>
>> When running vagrant up I allow the GUI to start so I can manually login
>> and verify that the mac address is indeed different from when I was packing
>> the base box. I have a couple of kludgy hacks to do a work around (i.e.,
>> running scripts and using hardcoded mac address to "bootstrap" the
>> networking) but Ideally I'd like to just have linked clones have the same
>> work flow as virtualbox provider does, i.e., "it just works" -> vagrant up,
>> VM clones, VM gets an IP, vagrant ssh works.
>>
>> One more thing, I know I can send boot params to during the packing phase
>> to get ye ole ethX but is there something I can put in a vagrantfile that
>> would also do that? I would be ok with having the interface always come up
>> as eth0 and then during the first provision configure the name of the
>> interface on next boot via udev persistent rules.
>>
>> Thanks for the help
>>
>> --
>> 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 vagrant-up+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/vagrant-up/7d37fe6f-5286-49ec-a70c-7282b93d171a%40googlegroups.com
>> <https://groups.google.com/d/msgid/vagrant-up/7d37fe6f-5286-49ec-a70c-7282b93d171a%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 a topic in the
> Google Groups "Vagrant" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/vagrant-up/HCNM8n7lAfA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/CAHqq0exB7k4xFGuA7c_Zt_oCxWAG8De560k0pKEH6DXqnSu1eA%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0exB7k4xFGuA7c_Zt_oCxWAG8De560k0pKEH6DXqnSu1eA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/3B2AB6F8-5536-45CF-BD96-6FB68147EEBC%40gmail.com
> <https://groups.google.com/d/msgid/vagrant-up/3B2AB6F8-5536-45CF-BD96-6FB68147EEBC%40gmail.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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyHb1JN1bhWNOcCTRhOK0EGpPhCofnFFPDkk69OuwTmZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
