Just confirming that this also occurs on a KVM virtual machine, in my case I was using 'virt-clone' to clone a system, which changes the MAC addr... on boot of the clone you have eth0 moved to eth1 due to the persistent udev rule entries.
Just confirming that this also occurs on a KVM virtual machine, in my case I was using 'virt-clone' to clone a system, which changes the MAC addr... on boot of the clone you have eth0 moved to eth1 due to the persistent udev rule entries.