When we notify peers of potential changes, it's also good to update
IGMP memberships. For example, during VM migration, updating IGMP
memberships will redirect existing multicast streams to the VM at the
new location.
Signed-off-by: Vladislav Yasevich <redacted>
---
net/core/dev.c | 1 +
1 file changed, 1 insertion(+)
From: "Michael S. Tsirkin" <mst@redhat.com> Date: 2017-03-14 15:32:16
On Tue, Mar 14, 2017 at 08:58:08AM -0400, Vladislav Yasevich wrote:
When we notify peers of potential changes, it's also good to update
IGMP memberships. For example, during VM migration, updating IGMP
memberships will redirect existing multicast streams to the VM at the
new location.
Signed-off-by: Vladislav Yasevich <redacted>
what will happen on the source? will the snooping bridge remove
membership on port removal as appropriate?
From: "Michael S. Tsirkin" <mst@redhat.com> Date: 2017-03-14 16:36:25
On Tue, Mar 14, 2017 at 08:58:08AM -0400, Vladislav Yasevich wrote:
When we notify peers of potential changes, it's also good to update
IGMP memberships. For example, during VM migration, updating IGMP
memberships will redirect existing multicast streams to the VM at the
new location.
Signed-off-by: Vladislav Yasevich <redacted>
Seems to make sense
Acked-by: Michael S. Tsirkin <mst@redhat.com>
but I also think there's another problem: source does not
leave the groups on migration. So I think we should add code on the
host - it's snooping IGMPs so it should be able to leave groups on the
source when VM is disconnected.
When we notify peers of potential changes, it's also good to update
IGMP memberships. For example, during VM migration, updating IGMP
memberships will redirect existing multicast streams to the VM at the
new location.
Signed-off-by: Vladislav Yasevich <redacted>