From: David Logan <djlogan2.dl@gmail.com>
To: "Srinivas M.A." <srinivas.aji@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Help with Ubuntu + bridge + tap + qemu + Windows
Date: Mon, 1 Feb 2016 22:47:37 -0700 [thread overview]
Message-ID: <541B3DA2-45E9-4E55-9BA0-DF554FCB2FE6@gmail.com> (raw)
In-Reply-To: <CANbryT-OrFoLy5APcXbrEEQSTAHQqfTH303HwV7d-jWM9mApyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
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@gmail.com> wrote:
>
> On Tue, Feb 2, 2016 at 1:21 AM, David Logan <djlogan2.dl@gmail.com> 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?
[-- Attachment #2: Type: text/html, Size: 3365 bytes --]
next prev parent reply other threads:[~2016-02-02 5:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 19:51 [Bridge] Help with Ubuntu + bridge + tap + qemu + Windows David Logan
2016-02-01 20:04 ` David Logan
2016-02-02 3:27 ` Stephen Hemminger
2016-02-02 4:48 ` David Logan
2016-02-02 5:34 ` Srinivas M.A.
2016-02-02 5:47 ` David Logan [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-02 23:33 gilberto dos santos alves
2016-02-03 0:51 ` Stephen Hemminger
2016-02-03 4:47 ` David Logan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=541B3DA2-45E9-4E55-9BA0-DF554FCB2FE6@gmail.com \
--to=djlogan2.dl@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=srinivas.aji@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox