Logically, a teamed adapter makes sense in a physical system, but in a virtual one, I can't figure out what the benefit is. I have a specific software package, I have no control over source code wise, which currently resides on a physical system that's highly depends on a teamed interface. It programmatically checks for it. Overall this is fine and I've created those within a windows vm.
My question is, what downsides, from an I/O side, might a virtual team adapter have? Each member is tied to its own virtio nic, which are in turn tied to a vnet -> zone -> vmbr -> bonded physical nics. It's definitely another software layer to worry about, but I'm more so interested in how it might affect the host level network stack, if at all.
My question is, what downsides, from an I/O side, might a virtual team adapter have? Each member is tied to its own virtio nic, which are in turn tied to a vnet -> zone -> vmbr -> bonded physical nics. It's definitely another software layer to worry about, but I'm more so interested in how it might affect the host level network stack, if at all.