Guest VM network not working when host is using balance-rr bonding and 2 active interfaces

I will try and find time to dabble with the above setting on .102, but i'm in quite a rush to get this machine in to use for some tasks. o_O

I can say though, that the 6.2 kernel (6.2.6-1-pve) seems to be working for me without issue, details are in the bugzilla thread.
 
I am seeing the same problem in proxmox 8.0.3:
m:~# pveversion
pve-manager/8.0.3/bbf3993334bfa916 (running kernel: 6.2.16-3-pve)
 
Last edited:
I got the exact same problem with v8.1.10(kernel 6.5.13-3pve)

note:
guest HDCP doesn't work with bonding in RR mode, but works fine in LACP
 
Last edited:
Just trying this out now and getting exactly the same issue :(

Proxmox v8.2.4 (kernel 6.8.8-3-pve)

Purely by chance I am only running 1 x VM each on these nodes (it's a test K3s cluster) so I don't think turning vmbr0 in to a hub matters too much .... but would definitely like to be able to find a better way around the issue :)

Note: The reason I chose balance-rr is purely for speed - AFAIK it's the only bonding type that gives you the maximum speed, e.g. 2 x 2.5Gbit NICs is pushing through around 4-4.2Gbps host-to-host.
 
Last edited:
Hi. Same issue here, on a single node instance of Proxmox 8.3.0 and kernel 6.8.12-2-pve and 1 VM (with Ubuntu 24.04 server).
Works perfectly with a single NIC up, without special "artifact" on the switch side (no LACP, for example) with a bridge configured directly in Proxmox (vmbr2), but when using a bonding "balance-rr" with two NIC up only hypervisor network traffic is correctly routed (vmbr1).
No traffic from VMs (except for host-to-host between VM and host).
In my use case both the host and the VM have static IP addresses.

Code: 
auto lo
iface lo inet loopback

auto enp51s0f1
iface enp51s0f1 inet manual

auto enp69s0f1
iface enp69s0f1 inet manual

auto eno145
iface eno145 inet manual

auto bond1
iface bond1 inet manual
        bond-slaves enp51s0f1 enp69s0f1
        bond-miimon 100
        bond-mode balance-rr

auto vmbr1
iface vmbr1 inet static
        address 10.72.74.1/32
        bridge-ports bond1
        bridge-stp off
        bridge-fd 0

auto vmbr2
iface vmbr2 inet static
        address 10.72.74.100/32
        gateway 10.72.74.254
        bridge-ports eno145
        bridge-stp off
        bridge-fd 0

Any ideas?
It's a fresh and simple installation.
Thanks.
 
Had the same thing occur. Balance-rr only allowed host to vm traffic, the vm would get a DHCP lease for a valid IP on the network but no traffic beyond the host. The ip should current in the DHCP server. i attempted the e1000 and virtio nic switch but it only last so long. I noticed that i had to ahve ipv6 enabled to have better chances of the connection lasting l longer.

Code: 
  Host Name . . . . . . . . . . . . : DESKTOP-QE6GT70
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8139C+ Fast Ethernet NIC
   Physical Address. . . . . . . . . : BC-24-11-ED-0E-BA
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : fd5a:424:f1db:55f6:2f02:cd71:7242:eb50(Preferred)
   Temporary IPv6 Address. . . . . . : fd5a:424:f1db:55f6:a193:3804:753f:c732(Preferred)
   Link-local IPv6 Address . . . . . : fe80::3e49:e907:b9a6:cdd5%21(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.22.22.179(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, May 2, 2025 3:23:21 PM
   Lease Expires . . . . . . . . . . : Friday, May 2, 2025 4:16:44 PM
   Default Gateway . . . . . . . . . : 10.22.22.1
   DHCP Server . . . . . . . . . . . : 10.22.22.1
   DHCPv6 IAID . . . . . . . . . . . : 364651537
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2F-A6-E0-88-BC-24-11-ED-0E-BF
   DNS Servers . . . . . . . . . . . : 10.22.22.1
                                       1.1.1.1
                                       1.0.0.1
                                       8.8.8.8
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter vEthernet (Default Switch):

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
   Physical Address. . . . . . . . . : 00-15-5D-B4-8D-00
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::afc5:b024:b22:55e%17(Preferred)
   IPv4 Address. . . . . . . . . . . : 172.29.0.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 285218141
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2F-A6-E0-88-BC-24-11-ED-0E-BF
   NetBIOS over Tcpip. . . . . . . . : Enabled


Code: 
auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto eno2
iface eno2 inet manual

auto bond0
iface bond0 inet manual
        bond-slaves eno1 eno2
        bond-miimon 100
        bond-mode balance-rr

auto vmbr0
iface vmbr0 inet static
        address 10.22.22.61/24
        gateway 10.22.22.1
        bridge-ports bond0
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094
`ip a` validates the info above

I tried vlan aware and not, I am not using LACP w/ L2&3. Crossing my fingers that it sticks. Nothing helpful has been found in the VM event viewer logs,
 
You must log in or register to reply here.
Top Bottom