From: Avi Kivity <avi@qumranet.com>
To: xming <xmingske@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Network Overruns
Date: Sat, 13 Sep 2008 17:44:19 +0300 [thread overview]
Message-ID: <48CBD1C3.4020006@qumranet.com> (raw)
In-Reply-To: <519a8b110809130118sd392d38lb11fe2fa004638c9@mail.gmail.com>
xming wrote:
>> Most likely the guest's rx queue length is greater than the host's. You
>> might try
>>
>> ifconfig vnet0 txqueuelen 1500
>>
>> (and so on for every interface)
>>
>>
>> or perhaps reducing the guests' txqueuelen.
>>
>
> I have the same issue (overruns) and I have stalled network (in my other
> report I can only unstall the network by putting the NIC in promisc back
> and forth).
>
> The txqueuelen is indeed greater in the guest then the tap on the host,
> and I also notice that it's almost ways the output NIc which get stuck.
>
> So changing the tap (on the host) to 1500, I can't not reproduce the hang yet
> and a ping -f -s 64000 (between guests) does not produce any packet loss.
>
> 27810 packets transmitted, 27809 received, 0% packet loss, time 259080ms
> rtt min/avg/max/mdev = 5.013/7.639/33.999/1.536 ms, pipe 3, ipg/ewma
> 9.316/7.284 ms
>
> I hope this is the solution for my network stalls and packet loss in games.
>
It's not a fix, rather a workaround. Hopefully some networking guru
will come up with a real fix.
What NIC model are you using in the guest?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2008-09-13 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 17:29 Network Overruns Henri Cook
2008-09-13 5:09 ` Avi Kivity
2008-09-13 8:18 ` xming
2008-09-13 14:44 ` Avi Kivity [this message]
[not found] ` <519a8b110809131600vbee71cbv6774e0d4ce2f4238@mail.gmail.com>
2008-09-14 1:03 ` Avi Kivity
2008-09-14 17:56 ` xming
2008-09-23 13:09 ` xming
2008-09-23 14:27 ` xming
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=48CBD1C3.4020006@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=xmingske@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