You need to add a vlan option to one of them, for example vlan=2
Otherwise kvm will bridge the interfaces together, and it's going to create
a packet storm.
I wondered about that -- but what's the relationship of a KVM vlan to
my existing bridge interfaces, and how can I control which one gets
mapped to, say "vlan 1" or "vlan 2"?
Are these redundant? Should I get rid of the bridges? Question still
remains about how to control which one connects to a physical NIC...
It's not redundant, it just ensures that each tap is treated as it's own
lan by kvm and that it isn't bridged together by kvm.
You need to keep the bridges as the kvm process doesn't talk to other kvm
processes by itself.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
