kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Ben Clay <rbclay@ncsu.edu>
Cc: kvm@vger.kernel.org
Subject: Re: FW: cgroup blkio.weight working, but not for KVM guests
Date: Tue, 23 Oct 2012 14:35:02 +0200	[thread overview]
Message-ID: <20121023123502.GF19977@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <014201cdb05a$414e7b20$c3eb7160$@ncsu.edu>

On Mon, Oct 22, 2012 at 07:36:34AM -0600, Ben Clay wrote:
> Forwarding this to the KVM general list.  I doubt you folks can help me with
> libvirt, but I was wondering if there’s some way to verify if the cache=none
> parameter is being respected for my KVM guest’s disk image, or if there are
> any other configuration/debug steps appropriate for KVM + virtio + cgroup.

Here's how you can double-check the O_DIRECT flag:

Find the QEMU process PID on the host:

ps aux | grep qemu

Then find the file descriptor of the image file which the QEMU process
has open:

ls -l /proc/$PID/fd

Finally look at the file descriptor flags to confirm it is O_DIRECT:

grep ^flags: /proc/$PID/fdinfo/$FD

Note the flags field is in octal and you're looking for:

#define O_DIRECT        00040000        /* direct disk access hint */

Stefan

  reply	other threads:[~2012-10-23 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <022401cdac8d$32565fa0$97031ee0$@ncsu.edu>
2012-10-22 13:36 ` FW: cgroup blkio.weight working, but not for KVM guests Ben Clay
2012-10-23 12:35   ` Stefan Hajnoczi [this message]
2012-10-23 22:48     ` Ben Clay
2012-10-24  6:10       ` Stefan Hajnoczi
2012-10-25 17:13         ` Avi Kivity

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=20121023123502.GF19977@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=rbclay@ncsu.edu \
    /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).