I’m running into a networking issue where VMs using different NIC types on the same physical interface can’t communicate with each other, even though they can both reach external hosts.
Setup
- Host: Debian 12, Incus 6.12
- NIC: Intel X553 10GbE with SR-IOV enabled (
eno1
) - Bridge: VLAN-aware bridge
br0
witheno1
as member - VM lab2: Uses SR-IOV with
nictype: sriov
,parent: eno1
,vlan: "41"
- VM lab3: Uses bridge with
nictype: bridged
,parent: br0
,vlan: "41"
Both VMs get IPs on the same subnet (192.168.41.x) and can communicate with external hosts, but not with each other.
What I’ve Found
Looking at bridge fdb list
, lab3’s MAC appears correctly in the forwarding database, but lab2’s MAC (the SR-IOV VM) is missing entirely.
I’ve used a similar SR-IOV/bridge mix with libvirt (though not with VLAN-aware bridges) and it works automatically with no special configuration needed. And for Proxmox I’ve found a thread where manual bridge FDB management is used as a workaround.
Has anyone successfully mixed SR-IOV and bridge networking on the same physical interface with Incus? Is there a recommended approach for this scenario?