This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Network scripts start/stop

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Network scripts start/stop
From: Christopher Thunes <c2thunes@xxxxxxxxxxx>
Date: Fri, 04 Apr 2008 19:28:32 -0400
Delivery-date: Fri, 04 Apr 2008 16:29:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20070604)
Hello all,
    I was poking around with some network scripts for Xen today (3.2-testing) and noticed that regardless of whether xend start, xend restart, or xend stop was called a 'start' argument was passed on to the network script (network-bridge, network-route, etc.). I can't imagine this is normal behavior and it seems that the only place that these scripts are called is from a global function call in xend/XendPIF.py around line 35 ("Vifctl.network('start')"). I commented this line out and added appropriate calls to Vifctl.network('start') and Vifctl.network('stop') in xend/server/SrvServer.py in the functions cleanup and start. If someone can let me know if this is standard behavior and if not, if there is a better way to fix the problem it would be much appreciated.

- Chris Thunes
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>