I posted on xen-devel, you can follow from :
https://lists.xenproject.org/archives/html/xen-devel/2023-08/msg00244.html
(Unfortunately, the formatting is weird via html, split the IRC part on
"- ").
Thank you for posting upstream.
Note that, at first sight, I was told this seems "not-a-Xen" bug (read
the IRC excerpts).
All documentation i found found on the Xen wiki suggests that interfaces
are connected vifX.Y <-> ethY. [0] [1]
The only other way i know of for identifying the interfaces are MAC
Addresses which can be randomly assigned if you don't configure them.
I also checked which net_ids udev knows about and the only things that
pop up are:
ID_NET_NAMING_SCHEME=v247
ID_NET_NAME_MAC=enx00163efd832b
ID_OUI_FROM_DATABASE=Xensource, Inc.
Either i am missing the way you're supposed to do this, or there is a
bug somewhere in the toolchain.
Unfortunately i'm not able to pinpoint the source of the issue, any help
would be appreciated.
Valentin
[0]
https://wiki.xenproject.org/wiki/Xen_Networking#Paravirtualised_Network_Devices
[1]
https://wiki.xenproject.org/wiki/Network_Throughput_and_Performance_Guide#Technical_Overview
