diff options
| author | Alex Kudentsov <43482574+alexk37@users.noreply.github.com> | 2026-10-14 20:45:45 +0700 |
|---|---|---|
| committer | Christian Breunig <christian@breunig.cc> | 2026-10-31 09:58:29 +0000 |
| commit | 639d575ad258f6f6ba629a0c50a710b736e4911d (patch) | |
| tree | ed62f4f285fd487d10c80c80e900dfb2637ce609 /interface-definitions/include/haproxy/logging.xml.i | |
| parent | 2c4b01409a625605009b6e6b29046723a4b2bd57 (diff) | |
| download | vyos-1x-639d575ad258f6f6ba629a0c50a710b736e4911d.tar.gz vyos-1x-639d575ad258f6f6ba629a0c50a710b736e4911d.zip | |
interfaces: T3871: keep an accelerated-networking VF off its NIC's .link file
On Azure every Hyper-V NIC shares one ID_PATH and has no slot, so it is
keyed on its MAC. Its accelerated-networking VF carries the same MAC and
matched the NIC's .link file, so udev tried to give the VF the NIC's name.
The .link file of a Hyper-V NIC now also matches Driver=hv_netvsc, so the
VF cannot match it. This holds for a lone NIC keyed on the VMBus path too.
A NIC absent at a pass cannot say what it is, so its file keeps the pin
it already carries. NICs that are not Hyper-V ones get no Driver line, and
their files do not change. The 34-to-35 migration passes the hardware it
found, so the pin is written on the first boot of an upgrade too.
Diffstat (limited to 'interface-definitions/include/haproxy/logging.xml.i')
0 files changed, 0 insertions, 0 deletions