qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: Davide Guerri <d.guerri@unidata.it>
Cc: Peter Lieven <pl@dlhnet.de>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, Jan Kiszka <jan.kiszka@web.de>,
	Peter Lieven <lieven-lists@dlhnet.de>,
	Dietmar Maurer <dietmar@proxmox.com>
Subject: Re: [Qemu-devel] slow virtio network with vhost=on and multiple cores
Date: Thu, 14 Mar 2013 11:43:30 +0100 (CET)	[thread overview]
Message-ID: <6ce47933-c4df-4a64-9b94-69922ea3ef9a@mailpro> (raw)
In-Reply-To: <EE07F1D6-13DE-455C-8679-C4E29CA848CA@unidata.it>

I don't think it's fixed in 1.3 or 1.4, some proxmox users have reported again this bug with guest kernel 2.6.32. (proxmox host is rhel 6.3 kernel + qemu 1.4)



----- Mail original -----

De: "Davide Guerri" <d.guerri@unidata.it>
À: "Alexandre DERUMIER" <aderumier@odiso.com>
Cc: "Peter Lieven" <pl@dlhnet.de>, "Michael S. Tsirkin" <mst@redhat.com>, "Stefan Hajnoczi" <stefanha@gmail.com>, qemu-devel@nongnu.org, "Jan Kiszka" <jan.kiszka@web.de>, "Peter Lieven" <lieven-lists@dlhnet.de>, "Dietmar Maurer" <dietmar@proxmox.com>
Envoyé: Jeudi 14 Mars 2013 10:22:22
Objet: Re: [Qemu-devel] slow virtio network with vhost=on and multiple cores

I'd like to reopen this thread because this problem is still here and it's really annoying.
Another possible work-around is to pin the virtio nic irq to one virtual CPU (with /proc/smp_affinity) but (of course) this is still sub-optimal.

Here are some graphs showing the performance of a heavy loaded machine after and before a live migration from KVM-1.0 to KVM-1.2.
Host is a Ubuntu 12.10 Kernel 3.5, guest is a Ubuntu 10.04.4 LTS Kernel 2.6.32

History
-------
CPU time: http://s1299.beta.photobucket.com/user/dguerri/media/CPU-10days_zps4a088ff0.png.html
CPU Load: http://s1299.beta.photobucket.com/user/dguerri/media/Load-10days_zpsff27f212.png.html
NET pps: http://s1299.beta.photobucket.com/user/dguerri/media/pps-10days_zps003dd039.png.html
NET Mbps: http://s1299.beta.photobucket.com/user/dguerri/media/Mbps-10days_zpsfc3cba8c.png.html

Current
-------
CPU time: http://s1299.beta.photobucket.com/user/dguerri/media/CPU-2days_zpsd362cac6.png.html
CPU Load: http://s1299.beta.photobucket.com/user/dguerri/media/load-2days_zpsd4b7b50d.png.html
NET pps: http://s1299.beta.photobucket.com/user/dguerri/media/pps-2days_zps8f5458c9.png.html
NET Mbps: http://s1299.beta.photobucket.com/user/dguerri/media/Mbps-2days_zps299338b9.png.html

Red arrows indicate the kvm version change.
Black arrows indicate when I "pinned" the virtio NIC IRQ to only one CPU (that machine has 2 virtual cores).
As can be seen the performance penalty is rather high: that machine was almost unusable!

Does version 1.3 fixes this issue?

Could someone with the required knowledge look into this, please?
Please, this is a very nasty bug because I guess I'm not the only one who is unable to upgrade all the machines with a (not-so) old kernel... :)

Thanks!

Davide Guerri.




On 09/dic/2012, at 19:38, Alexandre DERUMIER <aderumier@odiso.com> wrote:

