WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] console driver - How domain0 processes console messages ?

To: aq <aquynh@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] console driver - How domain0 processes console messages ?
From: Andrew Warfield <andrew.warfield@xxxxxxxxx>
Date: Wed, 16 Feb 2005 08:57:21 +0000
Delivery-date: Wed, 16 Feb 2005 08:58:37 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=TLPjThT95dQtQlJfItxeHa8NOyHWJqARHxhSbQyHKytGFGrt4bjERYu+mlo1PmNcgc9DNqax7MkWyStYXjtl/iYwGRxB0yNUimmDlPKLJUUe42LKaML/ZxarfQn39j9WddZTcfOqRjwFMFVJn4F0K6vXncdZx6JLIrLxfQ076A8=
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <eacc82a405021600562ed346d2@xxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <a146ff9b05021522102e311f77@xxxxxxxxxxxxxx> <eacc82a405021523546a3ad773@xxxxxxxxxxxxxx> <9cde8bff05021600382dc4a624@xxxxxxxxxxxxxx> <eacc82a405021600562ed346d2@xxxxxxxxxxxxxx>
Reply-to: andrew.warfield@xxxxxxxxxxxx
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> Andrew, as I understand, xcs provides xend's functionalities, and to
> some extent (I expect that xcs is still under development) we can use
> xcs instead of xend to manage domainUs. Is that correct?

Not exactly. ;)  As the control rings are shared memory, and indexed
using shared pointers, it isn't really possible to have multiple
clients in dom0 using them concurrently.  With xend connecting
directly to these rings, it was impossible to add new control messages
(for instance if you were working on a new driver) without having to
get waist-deep in xend itself.

xcs (xen control switch) just acts as a mux/demux for the control
channels.  In the unstable tree, xend has been modified to bind to
only the control messages that it is actively handling.  This means
that other control messages may be handled by completely separate
daemons in dom0.  It hopefully will also allow us to start to move
away from the current monolithic xend code, to a new set of control
tools in the very near future.

If all you are trying to do is add a relatively simple service between
dom0 and your domains, then xcs should help.  One example here would
be to build a rough load-balancer that received cpu load announcements
from a set of VMs and then periodically repinned them to alternate
CPUs or migrated them to other physical hosts.  (Just in case anybody
is looking for a little project. ;) )

Several people are working on new control tools at the moment.
Anthony Liguori has posted some first-round c-based tools to the list
in the past week or so.  Mike Wray is also in the process of
redesigning xend itself.  If you are looking for something in the
short term, Anthony's stuff may be helpful, and I'm sure he'd
appreciate any feedback.

cheers,
a.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel