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

To: Muli Ben-Yehuda <muli@xxxxxxxxxx>
Subject: [Xen-devel] Communicating with the domU from dom0 without Network
From: Ligesh <xen@xxxxxxxxxx>
Date: Mon, 7 Aug 2006 18:10:15 +0530
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 07 Aug 2006 05:34:57 -0700
Envelope-to: www-data@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>
Reply-to: Ligesh <xen@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
 Hi Folks,

  I would like to have a discussion on whether if it isn't desirable to have 
some mechanism to directly communicate with the domU from the dom0. Wouldn't 
that make managing this entire setup much easier? In the openVZ, the vzctl tool 
can actually run anything inside a virtual machine. For instance, we can say 
'vzctl exec $vpsid ps ax', and it will return the output of the 'ps' executed 
inside the vps. I realize that the virtualization concept is radically 
different in Xen, and thus this type of communication would be non-trivial.

  Anyway, I would like to know the pros and cons of having a direct mechanism 
to communicate with the domUs. As far as I have seen, the inability to manage 
the domUs directly has been the ONLY drawback of xen. 

  Thanks in advance.

Xen-devel mailing list