qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kaushik Bhandankar <kaushikb@cc.gatech.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Remote guest VBD
Date: Sun, 11 Nov 2007 20:06:25 -0500	[thread overview]
Message-ID: <4737A711.4010806@cc.gatech.edu> (raw)

Hello,

I  am trying to implement remote VBD functionality for HVM guests is 
fully-virtualized Xen 3.0 unstable.

Consider 2 machines: machine 1 and machine 2, booth Intel-VT capable 
machines hosting fully-virtualized Xen 3.0-unstable.

Lets say the HVM guest sitting on machine 1 has its VBD located on 
machine 2 (same/different LAN)

For this, I have established a 9P communication channel (similar to 
socket communication) between the Dom0's of machine 1 and machine 2 with 
the 9P server thread running on machine 2 and 9P client thread running 
on machine 1.

Whenever the HVM guest tries to access its VBD, my 9P client needs 
tointercept this invocation and send it to the 9P server which does the 
necessary stuff with the VBD and sends back the response to the 9P client.

But I am not sure about following details:
1) The code path followed when a guest tries to access its VBD before it 
lands me into tools/ioemu/hw/ide.c:ide_ioport_read() or 
tools/ioemu/hw/ide.c:ide_ioport_write()
2) Where exactly should the 9P client intercept the call by guest to 
access its VBD?
3) When the 9P server sends the response back to the 9P client, how 
should this response be forwarded by the client?

Any help about this will be appreciated.

-Kaushik

             reply	other threads:[~2007-11-12  1:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12  1:06 Kaushik Bhandankar [this message]
2007-11-13  1:08 ` [Qemu-devel] Remote guest VBD kaushikb

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=4737A711.4010806@cc.gatech.edu \
    --to=kaushikb@cc.gatech.edu \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).