Hi Greg, thanks for your quick reply.
> >But the host can't send packets to the guests (or these packets are > >never > >received on the guests). When using tcpdump, I can see these packets > >leaving > >the device on the host, but they never arrive on the guest. > So you're saying that the guests don't even receive packets from the host > with broadcast as the destination address? that is correct. I just tried it again to verify: eth1 on the host is connected to an otherwise unused switch. The host is at 192.168.100.1, the vm at 192.168.100.2. The vm is not connected to any other network and has only the vf as nic (eth0). [r...@host]# arping -I eth1 192.168.100.2 -> no response during this I ran on the vm: [r...@vm]# tcpdump -i eth0 -n -> no packets When looking at the packet counter on the vm, the RX-counter is still 0. So no broadcasts from the host can reach the vm. When doing it the other way round: [r...@vm]# arping -I eth0 192.168.100.1 I still get no response. But that is because the host can't answer. The host sees the packets and replies: [r...@host]# tcpdump -i eth1 -n 14:05:48.473303 ARP, Request who-has 192.168.100.1 (Broadcast) tell 192.168.100.2, length 28 14:05:48.473329 ARP, Reply 192.168.100.1 is-at 00:1b:21:60:xx:xx, length 28 14:05:49.473478 ARP, Request who-has 192.168.100.1 (Broadcast) tell 192.168.100.2, length 28 14:05:49.473492 ARP, Reply 192.168.100.1 is-at 00:1b:21:60:xx:xx, length 28 [...] This evening I will upgrade the vm to 2.6.34 too. But aside from that I don't know what else to try. Any ideas what I could do to further trace this down? Kind regards, Gerd -- Address (better: trap) for people I really don't want to get mail from: jo...@cactusamerica.com ------------------------------------------------------------------------------ _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
