Public bug reported:
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.
** Affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: Triaged
** Changed in: linux-kvm (Ubuntu)
Status: New => Triaged
--
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/1882955
Title:
LXD 4.2 broken on linux-kvm due to missing VLAN filtering
Status in linux-kvm package in Ubuntu:
Triaged
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1882955/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
