All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Wolfgang Richter <wolf@cs.cmu.edu>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Adding Disk-Level Introspection to QEMU
Date: Wed, 24 Apr 2013 11:26:59 +0200	[thread overview]
Message-ID: <5177A563.3000900@redhat.com> (raw)
In-Reply-To: <CACO=3k68tJUfroz=XrjguFs0VXyCfAJzEuaX-9N5ZvB8X4U=1Q@mail.gmail.com>

Il 23/04/2013 20:31, Wolfgang Richter ha scritto:
> On Tue, Apr 23, 2013 at 2:21 PM, Stefan Hajnoczi <stefanha@gmail.com
> <mailto:stefanha@gmail.com>> wrote:
> 
>     The tracing subsystem is geared towards tracepoint instrumentation
>     rather than binary dumps.
> 
>     Can you share some specific applications?
> 
> 
> Well, my main application is in exposing a "cloud-inotify" service by
> interpreting
> sector writes in real-time and publishing the updates as file system
> manipulations.
> By using introspection we don't need agents running inside the guest.
> 
> Example: guest writes to sector 5786907; I reverse-map that sector and
> notice
> it belongs to '/etc/passwd' within that guest; I immediately emit a message
> (currently using Redis pub-sub functionality) to any interested
> subscribers that
> '/etc/passwd' changed within this guest running on a certain host within the
> datacenter.

If you are okay with writes being "bundled" and you are able to handle
reordered writes within a small timeframe (usually 0.1-1s), then you can
use drive-mirror with an NBD destination.

Paolo

  parent reply	other threads:[~2013-04-24  9:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 17:12 [Qemu-devel] Adding Disk-Level Introspection to QEMU Wolfgang Richter
2013-04-23 17:22 ` Eric Blake
2013-04-23 17:40   ` Wolfgang Richter
2013-04-24  8:37     ` Stefan Hajnoczi
2013-04-24  9:24       ` Paolo Bonzini
2013-04-24 16:14         ` Wolfgang Richter
2013-04-24 15:59       ` Wolfgang Richter
2013-04-24 19:20       ` Wolfgang Richter
2013-04-23 18:19   ` Stefan Hajnoczi
2013-04-23 18:21 ` Stefan Hajnoczi
2013-04-23 18:31   ` Wolfgang Richter
2013-04-23 19:11     ` Wolfgang Richter
2013-04-24  8:39       ` Stefan Hajnoczi
2013-04-24 16:05         ` Wolfgang Richter
2013-04-24  9:26     ` Paolo Bonzini [this message]
2013-04-24 16:14       ` Wolfgang Richter
     [not found]       ` <CACO=3k4eoT9KwPBgM2eN089=PzzOyBECWgD6MOHz=bzy5EcxAQ@mail.gmail.com>
     [not found]         ` <51780539.1010303@redhat.com>
2013-04-24 16:43           ` Wolfgang Richter

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=5177A563.3000900@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=wolf@cs.cmu.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 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.