qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: "Aarian P. Aleahmad" <arian.spidey@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] Tracking the VM making an IO request
Date: Mon, 14 Mar 2016 10:13:56 +0800	[thread overview]
Message-ID: <20160314021356.GD2112@ad.usersys.redhat.com> (raw)
In-Reply-To: <CAEbcHeoC_k2wzzKM8cAxnXPJV7H0TW8nsNcuJkwkUjsn7BHOHg@mail.gmail.com>

On Sat, 03/12 16:17, Aarian P. Aleahmad wrote:
> Thanks for helping me. what should I do in case of using KVM?

The said method works exactly the same with or without -enable-kvm.

Fam

> 
> On Wed, Feb 10, 2016 at 4:10 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> 
> >
> >
> > On 10/02/2016 11:23, Stefan Hajnoczi wrote:
> > > On Wed, Feb 10, 2016 at 12:35:54PM +0330, Aarian P. Aleahmad
> > > wrote:
> > >> I'm a student, engaged in a project in which QEMU is a candidate
> > >> to be used to make some studies about IO usage etc. I need to
> > >> track the IO requests made to the block devices (e.g. HDD, SSD,
> > >> etc.). I check the source code but I was confused. What I want to
> > >> know is that when an IO request is made, find out that which on
> > >> of the VMs has made that request. I'll thank you if you help me
> > >> on this issue.
> > >
> > > There are trace events that you can use.  See docs/tracing.txt and
> > > trace-events.
> > >
> > > virtio_blk_handle_write and virtio_blk_handle_read can be used if
> > > your guest has virtio-blk.
> > >
> > > The QEMU block layer also has trace events named bdrv_aio_*.
> > >
> > > Or you could use blktrace(8) in the guest or on the host, depending
> > > on how you've set up storage.
> >
> > It's the third time I've gotten the question recently which makes me
> > believe the others were friends with Aarian...
> >
> > Each QEMU process represents a single VM.  Therefore, it is simple to
> > answer the question "which VM is making the request"; the answer is
> > "the one for the QEMU process you are tracing".
> >
> > You probably want to use blktrace if you care about multiple VMs.
> > Alternatively, you can use tracing as mentioned by Stefan.  If you
> > compile QEMU with --enable-trace-backend=simple, the resulting files
> > can be parsed with Python programs (see scripts/simpletrace.py).  The
> > trace files include the pid and a timestamp based on CLOCK_MONOTONIC,
> > so it should be easy to merge the traces together.
> >
> > Paolo
> >

      reply	other threads:[~2016-03-14  2:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  9:05 [Qemu-devel] Tracking the VM making an IO request Aarian P. Aleahmad
2016-02-10 10:23 ` Stefan Hajnoczi
2016-02-10 12:40   ` Paolo Bonzini
2016-03-12 12:47     ` Aarian P. Aleahmad
2016-03-14  2:13       ` Fam Zheng [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=20160314021356.GD2112@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=arian.spidey@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).