** Description changed: - This is another case of linux-kvm having unexplained differences - compared to linux-generic in areas that aren't related to hardware - drivers (see other bug we filed for missing nft). + [Description] + + Some VLAN options (BRIDGE_VLAN_FILTERING, and its dependencies + VLAN_8021Q*) were in a different state in Focal/kvm compared to + Focal/generic: LXD now depends on BRIDGE_VLAN_FILTERING and due to this + discrepancy it fails to work on the Focal/kvm kernel: fix it by aligning + the config with Focal/generic + + [Fix] + + Apply the attached config patch + + [Regression potential] + + Low, just some config changes already present in generic. + + --- + This is another case of linux-kvm having unexplained differences compared to linux-generic in areas that aren't related to hardware drivers (see other bug we filed for missing nft). This time, CPC is reporting that LXD no longer works on linux-kvm as we now set vlan filtering on our bridges to prevent containers from escaping firewalling through custom vlan tags. This relies on CONFIG_BRIDGE_VLAN_FILTERING which is a built-in on the generic kernel but is apparently missing on linux-kvm (I don't have any system running that kernel to confirm its config, but the behavior certainly matches that). We need this fixed in focal and groovy.
** Patch added: "0001-UBUNTU-Config-VLAN_8021Q-m-BRIDGE_VLAN_FILTERING-y.patch" https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1882955/+attachment/5386465/+files/0001-UBUNTU-Config-VLAN_8021Q-m-BRIDGE_VLAN_FILTERING-y.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882955 Title: LXD 4.2 broken on linux-kvm due to missing VLAN filtering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1882955/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
