runinng two switches: vde_switch -s /tmp/switch1 vde_switch -s /tmp/switch2 and two kvm guests: kvm -hda VT/debian_lenny0 -m 256 -net nic,model=rtl8139,macaddr=56:44:45:30:30:34 -net vde,sock=/tmp/switch1 kvm -hda VT/debian_lenny1 -m 256 -net nic,model=rtl8139,macaddr=56:44:45:30:30:34 -net vde,sock=/tmp/switch2 will cause them not to being able to see each other even in arp level, which is good and expected, i can use dpipe to connect two switches which will cause them to see each other in arp level, which is also good and expected, the issue is with: kvm -hda VT/debian_lenny2 -m 256 -net nic,macaddr=56:44:45:30:30:30 -net vde,sock=/tmp/switch1 -net nic,macaddr=56:44:45:30:30:10 -net vde,sock=/tmp/switch2 when i run this command, two 'single interface' guests immediately will get able to ping and see each other in arp level, this is happening even before entering OS, i don't know whats wrong, its appear that last kvm acts like dpipe bridge immediately after starting, any idea on this? ps: as it might not be clear, i have tried to emulate 'bridge' like guest between two switches, third guest should be able to see arps on both side, but should not do any bridging without arp proxy enabled in OS, which seems to happen far before OS immediately after KVM starts. --- Armin ranjbar, System administrator -- 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
