From: =?gb18030?B?0rbJ3Oih?= <yeshaochen@foxmail.com>
To: =?gb18030?B?cWVtdS1kaXNjdXNz?= <qemu-discuss@nongnu.org>,
=?gb18030?B?cWVtdS1kZXZlbA==?= <qemu-devel@nongnu.org>
Subject: [Qemu-devel] qemu vm big network latency when met heavy io
Date: Mon, 6 Jan 2014 14:55:54 +0800 [thread overview]
Message-ID: <tencent_2B73F8D91117D5F534D25607@qq.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 1395 bytes --]
hi, all:
There is a problem when I use ceph rbd for qemu storage. I launch 4 virtual machines, and start 5G random write test at the same time. Under such heavy I/O, the network to
virtual machine almost unusable, the network latency is extremely big.
I had test another situation, when I use 'virsh attach-device' command to attach rbd which mapped in my host machine(which run virtual machines), the problem was not show again.
So, I think this must be qemu-rbd 's problem.
Here is my testing environment:
# virsh version
Compiled against library: libvirt 1.2.0
Using library: libvirt 1.2.0
Using API: QEMU 1.2.0
Running hypervisor: QEMU 1.7.0
In vm's xml, I define the rbd like this:
<disk type='network' device='disk'>
<driver name='qemu' type='raw' cache='none'/>
<source protocol='rbd' name='qemu/rbd-vm4'>
<host name='10.120.111.111' port='6789'/>
</source>
<auth username='libvirt'>
<secret type='ceph' uuid='38b66185-4117-47a6-90bd-64111c3fc5d2'/>
</auth>
<target dev='vdb' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</disk>
testing tool is : fio
io depth is : 32
io engine is : libaio
io direct is open
Is there anyone met such a problem?
regards
Alan Ye
------------------
Alan Ye
[-- Attachment #2: Type: text/html, Size: 6374 bytes --]
next reply other threads:[~2014-01-06 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 6:55 =?gb18030?B?0rbJ3Oih?= [this message]
2014-01-08 4:44 ` [Qemu-devel] qemu vm big network latency when met heavy io Stefan Hajnoczi
[not found] ` <CANzgAZnvTmKc1NKoJPRLTT-L-ppYWoUko6JKHfpMzOGboLh8YA@mail.gmail.com>
2014-01-09 2:47 ` [Qemu-devel] [Qemu-discuss] " Stefan Hajnoczi
[not found] ` <tencent_1499A979046903942D656C7F@qq.com>
[not found] ` <CAJSP0QV0G=reFHP4N=njGUcZxP-x-Ef=L0U3zj5DHfRGjrgvrw@mail.gmail.com>
[not found] ` <tencent_2A1DD90F3E8281BD36D67A63@qq.com>
[not found] ` <CAJSP0QW1m7UL27_CROjXsG2sBse+Md9fSWMgXzTZWVaxvhaz7Q@mail.gmail.com>
[not found] ` <tencent_74BAFF5462FB3EA25C557F97@qq.com>
[not found] ` <CAJSP0QXgjkHf3mFzSOm5rLjd5+uHpHDPTcKPFruZ0naTiN5yHg@mail.gmail.com>
2014-01-14 6:24 ` [Qemu-devel] 回复: 回复: 回复: " Josh Durgin
[not found] ` <tencent_35E422F81535374D5992C5AB@qq.com>
2014-01-14 7:58 ` [Qemu-devel] =?gb18030?b?u9i4tKO6ILvYuLSjuiC72Li0o7ogu9i4tKO6ICBx?= =?gb18030?q?emu_vm_big_network_latency_when_met_heavy_io?= Josh Durgin
[not found] ` <tencent_043538FC1C65245E76ED4CB0@qq.com>
2014-01-16 2:25 ` [Qemu-devel] =?gb18030?b?u9i4tKO6ILvYuLSjuiC72Li0o7ogu9i4tKO6ILvY?= =?gb18030?q?=B8=B4=A3=BA__qemu_vm_big_network_latency_when_met_heavy_io?= Josh Durgin
[not found] ` <tencent_0C119822426FB8B81E60F6EB@qq.com>
2014-01-17 6:57 ` [Qemu-devel] =?gb18030?b?u9i4tKO6ILvYuLSjuiC72Li0o7ogu9i4tKO6ILvYuLSjuiC72Li0o7ogIHFlbXUgdm0gYmlnIG5ldHdvcmsgbGF0ZW5jeSB3aGVu?= =?gb18030?q?_met_heavy_io?= Josh Durgin
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=tencent_2B73F8D91117D5F534D25607@qq.com \
--to=yeshaochen@foxmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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 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).