This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] RFC: "local" communications

To: "Rik van Riel" <riel@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] RFC: "local" communications
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 15 Jun 2005 22:53:57 +0100
Cc: Lon Hohberger <lhh@xxxxxxxxxx>
Delivery-date: Wed, 15 Jun 2005 21:53:02 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVx5h5j3a6SHrjoRHmR1591x+pjagADWOlA
Thread-topic: [Xen-devel] RFC: "local" communications
> In order for this to work better, it would be good if there 
> was a way for software in a domU to communicate with software 
> on the local dom0 - so after being migrated elsewhere, a 
> guest would start talking to the new dom0 automatically.
> Now what I'm not sure about is, what would be the best way to do this?
> Should it be some virtual device analogous to the virtual 
> network driver, or should we have some other kind of socket 
> for node local communications ?
> What kind of approach would the Xen community (that's you, if 
> you read this far) prefer ?

For relatively static stuff (e.g. textual configuration data), it would
be reasonable to use xenbus/xenstore. We could give each domain a
subtree in the store that it can read/write via a /proc/sys interface.

For other low bandwidth stuff we could have a simple protocol for
multiplexing datagrams over the virtual console channel. 

For high bandwidth stuff we'd want to set up separate shared memory

Rik: Does this mean you could be pursuaded to look at splitting the
console handling out of xend? :-)


Xen-devel mailing list