> If you don't mind, once you verify the host's /proc/net/arp entries
> before and after it goes bad, I'm going to whip up a recipe for trying
> to reproduce this without kvm, so we can reclassify it approrpriately.
I don't see the ARP entry for the guest at all on the host machine before the networking fails, it's just not there; even after pinging the host machine from the guest, and vice-versa. It doesn't make a difference whether or not STP is enabled on the bridge.
BEFORE NETWORKING FAILS:
# cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.154 0x1 0x2 00:30:1b:be:63:4f * eth0
192.168.8.1 0x1 0x2 00:15:17:dc:2f:a2 * br0
AFTER NETWORKING FAILS:
# cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.154 0x1 0x2 00:30:1b:be:63:4f * eth0
192.168.8.1 0x1 0x2 00:15:17:dc:2f:a2 * br0
> If you don't mind, once you verify the host's /proc/net/arp entries
> before and after it goes bad, I'm going to whip up a recipe for trying
> to reproduce this without kvm, so we can reclassify it approrpriately.
I don't see the ARP entry for the guest at all on the host machine before the networking fails, it's just not there; even after pinging the host machine from the guest, and vice-versa. It doesn't make a difference whether or not STP is enabled on the bridge.
BEFORE NETWORKING FAILS:
# cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.154 0x1 0x2 00:30:1b:be:63:4f * eth0
192.168.8.1 0x1 0x2 00:15:17:dc:2f:a2 * br0
AFTER NETWORKING FAILS:
# cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.154 0x1 0x2 00:30:1b:be:63:4f * eth0
192.168.8.1 0x1 0x2 00:15:17:dc:2f:a2 * br0