public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Neil Aggarwal" <neil@JAMMConsulting.com>
To: <kvm@vger.kernel.org>
Subject: RE: Has anyone used tc to police traffic for VMs?
Date: Sat, 11 May 2013 10:00:59 -0500	[thread overview]
Message-ID: <000f01ce4e58$59455e50$0bd01af0$@JAMMConsulting.com> (raw)
In-Reply-To: <001b01ce4d9c$8f2ef7e0$ad8ce7a0$@JAMMConsulting.com>

Hello:

> Has anyone been able to limit traffic separately to individual VMs?

I just figured out libvirt has bandwidth controls in the guest machine's
configuration.  I tried it and it worked.  Looking at the qdisc ls report,
it apparently uses tc to achieve the limiting so I am not sure why my
manual commands did not work but now I guess it does not matter.

Thanks,
  Neil

--
Neil Aggarwal, (972)834-1565, http://UnmeteredVPS.net/centos
Virtual private server with CentOS 6 preinstalled
Unmetered bandwidth = no overage charges


      reply	other threads:[~2013-05-11 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 16:36 Has anyone used tc to police traffic for VMs? Neil Aggarwal
2013-05-11 15:00 ` Neil Aggarwal [this message]

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='000f01ce4e58$59455e50$0bd01af0$@JAMMConsulting.com' \
    --to=neil@jammconsulting.com \
    --cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox