-
Notifications
You must be signed in to change notification settings - Fork 1.1k
VMware Fusion 8
Seth Thomas edited this page Jul 3, 2017
·
1 revision
- If you're using the Vagrant VMWare Fusion provider, using
vagrant box add --provider vmware_desktop ...will work for these boxes. Using--provider vmware_fusion, will not.
Recent Linux distributions use systemd's logic to predictably name network devices. In our scenario, this is tied to the PCI slot id. For unknown reasons, boxes built with the default vmx config provided by packer use a different PCI slot id (32 instead of 33) once they got imported to VMWare Fusion 8, which results in a different device name and finally in broken networking. This issue is documented in the following places:
- https://github.com/chef/bento/issues/554
- https://github.com/chef/bento/pull/545#issuecomment-202988690
- https://github.com/mitchellh/vagrant/issues/4590
As a workaround we've started to provide the changed PCI slot id as a custom value with the packer definitions with Ubuntu 15.10+ and Debian 8+. However this is not yet tested, may not solve the issue and/or break compatibility with other VMWare products/versions!