From: Michal Ostrowski <mostrows@watson.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Ted Kaczmarek <tedkaz@optonline.net>, xen-devel@lists.xensource.com
Subject: Re: BUG? domu network interface configuration
Date: Wed, 31 Aug 2005 08:42:30 -0400 [thread overview]
Message-ID: <20050831084230.0115fd39@brick.watson.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282DA2@liverpoolst.ad.cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1729 bytes --]
The immediate problem is in fact that vif-bridge is being called instead of
vif-route.
I'm working on something like the following to detect the script:
SCRIPT=/bin/false
if [ -r $CONFIG_FILE ]; then
SCRIPT=$(sed -e '/^[^#]*vif-script/!d;s/^(vif-script *\([^ )]*\)).*$/\1/' \
$CONFIG_FILE)
fi
if [ -z "`which $SCRIPT`" ] ; then
# not in path, should probably log an error
exit
fi
As you can see, sxp is not very script friendly.
Having been able to call vif-route, is just the beginning of the real problems...
Once I'm in vif-route I need to get the IP address that I assigned to the partition.
To get that I need to figure out the domain id. (I suppose I could guess that from
the device name.)
Then I need to find the SXP config file in xenstore (and now I need a
tool to parse it and extract the "(ip a.b.c.d)" statement), but I don't
see a way of doing that because there seem to be no scripting tools to
access xenstore.
Now, even if I did have such a tool, I don't see a way of going from
domain id to uuid, which is what I think I need in order to interact
with xenstore.
--
Michal Ostrowski
On Wed, 31 Aug 2005 13:01:29 +0100
"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> wrote:
>
> > > One fix would be for you to just hack the hotplug script. Another,
> > > slightly better, way would be to grep around in xend's
> > config script
> > > to find out what script should be run, and call that. We might even
> > > take that as an interim patch.
>
> Can you confirm that things work OK if you rename vif-route to
> vif-bridge?
>
> > Any idea when this would be implemented?
>
> Getting this cleaned up is important.
>
> Ian
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-08-31 12:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 12:01 BUG? domu network interface configuration Ian Pratt
2005-08-31 12:42 ` Michal Ostrowski [this message]
2005-08-31 13:54 ` Christian Limpach
2005-08-31 16:03 ` Nivedita Singhvi
2005-09-02 2:26 ` Michal Ostrowski
2005-08-31 13:11 ` Ted Kaczmarek
[not found] <OFF1A8E8EE.5092796D-ON8725706E.005C610E-8625706E.005D1E22@LocalDomain>
2005-08-31 22:07 ` Hien Nguyen
[not found] <E1EARGE-0006dP-2b@host-192-168-0-1-bcn-london>
2005-08-31 15:00 ` Hien Nguyen
2005-08-31 15:10 ` Ted Kaczmarek
2005-08-31 16:57 ` Hien Nguyen
2005-08-31 15:24 ` Michal Ostrowski
-- strict thread matches above, loose matches on Subject: below --
2005-08-31 0:24 Michal Ostrowski
2005-08-31 8:00 ` Keir Fraser
2005-08-31 11:45 ` Ted Kaczmarek
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=20050831084230.0115fd39@brick.watson.ibm.com \
--to=mostrows@watson.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=tedkaz@optonline.net \
--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.