Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

Re: [Xen-devel] BUG? domu network interface configuration

To: Michal Ostrowski <mostrows@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] BUG? domu network interface configuration
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 31 Aug 2005 09:00:54 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 31 Aug 2005 07:55:09 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050830202415.34ecc212@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20050830202415.34ecc212@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 31 Aug 2005, at 01:24, Michal Ostrowski wrote:

- vif-route has never been called, so the domain's networking doesn't
come up, even though the domain runs.

- this same configuration was working prior to an update this afternoon
(previous snapshot was from last Thursday).

The changes to xenbus mean that we call vif up/down via hotplug, and our hotplug script is hardcoded to call the bridge script. Probably it ought to pull stuff out of xenstore to work out what to do, but that's not implemented right now.

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.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel