This bug was fixed in the package linux-kvm - 5.4.0-1021.21
---
linux-kvm (5.4.0-1021.21) focal; urgency=medium
* focal/linux-kvm: 5.4.0-1021.21 -proposed tracker (LP: #1890740)
* Focal update: v5.4.53 upstream stable release (LP: #1888560)
- [Config] updateconfigs for
** Changed in: linux-kvm (Ubuntu Focal)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881346
Title:
linux-kvm should support nftables
To manage
** Also affects: linux-kvm (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: linux-kvm (Ubuntu Focal)
Status: New => Triaged
** Changed in: linux-kvm (Ubuntu)
Status: New => Invalid
--
** Description changed:
- LXD can't use nftables on the latest linux-kvm kernels for eoan, focal,
- and groovy:
+ [Impact]
+
+ LXD can't use nftables on the latest linux-kvm kernels for Eoan and
+ Focal, since nftables support is off in those kernels (contrary to
+ generic, where nftables is
Right, I've sent a tweak to LXD upstream to detect such kernel setup and
fallback to xtables, but that's obviously not a situation we'd like to
rely on.
nftables is the current supported way of doing firewalling and is what
Ubuntu uses by default (through shim packages) as of 20.04, so we need
to
