WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] xen hotplug scripts not working

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] xen hotplug scripts not working
From: Christian Placzek <clp@xxxxxxxxxxx>
Date: Fri, 16 Mar 2007 10:18:44 +0100
Delivery-date: Fri, 16 Mar 2007 02:17:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1173986504.6538.170.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <45F9993D.9000408@xxxxxxxxxxx> <1173986504.6538.170.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Icedove 1.5.0.9 (X11/20061220)
Hi Tim,

thank you for your comments.

Tim Post wrote:
> On Thu, 2007-03-15 at 20:06 +0100, Christian Placzek wrote:
> 
>> auto eth1
>> allow-hotplug eth1
>> iface eth1 inet static
>>        address 10.1.1.201
>>        netmask 255.255.255.0
>>        network 1.1.1.0
> 
> Stop using network-bridge , its there to construct and deconstruct a
> bridge so that Xen itself is non destructive (no changing of network
> init needed to install it).
> 
> Since you are doing the more production-sensible thing by letting Debian
> handle your bridges in init, there's no need to be using network-bridge.
> Better, more structured and sensible control over all of that is partly
> achieved by how you construct your guests.
> 
> First thing to do, get rid of network-bridge
> 
> In /etc/xen/scripts/ do 
> 
> echo -e "#!/bin/sh\nexit 0" > network-dummy && chmod +x network-dummy

Just for information: this script already exists in the debian package (v. 
3.0.3).

> 
> Then in /etc/xen/ change xend-config.sxp to call network-dummy instead
> of network-bridge.
> 
> Secondly (just suggesting) : 
> 
> Specify vifname= in the vif [] containers in the guests to keep it all
> nice and neat. If you name the vif after the domname (or something else
> specific and meaningful), bandwidth accounting becomes *very* easy over
> an entire farm, which sounds like it would also lend well to your setup.

What do you mean? Naming the bridge for easy identifying or are there more 
options?


> 
> Best,
> --Tim
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 

-- 
Mit freundlichen Grüßen / with kind regards

Christian Placzek



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

<Prev in Thread] Current Thread [Next in Thread>