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

[Fernando Soto]

Thanks Michael.
I have reported it upstream:
https://github.com/systemd/systemd/issues/8652

Fernando

-----Original Message-----
From: Michael Biebl [mailto:biebl at debian.org] 
Sent: Saturday, March 24, 2018 5:25 PM
To: 810247 at bugs.debian.org; Martin Pitt <mpitt at debian.org>; Fernando Soto <fsoto at bluecatnetworks.com>
Subject: Re: RE: Bug#810247: Hyper-V network adapters are mapped to a different interface (ethN) on every boot

On Sat, 9 Jan 2016 17:20:26 +0000 Fernando Soto <fsoto at bluecatnetworks.com> wrote:
> Hi Martin,
> 
> Udevadm output is attached.
> 
> Thank you,
> Fernando
> 
> > -----Original Message-----
> > From: Martin Pitt [mailto:mpitt at debian.org]
> > Sent: Saturday, January 09, 2016 10:45 AM
> > To: Fernando Soto; 810247 at bugs.debian.org
> > Subject: Re: Bug#810247: Hyper-V network adapters are mapped to a 
> > different interface (ethN) on every boot
> > 
> > Control: tag -1 moreinfo
> > 
> > Fernando Soto [2016-01-08 15:22 +0000]:
> > > The persistent-net udev rules are not created in virtual 
> > > environments to avoid
> > issues with cloning/migrating VMs.
> > 
> > This was true with the old persistent names in Jessie and before, 
> > but not true any more with current testing and unstable versions. 
> > See /usr/share/doc/udev/README.Debian.gz.
> > 
> > Maybe the current ifnames system cannot figure out an appropriate 
> > name for Hyper-V interfaces?


P:
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_0_16/net/eth0
E:
DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_0_16/net/eth0
E: ID_NET_DRIVER=hv_netvsc
E: ID_NET_NAME_MAC=enx00155d0ae2ad
E: ID_OUI_FROM_DATABASE=Microsoft Corporation
E: ID_PATH=acpi-VMBUS:01
E: ID_PATH_TAG=acpi-VMBUS_01
E: IFINDEX=2
E: INTERFACE=eth0
E: MATCHDEVID=0x0
E: MATCHIFTYPE=1
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0
E: TAGS=:systemd:
E: USEC_INITIALIZED=39002

Looks like this is the case.
I notice that there is

Author: Hannes Reinecke <hare at suse.de>
Date:   Fri Nov 23 14:12:39 2012 +0100

    udev: path_id - handle Hyper-V devices

    Hyper-V has an abstract bus, which gets renumbered on guest
    startup. So instead of the bus numbers we should be using
    the device GUIDs, which can be retrieved from the 'device_id'
    sysfs attribute.


That doesn't seem to handle network interfaces though.

That said, this doesn't look like a Debian specific problem. So it's probably best if you raise this upstream at https://github.com/systemd/systemd

--
Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?