>>> Have you had any further progress on this regression/problem?
>
> Hi Peter,
> I didn't re-tested myself,
> but a proxmox user who's have the problem with qemu-kvm 1.2, with windows guest and linux guest,
> don't have the problem anymore with qemu 1.3.
>
> http://forum.proxmox.com/threads/12157-Win2003R2-in-KVM-VM-is-slow-in-PVE-2-2-when-multiply-CPU-cores-allowed
>
> I'll try to redone test myself this week
>
> Regards,
>
> Alexandre
>
> ----- Mail original -----
>
> De: "Peter Lieven" <pl@dlhnet.de>
> À: "Alexandre DERUMIER" <aderumier@odiso.com>
> Cc: "Dietmar Maurer" <dietmar@proxmox.com>, "Stefan Hajnoczi" <stefanha@gmail.com>, "Jan Kiszka" <jan.kiszka@web.de>, qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>, "Peter Lieven" <lieven-lists@dlhnet.de>
> Envoyé: Lundi 3 Décembre 2012 12:23:11
> Objet: Re: [Qemu-devel] slow virtio network with vhost=on and multiple cores
>
>
> Am 16.11.2012 um 12:00 schrieb Alexandre DERUMIER <aderumier@odiso.com>: 
>
>>>> While trying to reproduce the bug, we just detected that it depends on the hardware (mainboard) you run on.
>>>>
>>>> Sigh :-/
>>
>> Hi,
>>
>> I can reproduce the bug on all my dell servers,differents generation (R710 (intel),R815 (amd), 2950 (intel).
>>
>> They all use broadcom bnx2 network card (don't know if it can be related)
>>
>> host kernel : rhel 63 with 2.6.32 kernel
>>
>> guest kernel : 2.6.32 (debian squeeze, ubuntu).
>>
>> No problem with guest kernel 3.2
>
> Have you had any further progress on this regression/problem?
>
> Thanks,
> Peter
>
>>
>>
>>
>>
>> ----- Mail original -----
>>
>> De: "Dietmar Maurer" <dietmar@proxmox.com>
>> À: "Peter Lieven" <lieven-lists@dlhnet.de>
>> Cc: "Stefan Hajnoczi" <stefanha@gmail.com>, "Peter Lieven" <pl@dlhnet.de>, "Jan Kiszka" <jan.kiszka@web.de>, qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
>> Envoyé: Vendredi 16 Novembre 2012 11:44:26
>> Objet: Re: [Qemu-devel] slow virtio network with vhost=on and multiple cores
>>
>>>> I only tested with RHEL6.3 kernel on host.
>>>
>>> can you check if there is a difference on interrupt delivery between those
>>> two?
>>>
>>> cat /proc/interrupts should be sufficient after some traffic has flown.
>>
>> While trying to reproduce the bug, we just detected that it depends on the hardware (mainboard) you run on.
>>
>> Sigh :-/
>
>

  reply	other threads:[~2013-03-14 10:44 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 11:51 [Qemu-devel] slow virtio network with vhost=on and multiple cores Dietmar Maurer
2012-11-05 12:36 ` Stefan Hajnoczi
2012-11-05 15:01   ` Dietmar Maurer
2012-11-06  6:12   ` Dietmar Maurer
2012-11-06  7:46     ` Peter Lieven
2012-11-06  7:51       ` Dietmar Maurer
2012-11-06  9:01       ` Dietmar Maurer
2012-11-06  9:26         ` Jan Kiszka
2012-11-06  9:46           ` Dietmar Maurer
2012-11-06 10:12             ` Jan Kiszka
2012-11-06 11:24               ` Dietmar Maurer
2012-11-08  9:39                 ` Jan Kiszka
2012-11-08 10:55                   ` Peter Lieven
2012-11-08 12:03                   ` Dietmar Maurer
2012-11-08 15:02                     ` Peter Lieven
2012-11-09  5:55                       ` Dietmar Maurer
2012-11-09 17:27                         ` Peter Lieven
2012-11-09 17:51                           ` Peter Lieven
2012-11-09 18:03                             ` Peter Lieven
2012-11-13 11:44                               ` Peter Lieven
2012-11-13 11:49                               ` Peter Lieven
2012-11-13 16:22                                 ` Michael S. Tsirkin
2012-11-13 16:21                                   ` Peter Lieven
2012-11-13 16:26                                     ` Michael S. Tsirkin
2012-11-13 16:27                                       ` Peter Lieven
2012-11-13 16:59                                         ` Dietmar Maurer
2012-11-13 17:03                                         ` Michael S. Tsirkin
2012-11-13 16:33                                   ` Michael S. Tsirkin
2012-11-13 16:35                                     ` Peter Lieven
2012-11-13 16:46                                       ` Michael S. Tsirkin
2012-11-13 17:03                                     ` Dietmar Maurer
2012-11-13 17:07                                       ` Michael S. Tsirkin
2012-11-13 17:38                                         ` Dietmar Maurer
2012-11-15 18:26                                           ` Peter Lieven
2012-11-16 10:44                                             ` Dietmar Maurer
2012-11-16 11:00                                               ` Alexandre DERUMIER
2012-12-03 11:23                                                 ` Peter Lieven
2012-12-09 18:38                                                   ` Alexandre DERUMIER
2013-03-14  9:22                                                     ` Davide Guerri
2013-03-14 10:43                                                       ` Alexandre DERUMIER [this message]
2013-03-14 17:50                                                         ` Michael S. Tsirkin
2013-03-14 18:15                                                           ` Davide Guerri
2013-03-14 18:21                                                             ` Peter Lieven
2013-03-14 23:04                                                               ` Davide Guerri
2013-03-15  7:23                                                                 ` Peter Lieven
2013-03-17  9:08                                                                   ` Michael S. Tsirkin
2013-03-18  9:50                                                                     ` Alexandre DERUMIER
2013-03-18  9:53                                                                       ` Michael S. Tsirkin
2013-03-25 13:34                                                                         ` Peter Lieven
2012-11-19 13:49                                     ` Peter Lieven
2012-11-06  6:48   ` Dietmar Maurer

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=6ce47933-c4df-4a64-9b94-69922ea3ef9a@mailpro \
    --to=aderumier@odiso.com \
    --cc=d.guerri@unidata.it \
    --cc=dietmar@proxmox.com \
    --cc=jan.kiszka@web.de \
    --cc=lieven-lists@dlhnet.de \
    --cc=mst@redhat.com \
    --cc=pl@dlhnet.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).