KVM virbr# no longer forwards multicast traffic by default (U12.04)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Won't Fix
|
High
|
Unassigned |
Bug Description
A recent kernel update (Apr 2013) has made it's way to U12.04.2 LTS (approx June-Aug 2013) and has stopped the (default) behaviour of automatically forwarding multicast traffic over virbr#. Some updates the bridge subsystem now, by default, disable multicast traffic without IGMP Querier being enabled on that bridge.
The corresponding Fedora/RHEL bug tracks the progress/updates of this specific change in relation to Fedora.
https:/
(I have yet to find a similar bug report in Ubuntu so I have created this bug to help the Ubuntu community identify multicast issues that may arise since April 2013 in U12.04 LTS and presumably other Ubuntu releases as backports are made and break regression testing.)
Using the latest patches in U12.04.2 LTS this following addition, with some modifications, can be made to the udev rules will enable multicast on virbr# bridge:
https:/
While this is an improvement/
IMPACT: multicast is broken over libvirt bridges
FIX: set a (new, introduced by a new kernel) toggle on the bridges
TEST CASE: cat /sys/devices/
REGRESSION POTENTIAL: should be none. older kernels do not have the toggle, and failure to set it will be ignored
Changed in bridge-utils (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
affects: | bridge-utils (Ubuntu) → libvirt (Ubuntu) |
Changed in libvirt (Ubuntu Precise): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in libvirt (Ubuntu): | |
status: | Confirmed → Fix Released |
tags: | added: patch |
description: | updated |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Changed in linux (Ubuntu Precise): | |
status: | Incomplete → Won't Fix |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
Changed in linux (Ubuntu Precise): | |
importance: | Undecided → High |
This patch should solve this bug. However there is a package in precise-proposed right now, so this will need to be queued up.