From: Ligesh <xen@lxlabs.com>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Communicating with the domU from dom0 without Network
Date: Mon, 7 Aug 2006 19:19:07 +0530 [thread overview]
Message-ID: <20060807134906.GA5601@lxlabs.com> (raw)
In-Reply-To: <20060807133203.GL3802@rhun.haifa.ibm.com>
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
next prev parent reply other threads:[~2006-08-07 13:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 12:40 Communicating with the domU from dom0 without Network Ligesh
2006-08-07 12:57 ` Muli Ben-Yehuda
2006-08-07 13:31 ` Ligesh
2006-08-07 13:32 ` Muli Ben-Yehuda
2006-08-07 13:49 ` Ligesh [this message]
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=20060807134906.GA5601@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.