Bug#810247: RE: Bug#810247: Hyper-V network adapters are mapped to a different interface (ethN) on every boot

Thanks Michael. I have reported it upstream: https://github.com/systemd/systemd/issues/8652 Fernando -Original Message- From: Michael Biebl [mailto:bi...@debian.org] Sent: Saturday, March 24, 2018 5:25 PM To: 810...@bugs.debian.org; Martin Pitt <mp...@debian.org>; Fernando Sot

Bug#810247: Hyper-V network adapters are mapped to a different interface (ethN) on every boot

Hi Martin, Udevadm output is attached. Thank you, Fernando > -Original Message- > From: Martin Pitt [mailto:mp...@debian.org] > Sent: Saturday, January 09, 2016 10:45 AM > To: Fernando Soto; 810...@bugs.debian.org > Subject: Re: Bug#810247: Hyper-V network adap

Bug#810247: Hyper-V network adapters are mapped to a different interface (ethN) on every boot

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