** Changed in: linux-kvm (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux-kvm (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-kvm (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-kvm (Ubuntu Groovy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1899832
Title:
CONFIG options for (ipip, sit) should not be built-in to the KVM
kernels
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-kvm source package in Xenial:
Fix Committed
Status in linux-kvm source package in Bionic:
Fix Committed
Status in linux-kvm source package in Focal:
Fix Committed
Status in linux-kvm source package in Groovy:
Fix Committed
Bug description:
CONFIG_NET_IPIP and CONFIG_IPV6_SIT are set to =y in the -kvm kernels.
This means that they are always present in the kernel, and the virtual
devices they created (tunl0 and sit0) are always present, even when
not configured and not needed.
This is causing some issues for clouds that use the -kvm flavour, and
there is no good reason for those configuration options to be =y
anyway.
So they should be converted to =m instead.
[Regression potential]
- The only possible regression I can think of by compiling these as modules
is the possibility that someone's boot setup somehow depended on IP tunneling.
Such issues would need to be worked out by some initramfs means, etc.
- After this change, the modules (ipip.ko, sit.ko) are present in
linux-modules.
- General consensus was that these options should have been =m all along.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1899832/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
