From: Antoine Martin <antoine@nagafix.co.uk>
To: Antoine Martin <antoine@devloop.org.uk>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: virtio net regression
Date: Thu, 16 Apr 2009 00:38:35 +0100 [thread overview]
Message-ID: <49E66FFB.4080504@nagafix.co.uk> (raw)
In-Reply-To: <49E63DB4.4090107@devloop.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Wireshark was showing a huge amount of invalid packets (wrong checksum)
- - that was the cause of the slowdown.
Simply rebooting the host into 2.6.28.9 fixed *everything*, regardless
of whether the guests use virtio or ne2k_pci/etc.
The guests are still running 2.6.29.1, but I am not likely to try that
release again on the host anytime soon! Ouch!
Antoine
Antoine Martin wrote:
> Hi,
>
> I've got some hosts that were happily running the 2.6.25.x host kernel,
> kvm-84, kernel.org kvm modules.
> The guests were running 2.6.25 to 2.6.29.x quite happily.
> Network was using virtio.
> Since I upgraded one of the hosts (Intel dual core) to 2.6.29.x
> yesterday, the virtio network performance of the guests on it dropped
> dramatically. (for some reason another AMD host did not seem to be
> affected...)
> Here are the tests I performed using wget and scp:
> * guest to guest: fast
> * guest to host: fast
> * host to internet: fast
> * guest to internet: slow!!!
> I was normally getting ~5MB/s to the host (speed to the internet was
> limited by the capacity of the DSL line), but since the upgrade the
> performance had dropped to around 20KB/s!
> Strangely enough, I could open many new connections to the guest and get
> more chunks all at 20KB/s!
> I switched the guests to using ne2k_pci and the performance has been
> restored...
>
> And this is where it gets even weirder...
> UDP packets get corrupted using ne2k_pci and rtl8139cp but not with
> virtio...
> So I can get performance or UDP, but not both...
>
> Let me know if there is anything more I can provide to help fix this
> regression.
> I can reproduce the problem quite easily without causing problems on the
> host.
>
> Cheers
> Antoine
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEUEAREKAAYFAknmb/sACgkQGK2zHPGK1ruzgwCWPMvAJzToIMbrE7k2K2FHBQlk
dQCcCpDrTufqIN4ZSQs/dMLTQMYtTAU=
=lDW9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-04-15 23:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 20:04 virtio net regression Antoine Martin
2009-04-15 23:38 ` Antoine Martin [this message]
2009-04-19 11:48 ` Avi Kivity
2009-04-20 11:12 ` Mark McLoughlin
2009-04-20 15:09 ` Antoine Martin
[not found] ` <49EC8F1D.7000109@nagafix.co.uk>
2009-04-28 18:57 ` Antoine Martin
2009-05-09 13:19 ` Antoine Martin
2009-05-13 12:58 ` Antoine Martin
2009-05-14 3:52 ` David Miller
2009-05-18 9:39 ` Avi Kivity
2009-05-19 10:16 ` Antoine Martin
2009-05-19 10:21 ` Avi Kivity
2009-05-19 10:47 ` Antoine Martin
2009-05-19 13:03 ` Avi Kivity
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=49E66FFB.4080504@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--cc=antoine@devloop.org.uk \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox