From: Wido den Hollander <wido@widodh.nl>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Setting iotune limits on rbd
Date: Tue, 03 Apr 2012 10:21:08 +0200 [thread overview]
Message-ID: <4F7AB2F4.2060905@widodh.nl> (raw)
In-Reply-To: <CABYiri81Jku1F7DjHYT80FPAq_swMfPkYGSnUpEaNsxs0BG6=w@mail.gmail.com>
Hi,
Op 3-4-2012 10:02, Andrey Korolyov schreef:
> Hi,
>
> # virsh blkdeviotune Test vdb --write_iops_sec 50 //file block device
>
> # virsh blkdeviotune Test vda --write_iops_sec 50 //rbd block device
> error: Unable to change block I/O throttle
> error: invalid argument: No device found for specified path
That is correct. As far as I know iotune uses the underlying cgroups
from the OS.
RBD devices (when using Qemu) are not block devices which can be managed
by cgroups. That's why it's not working and you get the error that the
device can't be found.
There is however somebody working on DiskIoThrottling inside Qemu:
http://wiki.qemu.org/Features/DiskIOLimits
That would work with RBD (he even names Ceph :) )
Wido
>
> 2012-04-03 07:38:49.170+0000: 30171: debug :
> virDomainSetBlockIoTune:18317 : dom=0x1114590, (VM: name=Test,
> uuid=8c27bf32-82dc-315a-d0ba-4653b1b3d595), disk=vda,
> params=0x1114600, nparams=1, flags=0
> 2012-04-03 07:38:49.170+0000: 30169: debug :
> virEventPollMakePollFDs:383 : Prepare n=8 w=11, f=16 e=1 d=0
> 2012-04-03 07:38:49.170+0000: 30169: debug :
> virEventPollCalculateTimeout:325 : Calculate expiry of 4 timers
> 2012-04-03 07:38:49.170+0000: 30169: debug :
> virEventPollCalculateTimeout:331 : Got a timeout scheduled for
> 1333438734170
> 2012-04-03 07:38:49.170+0000: 30171: error : qemuDiskPathToAlias:11338
> : invalid argument: No device found for specified path
> 2012-04-03 07:38:49.170+0000: 30171: debug : virDomainFree:2313 :
> dom=0x1114590, (VM: name=Test,
> uuid=8c27bf32-82dc-315a-d0ba-4653b1b3d595)
> 2012-04-03 07:38:49.170+0000: 30171: debug : virUnrefDomain:276 :
> unref domain 0x1114590 Test 1
> 2012-04-03 07:38:49.170+0000: 30171: debug : virReleaseDomain:238 :
> release domain 0x1114590 Test 8c27bf32-82dc-315a-d0ba-4653b1b3d595
> 2012-04-03 07:38:49.170+0000: 30169: debug :
> virEventPollCalculateTimeout:351 : Timeout at 1333438734170 due in
> 5000 ms
> 2012-04-03 07:38:49.170+0000: 30169: debug : virEventPollRunOnce:619 :
> EVENT_POLL_RUN: nhandles=9 imeout=5000
> 2012-04-03 07:38:49.170+0000: 30171: debug : virReleaseDomain:246 :
> unref connection 0x1177b10 2
>
> libvir 0.9.10, json-escape patch applied, but seems that this problem
> related to another incorrect path handle.
>
> I`m in doubt if it belongs to libvirt ml or here.
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-04-03 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 8:02 Setting iotune limits on rbd Andrey Korolyov
2012-04-03 8:21 ` Wido den Hollander [this message]
2012-04-03 8:28 ` Andrey Korolyov
2012-04-03 8:45 ` Wido den Hollander
2012-04-03 8:55 ` Andrey Korolyov
2012-04-03 9:43 ` Andrey Korolyov
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=4F7AB2F4.2060905@widodh.nl \
--to=wido@widodh.nl \
--cc=andrey@xdel.ru \
--cc=ceph-devel@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 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.