14 messages in com.xensource.lists.xen-develRe: [Xen-devel] BUG? domu network in...
FromSent OnAttachments
Michal OstrowskiAug 30, 2005 5:23 pm 
Keir FraserAug 31, 2005 1:00 am 
Ted KaczmarekAug 31, 2005 4:44 am 
Ian PrattAug 31, 2005 5:01 am 
Michal OstrowskiAug 31, 2005 5:42 am 
Ted KaczmarekAug 31, 2005 6:11 am 
Christian LimpachAug 31, 2005 6:53 am 
Hien NguyenAug 31, 2005 7:59 am 
Ted KaczmarekAug 31, 2005 8:09 am 
Michal OstrowskiAug 31, 2005 8:23 am 
Nivedita SinghviAug 31, 2005 9:03 am 
Hien NguyenAug 31, 2005 9:56 am 
Hien NguyenAug 31, 2005 3:07 pm 
Michal OstrowskiSep 1, 2005 7:26 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [Xen-devel] BUG? domu network interface configurationActions...
From:Michal Ostrowski (most@watson.ibm.com)
Date:Aug 31, 2005 5:42:08 am
List:com.xensource.lists.xen-devel

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.@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.