From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, "Rémi PAETA" <remi.paeta@comaite.com>
Subject: applied: [PATCH qemu-server v2 0/2] fix #6490: network: bridge fdb entries on nic hotplug
Date: Mon, 9 Nov 2026 22:15:52 +0100 [thread overview]
Message-ID: <179425895080.866952.17654568750180480138.b4-ty@b4> (raw)
In-Reply-To: <20261029164939.1278135-1-remi.paeta@comaite.com>
On Thu, 29 Oct 2026 17:49:37 +0100, Rémi PAETA wrote:
> Thank you Gabriel and Fiona for your feedback on v1! This v2 takes it
> into account.
>
> On bridges with MAC learning disabled, hotplugged or re-plugged NICs
> get no forwarding database entries, so the guest loses connectivity on
> that NIC, and a later live migration fails when deleting the missing
> entries.
>
> [...]
Applied, thanks!
[1/2] network: do not fail on missing bridge fdb entries when migrating
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=7bb788e2bbfd89e45bc293e2290fc0f3314cc5da
[2/2] fix #6490: network: add bridge fdb entries when hotplugging a nic
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=27e51213d75e9fdf067153c8008794e84d69af8a
prev parent reply other threads:[~2026-11-09 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 16:49 [PATCH qemu-server v2 0/2] fix #6490: network: bridge fdb entries on nic hotplug Rémi PAETA
2026-10-29 16:49 ` [PATCH qemu-server v2 1/2] network: do not fail on missing bridge fdb entries when migrating Rémi PAETA
2026-10-29 16:49 ` [PATCH qemu-server v2 2/2] fix #6490: network: add bridge fdb entries when hotplugging a nic Rémi PAETA
2026-10-30 13:32 ` [PATCH qemu-server v2 0/2] fix #6490: network: bridge fdb entries on nic hotplug Gabriel Goller
2026-11-09 21:15 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179425895080.866952.17654568750180480138.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=remi.paeta@comaite.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox