To keep potential regressions even lower I'd for now only consider that for
>=Bionic.
That also helps as if someone intentionally spawns an old type KVM machine (pre
Bionic) on a >=Bionic host we don#t have to care about this too much (machine
type, not release runnin IN the guest). That makes us able to ignore
ipxe-qemu-256k-compat-efi-roms in regard to this issue.
** Also affects: ipxe-qemu-256k-compat (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: ipxe (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: ipxe-qemu-256k-compat (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: ipxe (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: ipxe-qemu-256k-compat (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: Invalid
** Also affects: ipxe (Ubuntu Disco)
Importance: Undecided
Status: Fix Released
** Also affects: ipxe-qemu-256k-compat (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ipxe (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ipxe-qemu-256k-compat (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ipxe (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ipxe-qemu-256k-compat (Ubuntu Bionic)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Trusty)
** No longer affects: linux (Ubuntu Xenial)
** No longer affects: linux (Ubuntu Bionic)
** No longer affects: linux (Ubuntu Cosmic)
** No longer affects: linux (Ubuntu Disco)
** Changed in: ipxe-qemu-256k-compat (Ubuntu Trusty)
Status: New => Invalid
** Changed in: ipxe-qemu-256k-compat (Ubuntu Xenial)
Status: New => Invalid
** No longer affects: ipxe-qemu-256k-compat (Ubuntu Trusty)
** No longer affects: ipxe-qemu-256k-compat (Ubuntu Xenial)
** No longer affects: ipxe-qemu-256k-compat (Ubuntu Bionic)
** No longer affects: ipxe-qemu-256k-compat (Ubuntu Cosmic)
** No longer affects: ipxe-qemu-256k-compat (Ubuntu Disco)
** Changed in: ipxe-qemu-256k-compat (Ubuntu)
Status: New => Won't Fix
** Changed in: ipxe (Ubuntu Trusty)
Status: New => Won't Fix
** Changed in: ipxe (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: ipxe-qemu-256k-compat (Ubuntu)
Status: Won't Fix => Invalid
** Changed in: ipxe (Ubuntu Bionic)
Status: New => Triaged
** Changed in: ipxe (Ubuntu Cosmic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805920
Title:
iPXE ignores vlan 0 traffic
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1805920/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
