From: Felix Leimbach <felix.leimbach@gmx.net>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: strange guest slowness after some time
Date: Tue, 17 Mar 2009 18:05:19 +0100 [thread overview]
Message-ID: <49BFD84F.8050509@gmx.net> (raw)
In-Reply-To: <49BFCC04.9080402@wpkg.org>
Tomasz Chmielewski wrote:
> Avi Kivity schrieb:
>> Might it be that some counter overflowed? What are the packet counts
>> on long running guests?
> I don't think so.
>
> I just made both counters (TX, RX) of ifconfig for virtio interfaces
> overflow several times and everything is still as fast as it should be.
I had overflows on the counters as well (32 bit guests) without an problem.
Here is the current ifconfig output of a machine which suffered the
problem before:
eth0 Link encap:Ethernet HWaddr 52:54:00:74:01:01
inet addr:10.75.13.1 Bcast:10.75.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3542104 errors:0 dropped:0 overruns:0 frame:0
TX packets:412546 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:682285568 (650.6 MiB) TX bytes:2907586796 (2.7 GiB)
>> (output of ifconfig, even on an unaffected e1000 guest, might help)
currently I have e1000 only on windows guests. Is there a way to gather
relevant statistics there too?
next prev parent reply other threads:[~2009-03-17 17:05 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 15:47 strange guest slowness after some time Tomasz Chmielewski
2009-03-07 16:41 ` Johannes Baumann
2009-03-07 16:54 ` Tomasz Chmielewski
2009-03-09 9:18 ` Tomasz Chmielewski
2009-03-09 9:28 ` Tomasz Chmielewski
2009-03-19 13:03 ` Tomasz Chmielewski
2009-03-09 9:55 ` Avi Kivity
2009-03-09 10:22 ` Tomasz Chmielewski
2009-03-09 10:25 ` Avi Kivity
2009-03-09 10:31 ` Tomasz Chmielewski
2009-03-09 10:37 ` Avi Kivity
2009-03-09 10:54 ` Tomasz Chmielewski
2009-03-09 11:37 ` Tomasz Chmielewski
2009-03-09 12:14 ` Avi Kivity
2009-03-09 12:52 ` Tomasz Chmielewski
2009-03-15 15:41 ` Avi Kivity
2009-03-15 16:14 ` Avi Kivity
2009-03-15 13:19 ` Tomasz Chmielewski
2009-03-17 10:47 ` Tomasz Chmielewski
2009-03-17 11:16 ` Avi Kivity
2009-03-17 11:25 ` Tomasz Chmielewski
2009-03-17 15:32 ` Felix Leimbach
2009-03-17 15:43 ` Tomasz Chmielewski
2009-03-17 17:01 ` Felix Leimbach
2009-03-17 17:05 ` Avi Kivity
2009-03-17 18:49 ` Felix Leimbach
2009-03-18 6:36 ` Avi Kivity
2009-03-18 7:57 ` Felix Leimbach
2009-03-18 8:48 ` Avi Kivity
2009-03-18 9:08 ` Felix Leimbach
2009-03-17 17:38 ` Tomasz Chmielewski
2009-06-08 11:02 ` Felix Leimbach
2009-06-16 14:26 ` Tomasz Chmielewski
2009-03-31 8:50 ` Tomasz Chmielewski
2009-04-01 4:22 ` David S. Ahern
2009-04-01 6:21 ` Tomasz Chmielewski
2009-04-06 15:19 ` Tomasz Chmielewski
2009-04-08 0:49 ` Rusty Russell
2009-04-08 5:45 ` Tomasz Chmielewski
2009-05-26 11:49 ` Tomasz Chmielewski
2009-05-26 11:55 ` Avi Kivity
2009-05-26 12:05 ` Tomasz Chmielewski
2009-05-26 12:10 ` Avi Kivity
2009-05-26 14:07 ` Tomasz Chmielewski
2009-05-26 14:35 ` Avi Kivity
2009-05-28 14:58 ` Tomasz Chmielewski
2009-05-31 8:43 ` Avi Kivity
2009-03-17 15:52 ` Avi Kivity
2009-03-17 16:12 ` Tomasz Chmielewski
2009-03-17 17:05 ` Felix Leimbach [this message]
2009-03-17 17:10 ` Avi Kivity
2009-03-17 17:43 ` Tomasz Chmielewski
2009-03-17 18:55 ` Tomasz Chmielewski
2009-03-17 19:04 ` Felix Leimbach
2009-03-17 19:24 ` Tomasz Chmielewski
2009-03-17 20:14 ` Tomasz Chmielewski
2009-03-17 22:34 ` Tomasz Chmielewski
2009-03-17 23:02 ` Tomasz Chmielewski
2009-03-18 6:29 ` Avi Kivity
2009-03-19 4:59 ` Rusty Russell
2009-03-19 5:22 ` David S. Ahern
2009-03-19 6:08 ` David S. Ahern
2009-03-19 8:03 ` Tomasz Chmielewski
2009-03-19 14:11 ` David S. Ahern
2009-03-17 18:57 ` Felix Leimbach
2009-03-18 5:54 ` Felix Leimbach
2009-03-17 16:27 ` Tomasz Chmielewski
2009-03-17 17:14 ` Felix Leimbach
2009-03-17 17:19 ` Avi Kivity
2009-03-17 17:34 ` Tomasz Chmielewski
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=49BFD84F.8050509@gmx.net \
--to=felix.leimbach@gmx.net \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mangoo@wpkg.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.