From: Shiva <shivaramakrishnan740@gmail.com>
To: kvm@vger.kernel.org
Subject: I/O redirection Guest VM
Date: Fri, 14 Mar 2014 04:46:34 +0000 (UTC) [thread overview]
Message-ID: <loom.20140314T053855-981@post.gmane.org> (raw)
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
--
Shiva
next reply other threads:[~2014-03-14 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 4:46 Shiva [this message]
2014-03-14 5:25 ` I/O redirection Guest VM Fam Zheng
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=loom.20140314T053855-981@post.gmane.org \
--to=shivaramakrishnan740@gmail.com \
--cc=kvm@vger.kernel.org \
/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