From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Jose A. Lopes" <jabolopes@google.com>
Subject: Re: Guest to Host communication
Date: Tue, 22 Oct 2013 09:54:28 -0400 [thread overview]
Message-ID: <20131022135428.GA17624@phenom.dumpdata.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD013ED63@AMSPEX01CL01.citrite.net>
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
prev parent reply other threads:[~2013-10-22 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 7:59 Guest to Host communication Jose A. Lopes
2013-10-22 8:48 ` Paul Durrant
2013-10-22 12:48 ` Jose A. Lopes
2013-10-22 13:18 ` Paul Durrant
2013-10-22 13:42 ` Jose A. Lopes
2013-10-31 14:21 ` George Dunlap
2013-10-31 16:08 ` Jose A. Lopes
2013-10-31 16:13 ` George Dunlap
2013-10-31 18:42 ` Jose A. Lopes
2013-10-31 20:02 ` Ian Campbell
2013-11-04 10:51 ` Jose A. Lopes
2013-10-22 13:54 ` Konrad Rzeszutek Wilk [this message]
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=20131022135428.GA17624@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Paul.Durrant@citrix.com \
--cc=jabolopes@google.com \
--cc=xen-devel@lists.xenproject.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).