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] Re: Communicating with the domU from dom0 without Network

To: Ligesh <xen@xxxxxxxxxx>
Subject: [Xen-devel] Re: Communicating with the domU from dom0 without Network
From: Muli Ben-Yehuda <muli@xxxxxxxxxx>
Date: Mon, 7 Aug 2006 16:32:03 +0300
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 07 Aug 2006 06:32:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060807133130.GA4912@xxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11
On Mon, Aug 07, 2006 at 07:01:30PM +0530, Ligesh wrote:

>  How do we do this for windows? The ideal would be an internal
>  mechanism to spawn and execute a process inside the DomU, and
>  return its output/error/status back.

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.

>  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?

Cheers,
Muli

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel