From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Equivalent of vmware SIOC (Storage IO Control) in KVM Date: Sun, 13 Oct 2013 15:26:31 +0200 Message-ID: <525A9F87.4020107@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" , Stefan Hajnoczi To: "Soumendu Satapathy (sosatapa)" Return-path: Received: from mail-ea0-f174.google.com ([209.85.215.174]:54029 "EHLO mail-ea0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751283Ab3JMN0f (ORCPT ); Sun, 13 Oct 2013 09:26:35 -0400 Received: by mail-ea0-f174.google.com with SMTP id z15so2819409ead.19 for ; Sun, 13 Oct 2013 06:26:34 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: Il 12/10/2013 08:09, Soumendu Satapathy (sosatapa) ha scritto: > Do we have an equivalent of vmware SIOC like feature in KVM? Yes, you have two choices: 1) use cgroups to throttle I/O at the level of the host disk (i.e. multiple virtual disks stored on the same disk share the limit). If you're using libvirt, add the element to the definition of the virtual machine. 2) enable I/O throttling in QEMU, to apply limits at the level of the guest disk. If you're using libvirt, add the "iotune" element within the element in the definition of the virtual machine. Both are documented at http://libvirt.org/formatdomain.html (search for blkiotune and iotune). Paolo