From 0f78c008044a9eaa589ec9268496b547893e2428 Mon Sep 17 00:00:00 2001 From: Dongsu Park Date: Wed, 12 Feb 2020 12:49:44 +0100 Subject: [PATCH] systemd: check both OEM IDs for flatcar and coreos For backwards compatibilities, we need to check both OEM IDs in the kernel command line, `flatcar.oem.id` and `coreos.oem.id`. --- systemd/network/yy-azure-sriov-coreos.network | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 systemd/network/yy-azure-sriov-coreos.network diff --git a/systemd/network/yy-azure-sriov-coreos.network b/systemd/network/yy-azure-sriov-coreos.network new file mode 100644 index 0000000..f147318 --- /dev/null +++ b/systemd/network/yy-azure-sriov-coreos.network @@ -0,0 +1,15 @@ +# Ignore SR-IOV interface on Azure, since it'll be transparently bonded +# to the synthetic interface + +[Match] +KernelCommandLine=coreos.oem.id=azure +# With NetworkManager, Azure uses a udev rule matching DRIVERS=="hv_pci". +# This won't work with networkd because it only checks the driver of the +# device itself, not its parents. All we can do instead is blacklist the +# VF driver currently used in Azure. If other drivers come into use, the +# symptom will be a VF interface in the output of "networkctl" which never +# finishes configuring. +Driver=mlx4_en + +[Link] +Unmanaged=yes