From mboxrd@z Thu Jan 1 00:00:00 1970 From: Muli Ben-Yehuda Subject: Re: Communicating with the domU from dom0 without Network Date: Mon, 7 Aug 2006 15:57:54 +0300 Message-ID: <20060807125754.GG3802@rhun.haifa.ibm.com> References: <20060807124015.GA3365@lxlabs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20060807124015.GA3365@lxlabs.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ligesh Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Mon, Aug 07, 2006 at 06:10:15PM +0530, Ligesh wrote: > 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. I agree this could be useful. If you have networking setup between dom0 and the domU's (which I think is set up by default), you can do this without any Xen involvement by just using ssh: ssh domu.ip.add.ress command args args args To avoid having ssh ask for a password, use passwordless SSH as explained in the SSH documentation. Cheers, Muli