From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IrNl7-0008VG-21
	for qemu-devel@nongnu.org; Sun, 11 Nov 2007 20:06:37 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IrNl6-0008U8-6z
	for qemu-devel@nongnu.org; Sun, 11 Nov 2007 20:06:36 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IrNl6-0008Ty-2T
	for qemu-devel@nongnu.org; Sun, 11 Nov 2007 20:06:36 -0500
Received: from sark4.cc.gatech.edu ([130.207.7.19])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kaushikb@cc.gatech.edu>) id 1IrNl5-0008GF-NB
	for qemu-devel@nongnu.org; Sun, 11 Nov 2007 20:06:35 -0500
Received: from sark3.cc.gatech.edu (sark3.cc.gatech.edu [130.207.7.22])
	by sark4.cc.gatech.edu (8.13.6/8.12.8) with ESMTP id lAC16XED017593
	for <qemu-devel@nongnu.org>; Sun, 11 Nov 2007 20:06:33 -0500 (EST)
Received: from [192.168.0.161] (c-66-56-81-115.hsd1.ga.comcast.net
	[66.56.81.115]) (authenticated bits=0)
	by sark3.cc.gatech.edu (8.12.10/8.12.10) with ESMTP id lAC16WXt007526
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <qemu-devel@nongnu.org>; Sun, 11 Nov 2007 20:06:33 -0500 (EST)
Message-ID: <4737A711.4010806@cc.gatech.edu>
Date: Sun, 11 Nov 2007 20:06:25 -0500
From: Kaushik Bhandankar <kaushikb@cc.gatech.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Remote guest VBD
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

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