Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Shivaramakrishnan Vaidyanathan <shivaramakrishnan740@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: I/O redirection Guest VM
Date: Fri, 14 Mar 2014 14:32:41 +0800	[thread overview]
Message-ID: <20140314063241.GI31322@T430.nay.redhat.com> (raw)
In-Reply-To: <CAAQucXZcbca9MCykjKn1C43GqVh2x0R8dceWkPz7LGkFHnEoJQ@mail.gmail.com>

On Fri, 03/14 02:00, Shivaramakrishnan Vaidyanathan wrote:
> Hello Fam,
> Thanks a lot  to your reply.
> I think I needed to bit more clear in my explanation.
> Here is my requirement:
> At first,I have a guest vm with its virtual disk performing no storage
> intrusion detection  running on top of kvm hypervisor. Then later I create
> this new VM app that performs the storage intrusion detection functionality
> again running on top of kvm hypervisor.I run nfs share inside this vm. Once
> I do this,I need the I/O's that is happening on guest vm to undergo the
> intrusion detection functionality before writes are performed on the disks.
> 
> 
> How could I point the image to the NFS share if the guest vm prior didn't
> had this functionality?
> And If I do the functionality now,Only NFS-shared partitions could be
> intercepted.What about the other partition writes occurring at the guest vm?
> 

Sounds like you need to change the backend of VM on flight to you NFS share.
But I don't think it's supported for now. (Assuming you use QEMU as device
virtualizer).

Fam

  parent reply	other threads:[~2014-03-14  6:32 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
2014-03-14  6:32   ` Shiva
     [not found]   ` <CAAQucXZcbca9MCykjKn1C43GqVh2x0R8dceWkPz7LGkFHnEoJQ@mail.gmail.com>
2014-03-14  6:32     ` Fam Zheng [this message]
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=20140314063241.GI31322@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