From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH pve-common v2 1/1] fix #7153: iproute2: consider bonds as physical bridge ports
Date: Tue, 16 Dec 2025 17:17:46 +0100 [thread overview]
Message-ID: <3b03e6f0-a436-4ec7-8242-f32f745998de@proxmox.com> (raw)
In-Reply-To: <20251216160513.360391-1-s.hanreich@proxmox.com>
tested by a user in the forum:
https://forum.proxmox.com/threads/problem-migrating-vms-in-a-proxmox-9-cluster-with-vlan-on-vmbr0.177334/#post-825321
On 12/16/25 5:05 PM, Stefan Hanreich wrote:
> The new check did not consider bonds, since ip_link_is_physical only
> returns true for physical interfaces - but not bonds. Add a new
> function to check for bonds explicitly and use it when checking for
> bridge ports in activate_bridge_vlan.
>
> This bug caused VMs with network devices with VLAN tags, on
> non-vlan-aware bridges, to not get started / migrated.
>
> Fixes: 057f62f7
> Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
> ---
> Changes from v1:
> * improved commit message
> * add missing definedness check
>
> src/PVE/IPRoute2.pm | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/src/PVE/IPRoute2.pm b/src/PVE/IPRoute2.pm
> index 5208d93..c60a91d 100644
> --- a/src/PVE/IPRoute2.pm
> +++ b/src/PVE/IPRoute2.pm
> @@ -32,6 +32,14 @@ sub ip_link_is_physical($ip_link) {
> && (!defined($ip_link->{linkinfo}) || !defined($ip_link->{linkinfo}->{info_kind}));
> }
>
> +sub ip_link_is_bond($ip_link) {
> + return
> + $ip_link->{link_type} eq 'ether'
> + && defined($ip_link->{linkinfo})
> + && defined($ip_link->{linkinfo}->{info_kind})
> + && $ip_link->{linkinfo}->{info_kind} eq 'bond';
> +}
> +
> sub ip_link_is_bridge($ip_link) {
> return
> defined($ip_link->{linkinfo})
> @@ -67,7 +75,8 @@ sub get_physical_bridge_ports($bridge, $ip_links = undef) {
> }
>
> return grep {
> - ip_link_is_physical($ip_links->{$_}) && $ip_links->{$_}->{master} eq $bridge
> + (ip_link_is_physical($ip_links->{$_}) || ip_link_is_bond($ip_links->{$_}))
> + && defined($ip_links->{$_}->{master}) && $ip_links->{$_}->{master} eq $bridge
> } keys $ip_links->%*;
> }
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-12-16 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 16:05 Stefan Hanreich
2025-12-16 16:17 ` Stefan Hanreich [this message]
2025-12-17 14:30 ` Stoiko Ivanov
2025-12-17 17:26 ` Stefan Hanreich
2025-12-17 21:27 ` [pve-devel] applied: " Thomas Lamprecht
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=3b03e6f0-a436-4ec7-8242-f32f745998de@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pve-devel@lists.proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.