Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Shiva <shivaramakrishnan740@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: I/O redirection Guest VM
Date: Fri, 14 Mar 2014 13:25:29 +0800	[thread overview]
Message-ID: <20140314052529.GE31322@T430.nay.redhat.com> (raw)
In-Reply-To: <loom.20140314T053855-981@post.gmane.org>

On Fri, 03/14 04:46, Shiva wrote:
> Hello,
> I am working on building an Storage Intrusion Detection System(SIDS) App 
> 
> inside a VM on KVM hypervisor. 
> 
> I wanted I/O's from other vm's to first contact this App VM and
> 
>  then finally write to the  disk.I went with the network storage as
> 
>  an option to achieve this objective. But wanted to know what  about 
> 
> I/O's that are not a shared on NFS-share for example? How can 
> 
> I intercept these I/O/'s ? As the guest VM will be having its own virtual disk 
> 
> and can write to its own partitions that are not part of NFS share.
> 
> I know modifying Qemu could be other options here.(Like developing a
> 
>  driver or adding redirection of I/O). But I have a time constraint here and
> 
>  unlikely to achieve it by this way.
> 
> Looking forward to your help/comments.Thanks
> 

Not sure I understand it correctly, but this sounds doable to backend.

If you want to intercept the IO's from other VM, can you move the location of
its virtual disk and let them access throught your NFS you App VM can control?

If you only want to observe the IO, you can mirror the writes to a target on
the NFS.

Thanks,
Fam

  reply	other threads:[~2014-03-14  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14  4:46 I/O redirection Guest VM Shiva
2014-03-14  5:25 ` Fam Zheng [this message]
2014-03-14  6:32   ` Shiva
     [not found]   ` <CAAQucXZcbca9MCykjKn1C43GqVh2x0R8dceWkPz7LGkFHnEoJQ@mail.gmail.com>
2014-03-14  6:32     ` Fam Zheng
2014-03-14  6:39       ` Shiva

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=20140314052529.GE31322@T430.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=shivaramakrishnan740@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