All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ligesh <xen@lxlabs.com>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Communicating with the domU from dom0 without Network
Date: Mon, 7 Aug 2006 18:10:15 +0530	[thread overview]
Message-ID: <20060807124015.GA3365@lxlabs.com> (raw)

 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.

             reply	other threads:[~2006-08-07 12:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 12:40 Ligesh [this message]
2006-08-07 12:57 ` Communicating with the domU from dom0 without Network Muli Ben-Yehuda
2006-08-07 13:31   ` Ligesh
2006-08-07 13:32     ` Muli Ben-Yehuda
2006-08-07 13:49       ` Ligesh
2006-08-07 16:18         ` Michael LeMay
2006-08-08 10:49           ` Ligesh
2006-08-08 12:17             ` Michael LeMay
2006-08-08 14:45               ` Ligesh
2006-08-08 14:56                 ` Keir Fraser
2006-08-08 18:15                   ` Ligesh
2006-08-08 18:59                     ` Ian Campbell
2006-08-08 14:41           ` Mike D. Day
2006-08-08 20:54           ` Daniel Stodden
2006-08-08 23:04             ` Harry Butterworth
2006-08-08 23:34               ` Daniel Stodden
2006-08-08 23:47             ` Ligesh
2006-08-09 12:09               ` Daniel Stodden
2006-08-09 12:22                 ` Daniel Stodden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060807124015.GA3365@lxlabs.com \
    --to=xen@lxlabs.com \
    --cc=muli@il.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.