All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Kazakov <michael@marathonbet.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Packet dropps in virtual tap interface
Date: Tue, 24 Feb 2015 10:15:11 +0300	[thread overview]
Message-ID: <54EC24FF.3000407@marathonbet.ru> (raw)
In-Reply-To: <54E706ED.4040804@marathonbet.ru>

Hello. We use our highly load system in OpenStack environment. And faced 
with serious problems in network highload guests. At a relatively high 
CPU load of hypervisor (40-60%) virtual network interfaces of this 
guests starts to droppart of the packets. We use for virtualization 
qemu-kvm with vhost driver: "... -netdev 
tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:86:67:7b,bus=pci.0,addr=0x3...". 

The problem can be seen with the ifconfig utility:
tape4009073-0b Link encap:Ethernet  HWaddr fe:16:3e:86:67:7b
           inet6 addr: fe80::fc16:3eff:fe86:677b/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:1587622634 errors:0 dropped:0 overruns:0 frame:0
           TX packets:1484106438 errors:0 dropped:460259 overruns:0 
carrier:0
           collisions:0 txqueuelen:500
           RX bytes:877878711500 (877.8 GB)  TX bytes:3071846828531 (3.0 
TB)

Could you do a little look at our problem and give advice which 
direction to continue our investigation?



-- 
С уважением,
Михаил Казаков
Старший системный администратор
OOO "СПЛАТ"

       reply	other threads:[~2015-02-24  7:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54E706ED.4040804@marathonbet.ru>
2015-02-24  7:15 ` Michael Kazakov [this message]
2015-02-24  7:18   ` Packet dropps in virtual tap interface Michael Kazakov
2015-02-24 17:03     ` Rick Jones
2015-02-25 10:11       ` Michael Kazakov

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=54EC24FF.3000407@marathonbet.ru \
    --to=michael@marathonbet.ru \
    --cc=qemu-devel@nongnu.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.