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


[Xen-devel] Re: Communicating with the domU from dom0 without Network

To: Muli Ben-Yehuda <muli@xxxxxxxxxx>
Subject: [Xen-devel] Re: Communicating with the domU from dom0 without Network
From: Ligesh <xen@xxxxxxxxxx>
Date: Mon, 7 Aug 2006 19:19:07 +0530
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 07 Aug 2006 06:43:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060807133203.GL3802@xxxxxxxxxxxxxxxxxx>
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>
References: <20060807124015.GA3365@xxxxxxxxxx> <20060807125754.GG3802@xxxxxxxxxxxxxxxxxx> <20060807133130.GA4912@xxxxxxxxxx> <20060807133203.GL3802@xxxxxxxxxxxxxxxxxx>
Reply-to: Ligesh <xen@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Mon, Aug 07, 2006 at 04:32:03PM +0300, Muli Ben-Yehuda wrote:
> On Mon, Aug 07, 2006 at 07:01:30PM +0530, Ligesh wrote:
> Unlike openvz where all containers can run the same executables and
> largely share the same environment, in Xen domU's have nothing in
> common except being able to run on the same CPU. "Running an
> executable" is inherently domain-specific and thus not something that
> Xen should know about.

  It is evident that it is a bad design choice to let Xen be aware of the 
internals of domU, but I would like to know if it can be implemented as some 
sort of extra or something. Anyway, that is what would be the _ideal_ system 
management scenario. What would be practical is some form a message passing 
system, where a process running inside the domU can get messages directly from 
the dom0 without the help of network.

> >  Or at least we should be able to send some message to the domU
> >  using its NAME, and not ipaddress. This would make it easy to write
> >  scripts to automate the management, which would be difficult with
> >  the ipaddress, since ipaddress can change at some time.
> How about a simple script that given a domain's name or domain ID will
> return its IP?

 Is there any fool proof way to get an ip of the domU using its name? It is 
possible that the domU has been configured internally with a totally different 
IP from the one that has been assigned to it via the dhcp.

 Thanks for your time.

:: Ligesh :: http://ligesh.com 

Xen-devel mailing list