Issue with Consistent Network Device Naming on CentOS 7

[Xylakant]

CentOS 7 now defaults to using Consistent Network Device Naming and thus is affected by the same issues as Fedora. Issue #1997 describes the problem in detail and has a PR attached that applies the fixes for fedora, the same fixes might work for CentOS, so deferring there for a detailed description. RHEL7 is probably affected in the same way.

[vStone]

@Xylakant: I created https://github.com/vStone/vagrant-centos7_fix as a temp workaround.

[nickchappell]

@vStone's workaround does the trick for me (OS X 10.9.3 host, CentOS 7 64-bit box, Vagrant 1.6.3). Any updates on fixing the underlying cause, either here or in #1997?

[vStone]

I can probably forge a pull request that does pretty much the same as the workaround later today.

[mitchellh]

Fixed by #4195

[misheska]

I'm still seeing an issue when the network interfaces are using the new-style names on CentOS 7. I'm using the image 'box-cutter/centos7' on vagrantcloud. No issues with VirtualBox and public networks, only with VMware Fusion. Though my image is using the new-style network addresses. Here' s the output of ls /sys/class/net:

ls /sys/class/net | grep -v lo
ens32
ens33

No eth0 or eth1, but again, this works fine on VirtualBox.