libvirt and kvm networking
- From: Jack Snodgrass <jacks_temp_id_bf2142@xxxxxxxxxxx>
- Date: Tue, 27 Nov 2007 20:34:46 GMT
Not sure where to post this....
I have a kvm 'guest' running on a Fedora 8 box. It has a web server
running on it. I am using livbirt ( I guess ) to setup the vnet0
network device. When I start the kvm 'guest' vnet1 is started.
Everything seems to work ( I can ping my kvm 'guest' and vica-versa )
but if I put the network under a small load using webbench ) the
network delays go through the roof.
If I run 30 seconds of webbench ( same page loaded over and over again )
I get:
Speed=414 pages/min, 108129 bytes/sec.
Speed=1118 pages/min, 291756 bytes/sec.
Speed=762 pages/min, 198755 bytes/sec.
Speed=552 pages/min, 143980 bytes/sec.
Speed=474 pages/min, 123779 bytes/sec.
Speed=426 pages/min, 111115 bytes/sec.
Speed=658 pages/min, 172051 bytes/sec.
Speed=304 pages/min, 79293 bytes/sec.
Speed=510 pages/min, 133400 bytes/sec.
Speed=874 pages/min, 227968 bytes/sec.
these numbers should be failly consistent given that they are run
during the same time period, one right after another and nothing else
is running during that 5 minute span.
pings show:
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=95 ttl=64 time=1569 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=96 ttl=64 time=570 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=97 ttl=64 time=0.769 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=98 ttl=64 time=0.355 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=99 ttl=64 time=0.322 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=100 ttl=64 time=0.277 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=101 ttl=64 time=10128 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=102 ttl=64 time=9129 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=103 ttl=64 time=8129 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=104 ttl=64 time=7130 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=105 ttl=64 time=6130 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=106 ttl=64 time=5130 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=107 ttl=64 time=4131 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=108 ttl=64 time=3131 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=109 ttl=64 time=2131 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=110 ttl=64 time=1132 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=111 ttl=64 time=132 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=112 ttl=64 time=0.591 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=113 ttl=64 time=1.26 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=114 ttl=64 time=2571 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=115 ttl=64 time=1571 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=116 ttl=64 time=571 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=117 ttl=64 time=0.670 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=118 ttl=64 time=0.588 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=119 ttl=64 time=7123 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=120 ttl=64 time=6124 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=121 ttl=64 time=5125 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=122 ttl=64 time=4125 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=123 ttl=64 time=3125 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=124 ttl=64 time=2126 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=125 ttl=64 time=1126 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=126 ttl=64 time=126 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=127 ttl=64 time=0.699 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=128 ttl=64 time=0.264 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=129 ttl=64 time=0.192 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=130 ttl=64 time=0.854 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=131 ttl=64 time=0.671 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=132 ttl=64 time=0.380 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=133 ttl=64 time=0.187 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=134 ttl=64 time=0.220 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=135 ttl=64 time=1574 ms
64 bytes from kvmweb.private.net (192.168.100.23): icmp_seq=136 ttl=64 time=575 ms
.... I'm not loosing any packets... but the response time really, really
flucuates... 10 seconds -vs- 126ms.
Does anyonw know how to get this virtual network stuff more stable?
--
D.A.M. - Mothers Against Dyslexia
see http://www.jacksnodgrass.com for my contact info.
jack - Grapevine/Richardson
.
- Prev by Date: Re: hosts.allow does not resolve names
- Next by Date: Re: Fundamentals: what packets are dropped by the kernel?
- Previous by thread: timer resolution of ping programme
- Next by thread: Packet capture
- Index(es):
Relevant Pages
|