Re: Help with Ubuntu + bridge + tap + qemu + Windows

[David Logan <djlogan2.dl@xxxxxxxxx>]

No, not  yet, because I had no idea exactly who was responsible for what. I am using the virtio drivers and qemu. Let me look into that and see if I can find somebody to ask about it. That’s way more information that I had. I thought the “tx packets” were packets being transmitted from the vm to the bridge, not the other way around.

David Logan
http://www.linkedin.com/in/davidjlogan
303-818-8222

On Feb 1, 2016, at 10:34 PM, Srinivas M.A. <srinivas.aji@xxxxxxxxx> wrote:

On Tue, Feb 2, 2016 at 1:21 AM, David Logan <djlogan2.dl@xxxxxxxxx> wrote:

tap2      Link encap:Ethernet  HWaddr 8a:21:a8:cb:f5:98
         inet6 addr: fe80::8821:a8ff:fecb:f598/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:51870 errors:0 dropped:0 overruns:0 frame:0
         TX packets:741595 errors:0 dropped:5702 overruns:0 carrier:0
         collisions:0 txqueuelen:500
         RX bytes:3220139 (3.2 MB)  TX bytes:1113177111 (1.1 GB)

You are seeing TX packets dropped at the tap interface. So these are
packets that are being sent from the bridge to the VM on the tap
device, but getting dropped, probably because the tap device's queue
is full. This would mean that the packets are not getting read by the
VM fast enough, or may be not read at all after some point, since you
see only the dropped increase after a while. So the issue is likely to
be related to the virtualization software, rather than the bridge.
Have you tried asking about this on forums related to the
virtualization system you are using?