From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Guest to Host communication Date: Tue, 22 Oct 2013 09:54:28 -0400 Message-ID: <20131022135428.GA17624@phenom.dumpdata.com> References: <20131022075936.GB4223@google.com> <9AAE0902D5BC7E449B7C8E4E778ABCD013E890@AMSPEX01CL01.citrite.net> <20131022124857.GC4223@google.com> <9AAE0902D5BC7E449B7C8E4E778ABCD013ED63@AMSPEX01CL01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VYcPs-0003Lg-Qz for xen-devel@lists.xenproject.org; Tue, 22 Oct 2013 13:54:37 +0000 Content-Disposition: inline In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD013ED63@AMSPEX01CL01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Paul Durrant Cc: "xen-devel@lists.xenproject.org" , "Jose A. Lopes" List-Id: xen-devel@lists.xenproject.org On Tue, Oct 22, 2013 at 01:18:56PM +0000, Paul Durrant wrote: > > -----Original Message----- > > From: Jose A. Lopes [mailto:jabolopes@google.com] > > Sent: 22 October 2013 13:49 > > To: Paul Durrant > > Cc: xen-devel@lists.xenproject.org > > Subject: Re: [Xen-devel] Guest to Host communication > > > > Hi, > > > > If I understood correctly, Xenstore requires writing a driver and > > loading it inside the VM. Is this correct? > > > > Well, yes you'll need some code in the guest, but drivers already exist for linux and windows so you could just use them. So, Microsoft came up with this kvp (key value) driver that can communicate with the host. The guest only needs to use a socket interface to talk - and best of all it is in the upstream kernel. The driver (user-space) is this one: http://lxr.free-electrons.com/source/tools/hv/hv_kvp_daemon.c and it listens to the socket. The kernel driver gets the key/values from the host and it ends up pushing them to the daemon. The daemon does whatever it needs to do with them (say, alter the IP of the guest, return the OS info back and so on). It should be possible to make the kernel driver use a XenBus instead of a VMBus and piggyback on this. > > > If so, then it seems this approach would require writing different > > drivers for different OSes, such as, Linux and Windows. Currently, we The neat thing is that it would also work out of the box on Windows (I hope). > > are just exploring different design options and we would like to aim > > at a uniform approach across different OSes. Is there an option like that ? > > > > What option do you expect that doesn't involve writing at least some code for each OS you want to use? > > Paul > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel