Avi,
Avi Kivity wrote:
packet counters are will within 32-bit limits. byte counters not so
interesting.
This night my test overflowed the *packet* counters twice without any
slowness or loss of connectivity.
Snippet from my log file of the sending VM (linux 2.6.27):
Wed Mar 18 05:14:18 CET 2009: TX packet counter = 4292944043
Wed Mar 18 05:15:18 CET 2009: TX packet counter = 6259211
ifconfig after stress test:
# ifconfig
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:150 Metric:1
RX packets:48950340 errors:0 dropped:0 overruns:0 frame:0
TX packets:727911367 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3686511201 (3.4 GiB) TX bytes:4207842269 (3.9 GiB)
I didn't create a log file on the receiving Windows VM but they must
have overflowed as well. Its packet counters are currently:
Sent: 47.112.780
Received: 1.515.275.693
No problem on the Windows guest either.
So the problem must lie elsewhere.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
