please include the kernel module VXLAN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-kvm (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Committed
|
Undecided
|
Po-Hsu Lin | ||
Bionic |
Fix Released
|
Undecided
|
Po-Hsu Lin | ||
Disco |
Fix Released
|
Undecided
|
Po-Hsu Lin |
Bug Description
== SRU Justification ==
VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes,
it will be great to enable the support in KVM kernels.
== Fix ==
Enable the CONFIG_VXLAN in the config file.
CONFIG_
updateconfigs.
CONFIG_
not requested (and to reduce the binary size).
== Test ==
Test kernels could be found here:
https:/
Kernel smoke tested.
User has also verified that all the patched kernels are working as
expected.
== Regression Potentail ==
Low, this enables the support for VXLAN module on KVM kernels, we might
see some related bugs in the future. Since we already have this in the
generic kernel so the impact should be small.
== Original Bug Report ==
The kernel built with this packages does have VXLAN compiled.
It would be nice if this could be fixed since VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes.
$ grep -i vxlan /boot/config-
# CONFIG_VXLAN is not set
When running a kubernetes cluster with Flannel with this image:
$ kubectl logs kube-flannel-
I0116 11:35:34.176962 1 main.go:475] Determining IP address of default interface
I0116 11:35:34.177231 1 main.go:488] Using interface with name ens3 and address 10.32.192.14
I0116 11:35:34.177259 1 main.go:505] Defaulting external address to interface address (10.32.192.14)
I0116 11:35:34.191358 1 kube.go:131] Waiting 10m0s for node controller to sync
I0116 11:35:34.273844 1 kube.go:294] Starting kube subnet manager
I0116 11:35:35.274075 1 kube.go:138] Node controller sync successful
I0116 11:35:35.274106 1 main.go:235] Created subnet manager: Kubernetes Subnet Manager - node-1-case1
I0116 11:35:35.274113 1 main.go:238] Installing signal handlers
I0116 11:35:35.274233 1 main.go:353] Found network config - Backend type: vxlan
I0116 11:35:35.274292 1 vxlan.go:120] VXLAN config: VNI=1 Port=0 GBP=false DirectRouting=false
E0116 11:35:35.275803 1 main.go:280] Error registering network: operation not supported
I0116 11:35:35.275860 1 main.go:333] Stopping shutdownHandler...
CVE References
description: | updated |
description: | updated |
Changed in linux-kvm (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
Changed in linux-kvm (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux-kvm (Ubuntu Disco): | |
status: | In Progress → Fix Committed |
Hello,
Can you give this test kernel a try? /people. canonical. com/~phlin/ kernel/ lp-1811819- vxlan/X/
https:/
Config changed in this kernel: OPENVSWITCH_ VXLAN is not set
+# CONFIG_GENEVE is not set
+# CONFIG_
-# CONFIG_VXLAN is not set
+CONFIG_VXLAN=m
$ sudo modprobe vxlan
$ lsmod | grep vxlan
vxlan 36864 0
ip6_udp_tunnel 12288 1 vxlan
udp_tunnel 12288 1 vxlan
Do you need this feature in other KVM kernels?
Thanks