Fixing this in udev will cause issues like reported in #431190. The persistent-net udev rules are not created in virtual environments to avoid issues with cloning/migrating VMs.
I was also unable to reproduce the issue on a VMware ESX server VM, despite the fact that no net udev rules are created. And why it happens with Hyper-V only in kernel 3.16, not 3.2 or 4.2?
